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/steipete/agent-scripts/domain-dns-opsnpx skills add steipete/agent-scripts --skill domain-dns-opsgit clone --depth 1 https://github.com/steipete/agent-scriptsWrote 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/steipete/agent-scripts/domain-dns-ops)<a href="https://agentmods.dev/skills/steipete/agent-scripts/domain-dns-ops"><img src="https://agentmods.dev/badge/skills/steipete/agent-scripts/domain-dns-ops.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 | $0.00025 | $0.00729 |
| Opus 5 | $0.00013 | $0.00365 |
| Sonnet 5 | $0.00005 | $0.00146 |
| Haiku 4.5 | $0.00003 | $0.00073 |
Grade A, and why
domain-dns-ops 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 4d 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.
- HTTPS redirect: `curl -I https://example.com` (expect `301`). How it starts
The opening of the file, as written. The whole thing — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Domain/DNS Ops (Peter)
This skill is a thin router: use ~/Projects/manager as truth, run the repo scripts, follow the checklists.
Source of truth (read first)
~/Projects/manager/DOMAINS.md(domain -> target map; registrar hints; exclusions)~/Projects/manager/DNS.md(Cloudflare onboarding + DNS/redirect checklist)~/Projects/manager/redirect-worker.ts+~/Projects/manager/redirect-worker-mapping.md(worker redirects)
Golden path (new vanity domain -> Cloudflare -> redirect)
- Decide routing model
- Page Rule redirect (small scale, per-zone).
- Rulesets / Bulk Redirects (account-level; needs token perms).
- Worker route (fallback; uses
redirect-worker).
- Cloudflare zone
- Create zone (UI), then confirm with
cli4:cli4 --get name=example.com /zones
- Create zone (UI), then confirm with
- Nameservers
- If registrar = Namecheap:
cd ~/Projects/manager && source profile && bin/namecheap-set-ns example.com emma.ns.cloudflare.com scott.ns.cloudflare.com - If registrar = DNSimple: see
~/Projects/manager/DNS.mdfor delegation API notes.
- If registrar = Namecheap:
- DNS placeholders (so CF can terminate HTTPS)
- Proxied apex
A+ wildcardA→192.0.2.1(see~/Projects/manager/DNS.mdfor exactcli4calls).
- Proxied apex
- Redirect
- If using Page Rules: use the
cli4 --post ... /pagerulestemplate from~/Projects/manager/DNS.md. - If using Worker: update mapping (
~/Projects/manager/redirect-worker-mapping.md), deploy/bind routes per~/Projects/manager/DNS.md.
- If using Page Rules: use the
- Verify
- DNS:
dig +short example.com @1.1.1.1(expect CF anycast). - HTTPS redirect:
curl -I https://example.com(expect301).
- DNS:
Common ops
- Cloudflare token sanity: follow the root secret rule; export only the needed Cloudflare token for one command.
- Disable “Block AI bots”:
cd ~/Projects/manager && source profile && bin/cloudflare-ai-bots status/bin/cloudflare-ai-bots disable.
After edits (commit/push)
If you changed anything in ~/Projects/manager (docs, worker, scripts, mappings): commit there too.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 56 lines · 25 tokens per session scan A 85d96626b73b
domain-dns-ops is a skill published in the GitHub repository steipete/agent-scripts (6,596 stars, last pushed today), licensed MIT. It adds 25 tokens to every session and 729 once invoked, about $0.0001 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…