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 arjunprabhulal/devops-skills --skill dns-managementgit clone --depth 1 https://github.com/arjunprabhulal/devops-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/arjunprabhulal/devops-skills/dns-management)<a href="https://agentmods.dev/skills/arjunprabhulal/devops-skills/dns-management"><img src="https://agentmods.dev/badge/skills/arjunprabhulal/devops-skills/dns-management.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.00116 | $0.01414 |
| Opus 5 | $0.00058 | $0.00707 |
| Sonnet 5 | $0.00023 | $0.00283 |
| Haiku 4.5 | $0.00012 | $0.00141 |
Grade A, and why
dns-management 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 8d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DNS Management
DNS is the layer everyone forgets is a distributed system until it breaks one. A record change doesn't take effect atomically everywhere — it propagates through a chain of caching resolvers, each honoring a TTL you set, and a large share of "the whole platform is down" incidents turn out to be a single wrong record or an expired zone, not the application at all.
Treat every DNS change like a deploy: plan the rollout, control the blast radius with TTL, and have a way to verify it landed before you call it done. DNS is infrastructure with its own deploy pipeline — changes have propagation lag and no instant rollback.
1. Pick the record type for what's actually being pointed at
A/AAAA records point a name directly at an IP; CNAME points a name at another name and
cannot coexist with other records on the same label; ALIAS/ANAME (provider-specific) give
CNAME-like flexibility at a zone apex where CNAME is disallowed. Getting this wrong is the most
common reason a root domain can't point at a load balancer with a rotating IP.
- Zone apex records (
example.com, notwww.example.com) generally cannot be aCNAMEper the DNS spec — use an apex-capable alias feature or anArecord with a stable IP. MXandTXTcarry mail routing and verification/SPF/DKIM data — breaking these silently breaks email deliverability, not uptime, so they're easy to overlook in a network review.NSdelegation determines who is authoritative for a subdomain; a staleNSrecord points queries at a name server that no longer answers for that zone.
Done when: every record's type matches what it points at, and the zone apex resolves without
relying on CNAME.
2. Use TTL as a deliberate lever, not a fixed default
A long TTL (hours) reduces query load and is fine for stable records, but it means a mistake or an emergency failover takes that long to fully propagate through every caching resolver on the internet. A short TTL (minutes) costs more queries but buys fast rollback. The move is to lower TTL before a planned cutover and raise it again once the new value has proven stable.
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.
- 8d ago First seen · 105 lines · 116 tokens per session scan A 2bbc66abd4f2
dns-management is a skill published in the GitHub repository arjunprabhulal/devops-skills (3 stars, last pushed 13d ago), licensed MIT. It adds 116 tokens to every session and 1,414 once invoked, about $0.0006 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
google-cloud-solution-guided-gke-ai-migration
Guides the migration of existing AI workloads (Cloud Run, Gemini API, Gemini Enterprise Agent Platform) to self-hosted GKE inference using gcloud and kubectl. Use when the user has an existing AI inference workload (on Cloud Run, the Gemini API, Gemini Enterprise Agent Platform, or a custom VM) and wants to move it to…
agent-platform-tuning
Agent Platform Model Tuning. Use when you need to fine-tune open models or Gemini models using Agent Platform infrastructure. Don't use for model training outside Agent Platform, model deployment to endpoints (use agent-platform-deploy), or managing serving endpoints (use agent-platform-endpoint-management).
agent-platform-deploy
Deploy open models or custom weights from Model Garden to Agent Platform endpoints, check the status of an in-progress deployment operation, or clean up resources by undeploying models and deleting endpoints. Use when asked to actively deploy a model, list the Model Garden CATALOG of available models, check if a…
cloud-logging-cross-project-configuration
Configure and troubleshoot Google Cloud cross-project centralized logging and read-time aggregation. Use when: - Setting up log routing from multiple projects/folders/organizations to a central log bucket. - Creating cross-project log sinks and configuring central log buckets. - Troubleshooting cross-project routing.…
gke-alert-configuration
Configures alerting policies in Terraform for Google Kubernetes Engine (GKE) clusters, workloads, and services using PromQL and Google Cloud Managed Service for Prometheus. Use when writing, analyzing, validating, or deploying Terraform alerting policies to monitor GKE service latency, traffic, error rates using…
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…