agentleFS
hostingerhostinger/hostinger-agent-skills/skills/vps/SKILL.md

vps

Skill28 starsChanged 5 months agoMITView on GitHub

Hostinger VPS API for virtual machine management, Docker projects, firewalls, SSH keys, backups, snapshots, OS templates, post-install scripts, recovery mode, malware scanning, PTR records, and metrics. Use when creating, managing, or troubleshooting VPS instances, deploying Docker containers, configuring firewalls, or managing server infrastructure.

  • Sends data out

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. Bobagi/claude-skills★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository7 other files it gives its agents.

The file

Show its rules and text

We split this skill into the rules it gives an agent

20 rules. About 0 are common, 16 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈16

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Always attach SSH keys and disable password auth when possible

    line 392
  2. Distinctive:

    Sync firewalls: after any rule change — changes don't auto-apply

    line 394
  3. Distinctive:

    Only one firewall per VM — plan rules in a single firewall

    line 395
  4. Distinctive:

    Use strong passwords (12+ chars, mixed case, numbers, not leaked)

    line 397
  5. Very specific:

    Use recovery mode for filesystem repair — original disk is at /mnt

    line 403
  6. Distinctive:

    Use logs endpoint for debugging container issues

    line 409
  7. Distinctive:

    Test scripts on non-production VMs first

    line 418
  8. Distinctive:

    Check action history for error details

    line 423
  9. Very specific:

    Check if VM is in initial state — run setup first

    line 425
  10. Distinctive:

    Verify SSH key is attached (not just in account)

    line 428
  11. Distinctive:

    Check firewall allows port 22

    line 429
  12. Distinctive:

    Verify firewall is synced after rule changes

    line 430
  13. Distinctive:

    Only one firewall can be active per VM

    line 435
  14. Distinctive:

    Default policy is DROP — ensure accept rules exist for needed ports

    line 436
  15. Very specific:

    Check project logs: GET .../docker/{name}/logs

    line 439
  16. Very specific:

    Verify docker-compose.yaml is valid

    line 440
  17. Distinctive:

    Ensure required ports are not already in use

    line 441
  18. Distinctive:

    Check VM has enough resources (CPU, RAM, disk)

    line 442
  19. Distinctive:

    Must be 12+ characters with uppercase, lowercase, and numbers

    line 445
  20. Distinctive:

    If stuck for extended time, contact support

    line 452

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Hostinger VPS

The VPS API provides comprehensive management of virtual private servers — from purchasing and setup to Docker deployments, firewall configuration, SSH keys, backups, snapshots, OS reinstallation, recovery mode, malware scanning, and performance monitoring.

Table of Contents

  • Core Concepts
  • Common Patterns
  • API Reference
  • Best Practices
  • Troubleshooting
  • References

Core Concepts

Virtual Machines

VPS instances with dedicated CPU, RAM, disk, and network resources. Each VM has an OS template, root access, and an IP address. VMs go through states: initial → running → stopped.

Actions

Asynchronous operations on VMs (start, stop, restart, recreate, etc.) return an action resource with a status you can poll.

Docker Manager

Deploy and manage Docker Compose projects directly on VPS instances. Supports creating projects from docker-compose.yaml content or GitHub URLs.

Firewalls

Network security rules that control inbound traffic. By default, all incoming traffic is dropped — you must explicitly add accept rules. Only one firewall can be active per VM at a time. Changes require manual sync to take effect.

SSH Public Keys

SSH keys for authentication. Keys are managed at the account level and attached to specific VMs.

OS Templates

Pre-configured operating system images for VM installation (Ubuntu, Debian, CentOS, etc.) including panel templates (e.g., with cPanel or Plesk).

Post-Install Scripts

Automation scripts that run after VM installation. Saved to /post_install with executable permissions. Output goes to /post_install.log. Maximum size: 48KB.

Backups & Snapshots

  • Backups: Automatic periodic backups managed by Hostinger
  • Snapshots: User-initiated point-in-time captures. Only one snapshot per VM — creating a new one overwrites the existing one

Recovery Mode

Boot the VM from a recovery disk image for system rescue. The original disk is mounted at /mnt.

Malware Scanner (Monarx)

Optional security tool for malware detection and prevention on VPS instances.

Common Patterns

Purchase and Setup a VPS

# Step 1: Get available OS templates
curl -X GET "https://developers.hostinger.com/api/vps/v1/templates" \
  -H "Authorization: Bearer $HOSTINGER_API_TOKEN"

# Step 2: Get available data centers
curl -X GET "https://developers.hostinger.com/api/vps/v1/data-centers" \
  -H "Authorization: Bearer $HOSTINGER_API_TOKEN"

# Step 3: Purchase a VPS
curl -X POST "https://developers.hostinger.com/api/vps/v1/virtual-machines" \
  -H "Authorization: Bearer $HOSTINGER_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "item_id": "hostingercom-vps-kvm2-usd-1m",
    "payment_method_id": 517244,
    "template_id": 1,
    "data_center_id": 1,
    "hostname": "my-server",
    "password": "SecurePass123!"
  }'

# Step 4: Setup purchased VM (if in initial state)
curl -X POST "https://developers.hostinger.com/api/vps/v1/virtual-machines/12345/setup" \
  -H "Authorization: Bearer $HOSTINGER_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "template_id": 1,
    "data_center_id": 1,
    "hostname": "my-server",
    "password": "SecurePass123!"
  }'

CLI (hapi):

hapi vps vm list

Python SDK:

from hostinger_api import Hostinger

client = Hostinger(api_token="YOUR_API_TOKEN")

# List all VPS instances
vms = client.vps.virtual_machines.list()
for vm in vms:
    print(f"{vm.hostname} - {vm.state} - {vm.ip_address}")

TypeScript SDK:

import { Hostinger } from "hostinger-api-sdk";

const client = new Hostinger({ apiToken: "YOUR_API_TOKEN" });

const vms = await client.vps.virtualMachines.list();
for (const vm of vms) {
  console.log(`${vm.hostname} - ${vm.state} - ${vm.ipAddress}`);
}

PHP SDK:

use Hostinger\Api\HostingerApi;

$client = new HostingerApi('YOUR_API_TOKEN');

$vms = $client->vps->virtualMachines->list();
foreach ($vms as $vm) {
    echo "{$vm->hostname} - {$vm->state} - {$vm->ip_address}\n";
}

VM Lifecycle Operations

# List all VMs
curl -X GET "https://developers.hostinger.com/api/vps/v1/virtual-machines" \
  -H "Authorization: Bearer $HOSTINGER_API_TOKEN"

# Get VM details
curl -X GET "https://developers.hostinger.com/api/vps/v1/virtual-machines/12345" \
  -H "Authorization: Bearer $HOSTINGER_API_TOKEN"

# Start VM
curl -X POST "https://developers.hostinger.com/api/vps/v1/virtual-machines/12345/start" \
  -H "Authorization: Bearer $HOSTINGER_API_TOKEN"

# Stop VM
curl -X POST "https://developers.hostinger.com/api/vps/v1/virtual-machines/12345/stop" \
  -H "Authorization: Bearer $HOSTINGER_API_TOKEN"

# Restart VM
curl -X POST "https://developers.hostinger.com/api/vps/v1/virtual-machines/12345/restart" \
  -H "Authorization: Bearer $HOSTINGER_API_TOKEN"

# Set hostname
curl -X PUT "https://developers.hostinger.com/api/vps/v1/virtual-machines/12345/hostname" \
  -H "Authorization: Bearer $HOSTINGER_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{ "hostname": "new-hostname.example.com" }'

# Set root password
curl -X PUT "https://developers.hostinger.com/api/vps/v1/virtual-machines/12345/root-password" \
  -H "Authorization: Bearer $HOSTINGER_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{ "password": "NewSecurePass123!" }'

# Recreate VM (DESTRUCTIVE - all data lost)
curl -X POST "https://developers.hostinger.com/api/vps/v1/virtual-machines/12345/recreate" \
  -H "Authorization: Bearer $HOSTINGER_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "template_id": 1,
    "password": "SecurePass123!"
  }'

Deploy Docker Compose Projects

# List Docker projects on a VM
curl -X GET "https://developers.hostinger.com/api/vps/v1/virtual-machines/12345/docker" \
  -H "Authorization: Bearer $HOSTINGER_API_TOKEN"

# Deploy from docker-compose.yaml content
curl -X POST "https://developers.hostinger.com/api/vps/v1/virtual-machines/12345/docker" \
  -H "Authorization: Bearer $HOSTINGER_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "project_name": "my-app",
    "content": "version: \"3\"\nservices:\n  web:\n    image: nginx:latest\n    ports:\n      - \"80:80\""
  }'

# Deploy from GitHub URL
curl -X POST "https://developers.hostinger.com/api/vps/v1/virtual-machines/12345/docker" \
  -H "Authorization: Bearer $HOSTINGER_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "project_name": "my-app",
    "url": "https://github.com/user/repo"
  }'

# Get project containers and stats
curl -X GET "https://developers.hostinger.com/api/vps/v1/virtual-machines/12345/docker/my-app/containers" \
  -H "Authorization: Bearer $HOSTINGER_API_TOKEN"

# View project logs (last 300 entries)
curl -X GET "https://developers.hostinger.com/api/vps/v1/virtual-machines/12345/docker/my-app/logs" \
  -H "Authorization: Bearer $HOSTINGER_API_TOKEN"

# Start / Stop / Restart / Update / Delete project
curl -X POST ".../docker/my-app/start" -H "Authorization: Bearer $HOSTINGER_API_TOKEN"
curl -X POST ".../docker/my-app/stop" -H "Authorization: Bearer $HOSTINGER_API_TOKEN"
curl -X POST ".../docker/my-app/restart" -H "Authorization: Bearer $HOSTINGER_API_TOKEN"
curl -X POST ".../docker/my-app/update" -H "Authorization: Bearer $HOSTINGER_API_TOKEN"
curl -X DELETE ".../docker/my-app/down" -H "Authorization: Bearer $HOSTINGER_API_TOKEN"

Configure Firewalls

# Create a firewall
curl -X POST "https://developers.hostinger.com/api/vps/v1/firewall" \
  -H "Authorization: Bearer $HOSTINGER_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{ "name": "web-server" }'

# Add rules (default drops all — add accept rules for ports you need)
curl -X POST "https://developers.hostinger.com/api/vps/v1/firewall/1/rules" \
  -H "Authorization: Bearer $HOSTINGER_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "protocol": "tcp",
    "port": "80",
    "source": "0.0.0.0/0",
    "action": "accept"
  }'

# Activate firewall on a VM
curl -X POST "https://developers.hostinger.com/api/vps/v1/firewall/1/activate/12345" \
  -H "Authorization: Bearer $HOSTINGER_API_TOKEN"

# Sync firewall after rule changes
curl -X POST "https://developers.hostinger.com/api/vps/v1/firewall/1/sync/12345" \
  -H "Authorization: Bearer $HOSTINGER_API_TOKEN"

SSH Key Management

# Create SSH key
curl -X POST "https://developers.hostinger.com/api/vps/v1/public-keys" \
  -H "Authorization: Bearer $HOSTINGER_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "my-laptop",
    "key": "ssh-ed25519 AAAA... user@host"
  }'

# Attach key to VM
curl -X POST "https://developers.hostinger.com/api/vps/v1/public-keys/attach/12345" \
  -H "Authorization: Bearer $HOSTINGER_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{ "ids": [1, 2] }'

# List keys on a VM
curl -X GET "https://developers.hostinger.com/api/vps/v1/virtual-machines/12345/public-keys" \
  -H "Authorization: Bearer $HOSTINGER_API_TOKEN"

Backups and Snapshots

# List backups
curl -X GET "https://developers.hostinger.com/api/vps/v1/virtual-machines/12345/backups" \
  -H "Authorization: Bearer $HOSTINGER_API_TOKEN"

# Restore a backup (DESTRUCTIVE - overwrites all data)
curl -X POST "https://developers.hostinger.com/api/vps/v1/virtual-machines/12345/backups/99/restore" \
  -H "Authorization: Bearer $HOSTINGER_API_TOKEN"

# Create a snapshot (overwrites existing snapshot)
curl -X POST "https://developers.hostinger.com/api/vps/v1/virtual-machines/12345/snapshot" \
  -H "Authorization: Bearer $HOSTINGER_API_TOKEN"

# Get current snapshot
curl -X GET "https://developers.hostinger.com/api/vps/v1/virtual-machines/12345/snapshot" \
  -H "Authorization: Bearer $HOSTINGER_API_TOKEN"

# Restore from snapshot
curl -X POST "https://developers.hostinger.com/api/vps/v1/virtual-machines/12345/snapshot/restore" \
  -H "Authorization: Bearer $HOSTINGER_API_TOKEN"

Monitor Performance

# Get VM metrics (CPU, memory, disk, network, uptime)
curl -X GET "https://developers.hostinger.com/api/vps/v1/virtual-machines/12345/metrics?date_from=2025-05-01T00:00:00Z&date_to=2025-06-01T00:00:00Z" \
  -H "Authorization: Bearer $HOSTINGER_API_TOKEN"

API Reference

Virtual Machines

MethodEndpointDescription
GET/api/vps/v1/virtual-machinesList all VMs
POST/api/vps/v1/virtual-machinesPurchase new VM
GET/api/vps/v1/virtual-machines/{id}Get VM details
POST/api/vps/v1/virtual-machines/{id}/setupSetup purchased VM
POST/api/vps/v1/virtual-machines/{id}/startStart VM
POST/api/vps/v1/virtual-machines/{id}/stopStop VM
POST/api/vps/v1/virtual-machines/{id}/restartRestart VM
POST/api/vps/v1/virtual-machines/{id}/recreateRecreate VM (destructive)
PUT/api/vps/v1/virtual-machines/{id}/hostnameSet hostname
DELETE/api/vps/v1/virtual-machines/{id}/hostnameReset hostname
PUT/api/vps/v1/virtual-machines/{id}/root-passwordSet root password
PUT/api/vps/v1/virtual-machines/{id}/panel-passwordSet panel password
PUT/api/vps/v1/virtual-machines/{id}/nameserversSet nameservers
GET/api/vps/v1/virtual-machines/{id}/metricsGet metrics
GET/api/vps/v1/virtual-machines/{id}/public-keysGet attached SSH keys
GET/api/vps/v1/virtual-machines/{id}/actionsGet action history
GET/api/vps/v1/virtual-machines/{id}/actions/{actionId}Get action details

Docker Manager (experimental)

MethodEndpointDescription
GET.../dockerList projects
POST.../dockerCreate project
GET.../docker/{name}Get project contents
GET.../docker/{name}/containersGet containers with stats
GET.../docker/{name}/logsGet project logs (last 300)
POST.../docker/{name}/startStart project
POST.../docker/{name}/stopStop project
POST.../docker/{name}/restartRestart project
POST.../docker/{name}/updateUpdate project
DELETE.../docker/{name}/downDelete project (irreversible)

Firewall

MethodEndpointDescription
GET/api/vps/v1/firewallList firewalls
POST/api/vps/v1/firewallCreate firewall
GET/api/vps/v1/firewall/{id}Get firewall details
DELETE/api/vps/v1/firewall/{id}Delete firewall
POST/api/vps/v1/firewall/{id}/rulesCreate rule
PUT/api/vps/v1/firewall/{id}/rules/{ruleId}Update rule
DELETE/api/vps/v1/firewall/{id}/rules/{ruleId}Delete rule
POST/api/vps/v1/firewall/{id}/activate/{vmId}Activate on VM
POST/api/vps/v1/firewall/{id}/deactivate/{vmId}Deactivate on VM
POST/api/vps/v1/firewall/{id}/sync/{vmId}Sync rules to VM

SSH Keys, Templates, Scripts, Backups, Snapshots, Recovery, PTR, Malware

MethodEndpointDescription
GET/POST/DELETE/api/vps/v1/public-keysManage SSH keys
POST/api/vps/v1/public-keys/attach/{vmId}Attach keys to VM
GET/api/vps/v1/templatesList OS templates
GET/api/vps/v1/templates/{id}Get template details
GET/POST/PUT/DELETE/api/vps/v1/post-install-scriptsManage scripts
GET/api/vps/v1/data-centersList data centers
GET.../backupsList backups
POST.../backups/{id}/restoreRestore backup
GET/POST/DELETE.../snapshotManage snapshot
POST.../snapshot/restoreRestore snapshot
POST/DELETE.../recoveryStart/stop recovery mode
POST/DELETE.../ptr/{ipId}Manage PTR records
GET/POST/DELETE.../monarxManage malware scanner

Best Practices

Security

  • Always attach SSH keys and disable password auth when possible
  • Configure firewalls — default drops all traffic, add only needed ports
  • Sync firewalls after any rule change — changes don't auto-apply
  • Only one firewall per VM — plan rules in a single firewall
  • Install Monarx malware scanner on production servers
  • Use strong passwords (12+ chars, mixed case, numbers, not leaked)

Backups & Recovery

  • Take a snapshot before destructive operations (recreate, major changes)
  • Remember: creating a new snapshot overwrites the existing one
  • Backup restores overwrite all data on the VM
  • Use recovery mode for filesystem repair — original disk is at /mnt

Docker

  • Docker Manager endpoints are experimental — expect changes
  • GitHub URLs auto-resolve to docker-compose.yaml in master branch
  • Deploying a project with an existing name replaces it
  • Use logs endpoint for debugging container issues

Performance

  • Monitor metrics to right-size your VPS plan
  • Set custom nameservers only if you know what you're doing — wrong config breaks DNS resolution

Post-Install Scripts

  • Maximum script size: 48KB
  • Script runs as /post_install, output goes to /post_install.log
  • Test scripts on non-production VMs first

Troubleshooting

VM Not Starting

  • Check action history for error details
  • VM may be in recovery mode — stop recovery first
  • Check if VM is in initial state — run setup first

Cannot SSH Into VM

  • Verify SSH key is attached (not just in account)
  • Check firewall allows port 22
  • Verify firewall is synced after rule changes
  • Try root password login to diagnose

Firewall Rules Not Taking Effect

  • Rules require manual sync after changes: POST .../firewall/{id}/sync/{vmId}
  • Only one firewall can be active per VM
  • Default policy is DROP — ensure accept rules exist for needed ports

Docker Project Not Starting

  • Check project logs: GET .../docker/{name}/logs
  • Verify docker-compose.yaml is valid
  • Ensure required ports are not already in use
  • Check VM has enough resources (CPU, RAM, disk)

Password Rejected During Recreate

  • Must be 12+ characters with uppercase, lowercase, and numbers
  • Password is checked against leaked password databases
  • Try a completely unique, complex password

Action Stuck in Progress

  • Poll action status: GET .../actions/{actionId}
  • Some operations take several minutes (recreate, backup restore)
  • If stuck for extended time, contact support

See Also

The following deep-dive guides are available in this skill directory:

  • deployment-workflow.md — SSH-first deployment workflow for Dockerized apps (7-step process, rollback strategy, verification levels)
  • docker-patterns.md — Docker Compose deployment patterns (WordPress, Node+Redis+Postgres, Traefik SSL, lifecycle management)
  • firewall-patterns.md — Common firewall configurations (web server, database, Docker host, mail server, TypeScript/PHP examples)
  • terraform-examples.md — Infrastructure as Code with the Hostinger Terraform Provider (VPS provisioning, SSH keys, firewalls, complete infra example)

References

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.