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/floomhq/moto/dnsnpx skills add floomhq/moto --skill dnsgit clone --depth 1 https://github.com/floomhq/motoWrote 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/floomhq/moto/dns)<a href="https://agentmods.dev/skills/floomhq/moto/dns"><img src="https://agentmods.dev/badge/skills/floomhq/moto/dns.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.00059 | $0.00706 |
| Opus 5 | $0.00030 | $0.00353 |
| Sonnet 5 | $0.00012 | $0.00141 |
| Haiku 4.5 | $0.00006 | $0.00071 |
Grade A, and why
dns 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 5d 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.
curl -s -H "X-API-Key: $DNS_API_KEY" "$DNS_API_BASE" | jq '.[] | {name, id}' What it actually says
DNS Management
Auth
# Set your DNS provider API key
DNS_API_KEY="<YOUR_DNS_API_KEY>"
DNS_API_BASE="<YOUR_DNS_API_BASE_URL>" # e.g., https://api.hosting.ionos.com/dns/v1/zones
Header: X-API-Key: $DNS_API_KEY (or Authorization: Bearer $DNS_API_KEY depending on provider)
Known Zone IDs
| Domain | Zone ID |
|---|---|
| example.com | <ZONE_ID> |
Operations
List all zones (find zone ID)
curl -s -H "X-API-Key: $DNS_API_KEY" "$DNS_API_BASE" | jq '.[] | {name, id}'
List records for a zone
curl -s -H "X-API-Key: $DNS_API_KEY" "$DNS_API_BASE/{zoneId}" | jq '.records[] | {name, type, content, id}'
# Filter by type:
curl -s -H "X-API-Key: $DNS_API_KEY" "$DNS_API_BASE/{zoneId}?recordType=A"
Add record
curl -s -X POST \
-H "X-API-Key: $DNS_API_KEY" \
-H "Content-Type: application/json" \
-d '[{"name":"sub.domain.com","type":"A","content":"1.2.3.4","ttl":3600}]' \
"$DNS_API_BASE/{zoneId}/records"
Update record (need record ID first)
curl -s -X PUT \
-H "X-API-Key: $DNS_API_KEY" \
-H "Content-Type: application/json" \
-d '{"content":"1.2.3.4","ttl":3600}' \
"$DNS_API_BASE/{zoneId}/records/{recordId}"
Delete record
curl -s -X DELETE \
-H "X-API-Key: $DNS_API_KEY" \
"$DNS_API_BASE/{zoneId}/records/{recordId}"
Workflow
- If zone ID unknown: list zones, find matching domain
- List existing records for the zone
- Add / update / delete as needed
- Verify:
dig sub.domain.com @8.8.8.8(propagation takes 1-5 min)
Common Record Types
| Type | Use case | Example content |
|---|---|---|
| A | IPv4 | 93.184.216.34 |
| CNAME | Alias | cname.vercel-dns.com |
| TXT | Verification, SPF | "v=spf1 include:..." |
| MX | 10 smtp.example.com |
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.
- 5d ago First seen · 85 lines · 59 tokens per session scan A c17e585b65bc
dns is a skill published in the GitHub repository floomhq/moto (32 stars, last pushed 2mo ago), licensed MIT. It adds 59 tokens to every session and 706 once invoked, about $0.0003 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
moai-platform-deployment
Deployment and hosting platform specialist covering Vercel, Railway, and Convex. Use when deploying applications, configuring edge functions, setting up continuous deployment, or managing serverless infrastructure.
moai-platform-database-cloud
Cloud database platform specialist covering Neon (serverless PostgreSQL), Supabase (PostgreSQL 16 with real-time), and Firebase Firestore (NoSQL with offline sync). Use when choosing or setting up cloud databases.
deploy
Deploy an application to a configured environment.
architect
Architectural decision advisor for cloud, data, and SaaS distributed systems. Use when the user asks "should we use X or Y", weighs a tradeoff, or needs a decision matrix, scaling analysis, cost-at-scale review, data-tier design, multi-tenancy model, or API/resilience guidance. For full technical blueprints, use…
cloud-security
Rigorous security and data privacy scan for cloud deployments. Covers GCP infrastructure hardening, data privacy (PII/GDPR/CCPA), API security, container security, and compliance. Audits deployed infrastructure and config — not a code-diff review.
deploy
Deploy the project to a hosting platform. Detects deployment configuration, runs pre-deploy checks, and guides first-time setup.