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/vineetu/simple-host/connect-domainnpx skills add vineetu/simple-host --skill connect-domaingit clone --depth 1 https://github.com/vineetu/simple-hostWrote 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/vineetu/simple-host/connect-domain)<a href="https://agentmods.dev/skills/vineetu/simple-host/connect-domain"><img src="https://agentmods.dev/badge/skills/vineetu/simple-host/connect-domain.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.00108 | $0.01726 |
| Opus 5 | $0.00054 | $0.00863 |
| Sonnet 5 | $0.00022 | $0.00345 |
| Haiku 4.5 | $0.00011 | $0.00173 |
Grade A, and why
connect-domain 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 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.
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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Connect a Custom Domain
A site deployed on simple-host is already live at
https://sites.simple-host.app/<handle>/<site>/. This skill connects the user's own
domain — a subdomain (e.g. recipes.brand.com) or an apex (e.g. brand.com) — so the
site is served from it with automatic HTTPS.
This is agent-driven. You do every API call and compute the exact DNS record. Then either add that record yourself if you have DNS access for the domain (a provider MCP/API — see step 3b; ask permission first), or hand the human the single record to paste. Buying a domain (when they have none) and — absent your own DNS access — pasting the record are the only human steps.
When to use this
- The user asks to use their own domain / brand for a site.
- The user wants a private or password-locked page: privacy is a property of a connected domain (its own isolated origin), not of a path on the shared host. If they want privacy, connect a domain first.
Service
- Base URL:
https://simple-host.app - Auth header:
X-API-Key: <api_key>(the key from deploying the site) - One domain per site; a domain can be connected to only one site.
The flow
1. Confirm the site exists and pick the domain
The site must already be deployed. Ask the user for the exact domain they want.
Subdomains (recipes.brand.com) are the simplest path (CNAME). Apex domains
(brand.com) are fully supported too — the bind returns an A record instead of a
CNAME. Prefer a subdomain when the user has no strong preference; use apex when
they want the bare domain.
2. Bind the domain
POST /v1/sites/{site}/domain
X-API-Key: <api_key>
Content-Type: application/json
{ "domain": "recipes.brand.com" }
Response (subdomain example — CNAME):
{
"domain": "recipes.brand.com",
"status": "pending",
"dns": { "type": "CNAME", "host": "recipes.brand.com", "value": "cname.simple-host.app" }
}
For an apex (brand.com), dns.type is A and dns.value is the IP to point at —
relay whatever the response returns; don't invent the target.
409 means the domain is already connected to another site. 400 means the domain is
malformed or is one of our own hostnames.
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 · 142 lines · 108 tokens per session scan A 131ab6ab4438
connect-domain is a skill published in the GitHub repository vineetu/simple-host (1 stars, last pushed 6d ago), licensed MIT. It adds 108 tokens to every session and 1,726 once invoked, about $0.0005 per session on Opus 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-08-31.
Other skills, from other repositories
cloud-administration
Administers the cloud the company runs on rather than the one it sells — tenant and subscription structure, the SaaS estate and who owns each app, identity as the real perimeter, cloud spend that arrives as a surprise, and what the provider does not do for you. Use this to structure subscriptions or tenants, get…
network-administration
Designs and operates the corporate network — segmentation, remote access, wireless, DNS and addressing, and diagnosing network problems. Use this to segment a network, set up or fix remote access, diagnose intermittent connectivity, plan addressing or DNS, or assess whether the network's trust assumptions still hold.
telephony-and-conferencing
Runs voice and meeting infrastructure — phone systems and numbers, emergency calling obligations, conference rooms and their AV, call recording and its retention consequences, and the porting that makes provider changes go badly. Use this to replace a phone system, fix rooms nobody can start a meeting in, meet…
virtualization-operations
Runs the hypervisor layer beneath the servers — host capacity and consolidation ratios, VM sprawl, snapshot discipline, resilience and live migration, and licensing that counts cores rather than instances. Use this to size or expand a cluster, work out why VMs are slow when the hosts look idle, clean up sprawl, set…
business-continuity-and-resilience
Plans for operating through disruption — impact analysis, recovery objectives, continuity plans, and the exercises that prove they work. Use this to run a business impact analysis, set RTO and RPO, write or test a continuity plan, prepare for a supplier or site failure, or answer a customer's resilience questionnaire.
cloud-infrastructure
Designs and runs cloud infrastructure — environments, infrastructure as code, networking and isolation, scaling, and cost. Use this to design a cloud environment, control infrastructure spend, set up environment separation, plan for scale or region failure, or review infrastructure someone configured by hand.