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 01-check-stategit 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/01-check-state)<a href="https://agentmods.dev/skills/hostinger/api-mcp-server/01-check-state"><img src="https://agentmods.dev/badge/skills/hostinger/api-mcp-server/01-check-state/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/01-check-state"><img src="https://agentmods.dev/badge/skills/hostinger/api-mcp-server/01-check-state.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.00102 | $0.03021 |
| Opus 5.5 | $0.00041 | $0.01208 |
| Sonnet 5.5 | $0.00020 | $0.00604 |
| Haiku 4.5 | $0.00010 | $0.00302 |
Grade A, and why
headless-step-check-state 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 yesterday.
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 — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
headless-step-check-state
The first build step of the Hostinger Headless flow (orchestrated by hostinger.com/headless/skill.md),
run right after connect. Connect has already connected the Hostinger connector and confirmed the
account can build. Your job here is to
figure out where this domain stands and agree the route with the user before any new work begins.
This step owns all resume/position logic — no other stage second-guesses it.
Nothing in this step creates, provisions, deploys, or deletes anything. It reads and guides.
Where state lives
Everything for a domain lives under the global site workspace ~/.hostinger/<domain>/ — one
directory per domain, under the user's home (~ = $HOME), not the current working directory.
The directory name is the domain, so state.json inside does not store it. Because it's global,
~/.hostinger/ holds every site the user has built and each one is discoverable and resumable from
any directory — no collisions.
state.json shape (stage is the next stage to run; provision is the background task's status,
present only once provision has fired):
{ "tool": "claude-code", "stage": "content_model",
"provision": { "status": "in_progress", "domain": "<domain>", "started_at": "…" },
"updated_at": "…" }
provision.status is in_progress or completed — but it is a hint: always re-verify it against
hosting_websites_list-setups (Step 1) before trusting it to gate an instance-barrier step.
Step 0 — Start the run log
Before anything else, start a run and the stage (see Run log and build report in the top-level
SKILL.md):
node <skill>/run-log.mjs <domain> run-start --tool <tool> --model <model> --skill <skill version>
node <skill>/run-log.mjs <domain> stage-start check_state
If an earlier run on this domain never wrote its report, run-start closes it as abandoned first.
Then send any build reports that haven't reached Hostinger yet (that abandoned run, or a send that failed last time):
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.
- yesterday First seen · 210 lines · 102 tokens per session scan A 4ce8632b184b
headless-step-check-state is a skill published in the GitHub repository hostinger/api-mcp-server (163 stars, last pushed yesterday), licensed MIT. It adds 102 tokens to every session and 3,021 once invoked, about $0.0004 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
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
track-management
Use this skill when creating, managing, or working with Conductor tracks - the logical work units for features, bugs, and refactors. Applies to spec.md, plan.md, and track lifecycle operations.
feature-decision
Framework for making feature prioritization decisions.
feedback-page-generator
Deprecated compatibility entry for Feedback Page construction. This page is now maintained in Pagina; install and use page-builder to build a new Feedback Page.
status-page-generator
Deprecated compatibility entry for Status Page construction. This page is now maintained in Pagina; install and use page-builder to build a new Status Page.