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 Goodsmileduck/claude-registry --skill cloudflare-dns-zonesgit clone --depth 1 https://github.com/Goodsmileduck/claude-registryWrote 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/goodsmileduck/claude-registry/cloudflare-dns-zones)<a href="https://agentmods.dev/skills/goodsmileduck/claude-registry/cloudflare-dns-zones"><img src="https://agentmods.dev/badge/skills/goodsmileduck/claude-registry/cloudflare-dns-zones/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/goodsmileduck/claude-registry/cloudflare-dns-zones"><img src="https://agentmods.dev/badge/skills/goodsmileduck/claude-registry/cloudflare-dns-zones.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.00136 | $0.04553 |
| Opus 5 | $0.00068 | $0.02277 |
| Sonnet 5 | $0.00027 | $0.00911 |
| Haiku 4.5 | $0.00014 | $0.00455 |
Grade A, and why
cloudflare-dns-zones 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 10d 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.
description: Operates Cloudflare DNS zones and records via the REST API (curl + jq) — token scoping, zone discovery, record CRUD, batch operations, BIND import/export, proxied vs DNS-only decisions, CNAME flattening at a How it starts
The opening of the file, as written. The whole thing — 370 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cloudflare DNS Zones
Operational skill for managing Cloudflare DNS through the REST API. Not for Terraform — see the Cloudflare provider docs if IaC is wanted. This skill focuses on the API directly (curl + jq), which is the source of truth every wrapper is built on.
When to invoke
Symptoms:
- Need to add, update, or audit DNS records via script/CI rather than the dashboard.
- A record was switched to proxied (orange cloud) and a non-HTTP service stopped working.
- DNS-01 ACME challenges fail despite a token that "should have permission."
- Bulk record migration into or out of Cloudflare (BIND zone file in hand).
- DKIM, SPF, DMARC TXT records being authored and the long-string semantics matter.
- DNSSEC handoff to the parent registrar.
- The token in use is the deprecated Global API Key.
Cross-cutting rules
- Never use the Global API Key. It's account-wide and can't be scoped. Use API Tokens (Profile → API Tokens). Every example below uses
Authorization: Bearer $CLOUDFLARE_API_TOKEN— the same variable wrangler, thecfCLI, and the official SDK read, so one export serves every Cloudflare tool. - Scope tokens to the minimum. A token for DNS work needs
Zone:Read+Zone:DNS:Editon the specific zones it operates. Not "All Zones" unless the workload genuinely touches all zones. - Discover zone IDs at runtime. Hard-coding zone IDs in scripts is brittle — they change when zones are recreated. Look them up by name on each run.
- Idempotent operations require list-then-act. There is no "upsert by name+type" endpoint. Always
GETfiltered bynameandtypefirst, thenPOST(create) orPATCH(update by ID). - Verify proxiability before setting
proxied: true. Only HTTP-serving hostnames should be proxied. See proxied vs DNS-only.
API basics
Base URL: https://api.cloudflare.com/client/v4
Auth header: Authorization: Bearer $CLOUDFLARE_API_TOKEN
Response envelope: every endpoint returns:
What ships with it
3 files 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.
- 10d ago First seen · 370 lines · 136 tokens per session scan A 803a2ed67df4
cloudflare-dns-zones is a skill published in the GitHub repository Goodsmileduck/claude-registry (1 stars, last pushed 1mo ago), licensed MIT. It adds 136 tokens to every session and 4,553 once invoked, about $0.0007 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-31.
Other skills, from other repositories
devops-best-practices
Opinionated production-grade DevOps defaults for Terraform, Kubernetes, CI/CD, Docker, cloud security, observability, cost, and disaster recovery. ALWAYS use when generating, reviewing, or modifying any infrastructure code, Kubernetes manifests (Deployment, Service, StatefulSet, Helm, Kustomize), Terraform (.tf…
cloudflare-temporary-deploy
Deploy a Worker live, no account, via wrangler --temporary.
tensorrt-llm
High-throughput LLM inference on NVIDIA GPUs.
stripe-projects
Provision SaaS services + sync creds via Stripe Projects.
cloud-sync
Set up or check claude-mem cloud sync with cmem.ai Pro. Use when the user says "set up cloud sync", "sync my memories", "cmem pro", "cloud backup", "sync status", or wants their memory database backed up or synced to their cmem.ai account.
cli-backup-sync
Backup and restore OmniRoute data from the CLI. Trigger incremental snapshots, sync to cloud storage, manage backup schedules, and restore from archive files.