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 agentmods add skills/hostinger/hostinger-agent-skills/horizonsnpx skills add hostinger/hostinger-agent-skills --skill horizonsgit clone --depth 1 https://github.com/hostinger/hostinger-agent-skillsWrote 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/hostinger-agent-skills/horizons)<a href="https://agentmods.dev/skills/hostinger/hostinger-agent-skills/horizons"><img src="https://agentmods.dev/badge/skills/hostinger/hostinger-agent-skills/horizons.svg" alt="Measured on agentmods" 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.00047 | $0.01347 |
| Opus 5 | $0.00023 | $0.00674 |
| Sonnet 5 | $0.00009 | $0.00269 |
| Haiku 4.5 | $0.00005 | $0.00135 |
Grade A, and why
horizons 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 6d 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.
curl -X POST "https://developers.hostinger.com/api/horizons/v1/websites" \ How it starts
The opening of the file, as written. The whole thing — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hostinger Horizons
Horizons is Hostinger's AI website builder. The API creates a website from a natural-language description and returns a link where the user can preview and edit it. Use it when a user asks to build a website, landing page, blog, or other web application, or to fetch an edit link for an existing Horizons site.
Table of Contents
Core Concepts
Prompt-Driven Creation
You describe the desired site in natural language (the message), and Horizons generates it. The create call returns a website URL and ID immediately, but generation happens asynchronously — the site is built in the background after the call returns.
Messages
The create request takes a message array of message objects. Each has a type (currently text) and the text describing what to build, e.g. "Create a landing page for a coffee shop with a hero section, menu, and contact form."
Editing in the Horizons Interface
Horizons websites can only be modified inside the Horizons web interface. To change an existing site, fetch its edit link with GET /websites/{websiteId} and open the returned URL — there is no direct content-editing API.
Common Patterns
Create a Website from a Prompt
curl -X POST "https://developers.hostinger.com/api/horizons/v1/websites" \
-H "Authorization: Bearer $HOSTINGER_API_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"message": [
{
"type": "text",
"text": "Create a landing page for a coffee shop with a hero section, menu, and contact form"
}
]
}'
Returns a website URL and ID right away; the site continues generating asynchronously. Share the URL with the user to watch progress and preview the result.
Python SDK:
from hostinger_api import Hostinger
client = Hostinger(api_token="YOUR_API_TOKEN")
site = client.horizons.websites.create(
message=[{"type": "text", "text": "Create a portfolio site for a photographer"}]
)
print(site.id, site.url)
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.
- 6d ago First seen · 157 lines · 47 tokens per session scan A 841d740200e0
horizons is a skill published in the GitHub repository hostinger/hostinger-agent-skills (21 stars, last pushed 2mo ago), licensed MIT. It adds 47 tokens to every session and 1,347 once invoked, about $0.0002 per session on Opus 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-08-30.
Other skills, from other repositories
windows-mcp-tool-tester
Automated testing skill for Windows-MCP tools. Use this skill whenever the user wants to test, validate, benchmark, or evaluate any Windows-MCP tool (App, PowerShell, Screenshot, Snapshot, Click, Type, Scroll, Move, Shortcut, Wait, MultiSelect, MultiEdit, Clipboard, Process, Notification, FileSystem, Registry…
facts-discover
Scan the codebase and classify every fact by lifecycle stage — tag @draft, @spec, or @implemented based on what the code actually shows. Add missing facts, fix inaccurate ones, remove obsolete ones. Use when asked to discover facts, bootstrap or update a fact sheet, scan the codebase for truths, sync facts to match…
anneal
Use when the user wants to systematically fix AI code slop — duplicated logic, over-engineering, silent error swallowing, convention drift, cargo-cult patterns, and other LLM-introduced architectural decay — over a specified duration.
bughunt
Fully autonomous bug hunting pipeline — discover bugs in a scoped area using parallel subagents, independently triage each finding, fix confirmed issues with subagents, then audit all fixes against repo constraints and target platforms. Runs end-to-end without user interaction.
timeboxed-iterating
Use when the user specifies a task and a duration, and the work should be done iteratively by subagents over that time period.
facts-implement
Operate on @spec facts — implement them in code, then tag @implemented. Use when asked to implement facts, implement the spec, build from the fact sheet, make facts true, or work through unimplemented requirements.