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/reachnpx skills add hostinger/hostinger-agent-skills --skill reachgit 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/reach)<a href="https://agentmods.dev/skills/hostinger/hostinger-agent-skills/reach"><img src="https://agentmods.dev/badge/skills/hostinger/hostinger-agent-skills/reach.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.00049 | $0.02205 |
| Opus 5 | $0.00024 | $0.01103 |
| Sonnet 5 | $0.00010 | $0.00441 |
| Haiku 4.5 | $0.00005 | $0.00220 |
Grade A, and why
reach 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 5d 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/reach/v1/contacts" \ How it starts
The opening of the file, as written. The whole thing — 264 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hostinger Reach (Email Marketing)
The Reach API provides email marketing capabilities — managing contacts, creating segments for targeted campaigns, and working with sender profiles.
Table of Contents
Core Concepts
Contacts
Contacts are email recipients in your marketing system. Each contact has basic information (name, email, surname) and a subscription status. If double opt-in is enabled, new contacts start with a pending status and receive a confirmation email.
Segments
Segments group contacts based on specific criteria (email, name, subscription status, engagement metrics, etc.). Segments support complex filtering with operators like equals, contains, gte, lte, opened, clicked, etc.
Profiles
Sender profiles represent the email identity used to send campaigns. Each profile has basic information and is associated with your account.
Contact Groups
Groups are a way to organize contacts (deprecated in favor of segments).
Subscription Status
Contacts can have different subscription statuses that determine whether they receive emails. Status can be used as a filter when listing contacts.
Common Patterns
Create and Manage Contacts
# Create a new contact (direct)
curl -X POST "https://developers.hostinger.com/api/reach/v1/contacts" \
-H "Authorization: Bearer $HOSTINGER_API_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"email": "[email protected]",
"name": "John",
"surname": "Doe",
"phone": "+15551234567",
"note": "Met at conference"
}'
# Create a new contact (scoped to a specific sender profile)
curl -X POST "https://developers.hostinger.com/api/reach/v1/profiles/{profileUuid}/contacts" \
-H "Authorization: Bearer $HOSTINGER_API_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"email": "[email protected]",
"name": "John",
"surname": "Doe"
}'
# List contacts (paginated)
curl -X GET "https://developers.hostinger.com/api/reach/v1/contacts?page=1" \
-H "Authorization: Bearer $HOSTINGER_API_TOKEN"
# Filter contacts by subscription status
curl -X GET "https://developers.hostinger.com/api/reach/v1/contacts?subscription_status=active" \
-H "Authorization: Bearer $HOSTINGER_API_TOKEN"
# List contact groups
curl -X GET "https://developers.hostinger.com/api/reach/v1/contacts/groups" \
-H "Authorization: Bearer $HOSTINGER_API_TOKEN"
# Delete a contact
curl -X DELETE "https://developers.hostinger.com/api/reach/v1/contacts/{uuid}" \
-H "Authorization: Bearer $HOSTINGER_API_TOKEN"
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.
- 5d ago First seen · 264 lines · 49 tokens per session scan A 3fb33041c682
reach is a skill published in the GitHub repository hostinger/hostinger-agent-skills (21 stars, last pushed 2mo ago), licensed MIT. It adds 49 tokens to every session and 2,205 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.
new-service
Add a new service to Harbor — scaffold the compose config, environment variables, metadata, documentation, and cross-service integrations. Use this skill whenever the user wants to add a new service to Harbor, integrate a new tool/app/model server, create a compose configuration for a new project, or onboard any…
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.
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.