Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add hostinger/api-mcp-server --skill migrate-to-hostinggit clone --depth 1 https://github.com/hostinger/api-mcp-serverWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/hostinger/api-mcp-server/migrate-to-hosting)<a href="https://agentmods.dev/skills/hostinger/api-mcp-server/migrate-to-hosting"><img src="https://agentmods.dev/badge/skills/hostinger/api-mcp-server/migrate-to-hosting/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/hostinger/api-mcp-server/migrate-to-hosting"><img src="https://agentmods.dev/badge/skills/hostinger/api-mcp-server/migrate-to-hosting.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00115 | $0.01775 |
| Opus 5.5 | $0.00046 | $0.00710 |
| Sonnet 5.5 | $0.00023 | $0.00355 |
| Haiku 4.5 | $0.00012 | $0.00178 |
Grade A, and why
migrate-to-hosting scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 16d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
2. Import the dump from this machine: allow only its public IP (`curl -s https://api.ipify.org`) with `hosting_databases_create-remote-connection`, run `mysql -h HOST -u USER -p NAME < db.sql`, then remove the rule with How it starts
The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migrate to hosting
The old host keeps serving the site until the copy on Hostinger is proven to work. DNS moves last.
Calling the operations
- Read the
inputSchemathatsearchreturns before the first call of each operation. If a name below is rejected as unknown,searchfor what the step does (e.g. "import wordpress"). - Batch reads with
multi-execute. Batches chain operations from one server only — the Hostinger Connector runshosting,wordpress,agency-hosting,domainsanddnsas separate servers. - Imports and deploys overwrite the target website's contents; confirm the target before each one.
1. What is being moved
Establish, asking only for what cannot be inferred:
- Site type: WordPress, static, PHP (with or without MySQL), or Node.js.
- The export:
- WordPress — an archive of the whole WordPress root (including
wp-contentandwp-config.php) and a.sqldump. - PHP — a files archive, plus a
.sqldump when the app has a database. - Static — the files. Node.js — the source or its Git repository.
- Without one, the user exports it from the old host's panel, or over SSH:
tar -czf site.tar.gz -C /path/to/site .andmysqldump --single-transaction -u USER -p DBNAME > db.sql.
- WordPress — an archive of the whole WordPress root (including
- The exact home URL (
https, with or withoutwww) — WordPress keeps it in the database, so the new site must answer on the same one. - Current DNS, to preserve what already works:
dig +short NS DOMAIN; dig +short A DOMAIN; dig +short MX DOMAIN; dig +short TXT DOMAIN
- Cron jobs on the old host — they do not move with the files.
2. Create the website on the real domain
Create the Hostinger website on the domain being migrated, not on a free subdomain: step 4 tests it by pointing only this machine at Hostinger, so nothing changes for visitors yet.
- Shared and Cloud:
hosting_domains_verify-ownershipfirst. Whenis_accessibleis false, the user adds the returnedTXTrecord at their current DNS provider, next to the existing ones, and verification is repeated. Thenhosting_websites_createwithdomainandorder_id(fromhosting_orders_list), and pollhosting_websites_list-setupswithdomainevery 10–15 s untilstatus: completed. - Agency:
agency-hosting_website-setups_createwith thedomain,flavor: "php-fpm", asettings.php.versionmatching the old host (options inagency-hosting_php_list-versions-for-order) anddatacenter_codefromagency-hosting_datacenters_list. Pollagency-hosting_website-setups_statusuntilcompletedfor thewebsite_uid.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 16d ago First seen · 81 lines · 115 tokens per session scan A db36bfe57307
migrate-to-hosting is a skill published in the GitHub repository hostinger/api-mcp-server (163 stars, last pushed yesterday), licensed MIT. It adds 115 tokens to every session and 1,775 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-01.
Other skills, from other repositories
linkerd-patterns
Implement Linkerd service mesh patterns for lightweight, security-focused service mesh deployments. Use when setting up Linkerd, configuring traffic policies, or implementing zero-trust networking with minimal overhead.
cost-optimization
Optimize cloud costs across AWS, Azure, GCP, and OCI through resource rightsizing, tagging strategies, reserved instances, and spending analysis. Use when reducing cloud expenses, analyzing infrastructure costs, or implementing cost governance policies.
istio-traffic-management
Configure Istio traffic management including routing, load balancing, circuit breakers, and canary deployments. Use when implementing service mesh traffic policies, progressive delivery, or resilience patterns.
mirrord-prev-env
Help users create and manage mirrord preview environments — running a modified service as an isolated pod in a shared Kubernetes cluster, scoped by an environment key and HTTP/queue traffic filtering, so teams can validate and review changes against real traffic without affecting live services. Use when a developer…
mirrord-operator
Help users install and configure the mirrord Operator for team/enterprise environments. Use when users ask about operator setup, Helm installation, cloud API key or license configuration, air-gapped/offline licensing, enabling features (queue splitting, DB branching, preview environments, multi-cluster), internal…
mirrord-up
Helps users run multiple concurrent mirrord sessions from a single mirrord-up.yaml (compose-style multi-service local debugging). Use when the user mentions mirrord up, mirrord-up.yaml, mirrord up init, debugging several related microservices together, or managing multiple mirrord sessions' lifecycle in one command.