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 erphq/skills --skill attach-domaingit clone --depth 1 https://github.com/erphq/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/erphq/skills/attach-domain)<a href="https://agentmods.dev/skills/erphq/skills/attach-domain"><img src="https://agentmods.dev/badge/skills/erphq/skills/attach-domain/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/erphq/skills/attach-domain"><img src="https://agentmods.dev/badge/skills/erphq/skills/attach-domain.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.00033 | $0.00790 |
| Opus 5.5 | $0.00013 | $0.00316 |
| Sonnet 5.5 | $0.00007 | $0.00158 |
| Haiku 4.5 | $0.00003 | $0.00079 |
Grade A, and why
attach-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 1mo 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.
This is a copy
88% identical to ai-chat — 40 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Attach Domain
What This Skill Does
Deploy and operate code on build.host. This specific recipe handles the user intent add app.example.com to nimbus and should end with: DNS instructions + automatic Let's Encrypt SSL on resolution.
The skill is meant for agents using the build.host API through the user's installed build.host credentials. It is not a marketing card and it is not a command alias. Treat it as an operating playbook.
When To Use
Use this skill when:
- The user asks for:
add app.example.com to nimbus. - The work matches these tags:
- dns
- ssl
- The expected output is a concrete change, deployed URL, patch, or verified setup, not a vague recommendation.
Do not use this skill when the user is only asking about build.host pricing, account support, or general product explanation. Answer those conversationally instead.
Required Context
Before taking action, establish:
- The project directory or git repository to operate on.
- The target branch, usually
mainunless the user says otherwise. - The desired build.host slug or project name.
- Any required environment variables, secrets, custom domains, or provider accounts.
- Whether the user wants an immediate production deploy or only a patch/preview.
Credentials must come from ~/.build-host/credentials.json or the authenticated build.host browser session. Never ask the user to put a build.host API key in source code, markdown, screenshots, or chat logs.
Operating Procedure
- create or find the project.
- configure build and runtime inputs.
- deploy or operate the current release.
- verify the live URL.
For deploy or runtime operations, prefer the build.host API exposed by the installed master skill:
- GET /api/projects
- POST /api/projects
- POST /api/projects/:uuid/deploy
- GET /api/projects/:uuid/deployments
- GET /api/projects/:uuid/logs
Safety Rules
- Never print API keys, OAuth tokens, database URLs, webhook secrets, or full env values.
- Confirm destructive actions such as deleting a project, replacing a domain, or rolling back production when impact is ambiguous.
- Keep generated files inside the user's project unless the user explicitly asks for global setup.
- Prefer the smallest working implementation over adding a new framework or provider.
- After a deploy, verify the returned URL with an HTTP check and report the final URL plainly.
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.
- 1mo ago First seen · 93 lines · 33 tokens per session scan A 3e051f54695c
attach-domain is a skill published in the GitHub repository erphq/skills (3 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 790 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 88% identical to ai-chat, differing in 40 lines, and is treated as a copy.
Other skills, from other repositories
kubernetes-docs
Draft, rewrite, or audit Kubernetes and cloud-native documentation using an independently expressed interpretation of Kubernetes documentation style. Use for concepts, tasks, tutorials, references, configuration, operations, and version-sensitive guidance involving clusters, workloads, APIs, kubectl, or Kubernetes…
deploy-to-production-safely
Use when a change is about to touch a running system. Backup, dry run, rollback and per-node verification, in that order.
aws-research
Research an AWS or Kiro question across community and first-party sources, then answer with citations. Use when a docs answer is missing or contradicts observed behaviour, when someone else has probably hit the same error, when the question is about Kiro itself (steering, hooks, specs, powers, MCP), when it concerns…
vegastack
Use when the user asks to write, debug, import, or migrate Terraform / HCL, or names any cloud / SaaS provider in a "deploy / provision / configure" context. Provides per-resource argument schemas, import-ID formats, deprecation flags, recent-change knowledge cards, cross-provider recipes, and recommended-companion…
cloud-deployment-shipyou
Use this skill when preparing an application for cloud deployment, containerization, Docker-based handoff, or ShipYou deployment readiness. This skill emphasizes portable containers, clean source bundles, health checks, environment configuration, production start commands, and safe deployment defaults.
cloud-deployment-shipyou
Use this skill when preparing an application for cloud deployment, containerization, Docker-based handoff, or ShipYou deployment readiness. This skill emphasizes portable containers, clean source bundles, health checks, environment configuration, production start commands, and safe deployment defaults.