hostinger
Skill38 starsChanged 8 months agoMITView on GitHub
Manage Hostinger domains, DNS, hosting, subscriptions and VPS via REST API
In this repository36 other files it gives its agents.
- abacatepaySkill
- appsignalSkill
- clickupSkill
- cloudflareSkill
- cloudinarySkill
- datadogSkill
- digitaloceanSkill
- discordSkill
- firebaseSkill
- flyioSkill
- google-sheetsSkill
- herokuSkill
- honeybadgerSkill
- hubspotSkill
- intercomSkill
- jiraSkill
- linearSkill
- mercadopagoSkill
- n8nSkill
- notionSkill
- openaiSkill
- planetscaleSkill
- posthogSkill
- railwaySkill
- resendSkill
- rewriteSkill
- sentrySkill
- shopifySkill
- slackSkill
- stripeSkill
- supabaseSkill
- trelloSkill
- twilioSkill
- vercelSkill
- xSkill
- zendeskSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 42
If the output is OK, proceed to the Flow section.
- Very specific: line 44
If the output is SETUP_NEEDED, guide the user step by step.
- Distinctive: line 61
If the script outputs an error, the token is invalid.
≈ “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.
Files
/hostinger
Connect to Hostinger to manage domains, DNS records, hosting websites, subscriptions and VPS data centers. Pure Ruby, zero gems — stdlib only.
Structure
scripts/
├── auth.rb # Bearer token auth + hostinger_request helper (required by all scripts)
├── check_setup.rb # Check if token exists (outputs OK or SETUP_NEEDED)
├── save_token.rb # Save and validate an API token
├── domains.rb # List all domains in portfolio
├── domain.rb # Get domain details
├── domain_availability.rb # Check domain availability across TLDs
├── nameservers.rb # Update domain nameservers
├── domain_lock.rb # Enable/disable domain lock
├── privacy.rb # Enable/disable WHOIS privacy protection
├── dns_records.rb # List DNS records for a domain
├── dns_update.rb # Update DNS records
├── dns_delete.rb # Delete DNS records
├── dns_snapshots.rb # List DNS snapshots
├── dns_restore.rb # Restore a DNS snapshot
├── websites.rb # List hosting websites
├── subscriptions.rb # List subscriptions
├── catalog.rb # List catalog items available for order
└── vps_datacenters.rb # List available VPS data centersSetup (check before using)
ruby ~/.claude/skills/hostinger/scripts/check_setup.rbIf the output is OK, proceed to the Flow section.
If the output is SETUP_NEEDED, guide the user step by step. Present ONE step at a time, wait for the user to confirm before moving to the next.
Step 1 — Ask the user to create an API token:
You need a Hostinger API token. Go to your Hostinger panel:
hPanel > Account > API Tokens
Create a new token with the permissions you need (domains, DNS, hosting, billing). Copy the token and paste it here.
Step 2 — When the user pastes the token, save it:
ruby ~/.claude/skills/hostinger/scripts/save_token.rb 'PASTED_TOKEN'If the script outputs an error, the token is invalid. Ask the user to double-check and try again.
If setup is not complete, DO NOT proceed to the Flow. Complete all steps first.
Flow
The argument $ARGUMENTS may contain a domain name.
Step 1: Overview
ruby ~/.claude/skills/hostinger/scripts/domains.rbPresent the domains. If $ARGUMENTS matches a domain, use it. Otherwise ask what the user wants to do.
Step 2: Actions
Get domain details:
ruby ~/.claude/skills/hostinger/scripts/domain.rb example.comCheck domain availability:
ruby ~/.claude/skills/hostinger/scripts/domain_availability.rb mysite com net ioUpdate nameservers (requires user confirmation):
ruby ~/.claude/skills/hostinger/scripts/nameservers.rb example.com ns1.example.com ns2.example.comEnable/disable domain lock (requires user confirmation):
ruby ~/.claude/skills/hostinger/scripts/domain_lock.rb example.com --enable
ruby ~/.claude/skills/hostinger/scripts/domain_lock.rb example.com --disableEnable/disable WHOIS privacy (requires user confirmation):
ruby ~/.claude/skills/hostinger/scripts/privacy.rb example.com --enable
ruby ~/.claude/skills/hostinger/scripts/privacy.rb example.com --disableList DNS records:
ruby ~/.claude/skills/hostinger/scripts/dns_records.rb example.comUpdate DNS records (requires user confirmation):
ruby ~/.claude/skills/hostinger/scripts/dns_update.rb example.com '[{"type":"A","name":"@","content":"1.2.3.4","ttl":3600}]'Delete DNS records (requires user confirmation):
ruby ~/.claude/skills/hostinger/scripts/dns_delete.rb example.com '[{"type":"A","name":"@","content":"1.2.3.4"}]'List DNS snapshots:
ruby ~/.claude/skills/hostinger/scripts/dns_snapshots.rb example.comRestore a DNS snapshot (requires user confirmation):
ruby ~/.claude/skills/hostinger/scripts/dns_restore.rb example.com SNAPSHOT_IDList hosting websites:
ruby ~/.claude/skills/hostinger/scripts/websites.rbList subscriptions:
ruby ~/.claude/skills/hostinger/scripts/subscriptions.rbList catalog items:
ruby ~/.claude/skills/hostinger/scripts/catalog.rb
ruby ~/.claude/skills/hostinger/scripts/catalog.rb --category hostingList VPS data centers:
ruby ~/.claude/skills/hostinger/scripts/vps_datacenters.rbNotes
- Pure Ruby, zero gems — stdlib only (json, net/http, uri, fileutils)
- Auth via Bearer token
- Token file:
~/.config/hostinger/token(outside the repo, never commit) - Updating nameservers, DNS records, domain lock, privacy, and restoring snapshots require explicit user confirmation
- Rate limit enforced by Hostinger (HTTP 429 when exceeded)
- Base URL:
https://developers.hostinger.com
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
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.

