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 03-provisiongit 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/03-provision)<a href="https://agentmods.dev/skills/hostinger/api-mcp-server/03-provision"><img src="https://agentmods.dev/badge/skills/hostinger/api-mcp-server/03-provision/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/03-provision"><img src="https://agentmods.dev/badge/skills/hostinger/api-mcp-server/03-provision.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.00077 | $0.01920 |
| Opus 5.5 | $0.00031 | $0.00768 |
| Sonnet 5.5 | $0.00015 | $0.00384 |
| Haiku 4.5 | $0.00008 | $0.00192 |
Grade A, and why
headless-step-provision scanned grade A with 0 findings 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 8d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
headless-step-provision
Router. The backend is decided in refine and recorded in brief.md; this step only routes to the
matching subfolder, which provisions it.
In: brief.md. Out: site.json (written by the subfolder).
This stage runs in the background. Provisioning is mostly a poll wait, so it splits in two: a
fire half (detect + create, returns straight away) and a join half (poll to completed,
verify, write site.json). Fire it, record provision.in_progress, then go do the prepare work of
the other stages (content-model prepare, frontend shell) while it settles. Only cross back to
the join half when an instance-barrier step needs the live backend. See Background provision & the
instance barrier in the top-level SKILL.md. An agent that can't interleave simply does fire and
join back-to-back — still correct, just no overlap.
Step 1 — Route on the suggested backend
Read the brief's Suggested backend section:
| Suggested backend | Follow |
|---|---|
| WordPress | wordpress/SKILL.md |
| WordPress + WooCommerce | wordpress/SKILL.md with the WooCommerce store on (see below) |
| Ecommerce | ecommerce/SKILL.md |
| Webapp | webapp/SKILL.md |
If the section is missing or names something else, go back to refine — don't pick one here. Tell the user the backend and its one-line reason before provisioning.
WordPress + WooCommerce is the WordPress backend with a store — not a new backend. Route it to
wordpress/SKILL.mdand follow that recipe's optional WooCommerce tail (install + activate thewoocommerceplugin and verify the store endpoints; the catalog is seeded later through the per-site WP MCP's nativewc-*abilities — no custom plugin, no consumer key).site.json → backendstays"wordpress"; the store is recorded undersite.json → woocommerce(enabled: true). Everything else downstream that routes onwordpress(content-model push, deploy's/cmspreservation, done's wp-admin login) then works unchanged.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 118 lines · 77 tokens per session scan A 109661e94ce5
headless-step-provision is a skill published in the GitHub repository hostinger/api-mcp-server (164 stars, last pushed today), licensed MIT. It adds 77 tokens to every session and 1,920 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-20.
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.