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 digitalocean-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/digitalocean-dns-zones)<a href="https://agentmods.dev/skills/goodsmileduck/claude-registry/digitalocean-dns-zones"><img src="https://agentmods.dev/badge/skills/goodsmileduck/claude-registry/digitalocean-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/digitalocean-dns-zones"><img src="https://agentmods.dev/badge/skills/goodsmileduck/claude-registry/digitalocean-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.00142 | $0.02668 |
| Opus 5 | $0.00071 | $0.01334 |
| Sonnet 5 | $0.00028 | $0.00534 |
| Haiku 4.5 | $0.00014 | $0.00267 |
Grade A, and why
digitalocean-dns-zones 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 11d 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 — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DigitalOcean DNS Zones
Operational skill for managing DigitalOcean DNS through doctl, the REST API, and the Terraform provider. Covers the traps that appear most often when migrating zones in or out of Cloudflare — especially apex CNAME handling, trailing-dot semantics, and the account-wide token model that differs from Cloudflare's scoped tokens.
When to invoke
Symptoms:
- Apex hostname (
example.com) refuses to take a CNAME — the provider errors or the record silently misbehaves. - A Terraform CNAME resolves to a doubled FQDN like
api.example.com.example.com. - Need a wildcard cert (
*.example.com) with a DNS-01 ACME challenge on a DO-hosted zone. - Migrating a zone to or from Cloudflare and unsure which records need manual attention.
- Deciding whether to use doctl, the raw API, or the Terraform provider for a given task.
- Token handling for DO DNS in CI — needs guidance on secret management.
Cross-cutting rules
These rules apply to every section below. Read them before acting.
-
DIGITALOCEAN_ACCESS_TOKENis account-wide. Unlike Cloudflare, DigitalOcean has no zone-scoped token model. A token that can edit DNS can touch every domain in the account. Treat it as a high-value secret: store it in a secrets manager or CI secret, never echo it into shared shell history or CI logs. This is an explicit difference from thecloudflare-dns-zonesskill's "scope tokens to the minimum" rule — on DigitalOcean you cannot scope below the account level. -
Domain before records. A domain entry (
digitalocean_domainresource ordoctl compute domain create) must exist before any record can be added. There is no "lazy create." The apex record usesname = "@"in both doctl and Terraform. -
No apex CNAME, no flattening. DigitalOcean has no ALIAS, ANAME, or CNAME flattening. A bare apex (
example.com) must resolve to A or AAAA records. This is the most common trap when migrating from Cloudflare, which transparently flattens apex CNAMEs — that transparency disappears the moment you cut over nameservers to DO.
What ships with it
5 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.
- 11d ago First seen · 208 lines · 142 tokens per session scan A 50ba9c66f511
digitalocean-dns-zones is a skill published in the GitHub repository Goodsmileduck/claude-registry (1 stars, last pushed 1mo ago), licensed MIT. It adds 142 tokens to every session and 2,668 once invoked, about $0.0007 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
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.