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 mailgun/mailgun-plugins --skill domain-onboarding-dns-verificationgit clone --depth 1 https://github.com/mailgun/mailgun-pluginsWrote 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/mailgun/mailgun-plugins/domain-onboarding-dns-verification)<a href="https://agentmods.dev/skills/mailgun/mailgun-plugins/domain-onboarding-dns-verification"><img src="https://agentmods.dev/badge/skills/mailgun/mailgun-plugins/domain-onboarding-dns-verification/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/mailgun/mailgun-plugins/domain-onboarding-dns-verification"><img src="https://agentmods.dev/badge/skills/mailgun/mailgun-plugins/domain-onboarding-dns-verification.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.00030 | $0.00492 |
| Opus 5.5 | $0.00012 | $0.00197 |
| Sonnet 5.5 | $0.00006 | $0.00098 |
| Haiku 4.5 | $0.00003 | $0.00049 |
Grade A, and why
domain-onboarding-dns-verification 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 2mo 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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Domain Onboarding and DNS Verification
Use this skill when a user is adding a domain, checking DNS, or trying to understand why a domain is not verified.
Intake
Ask for the domain, intended Mailgun region (us or eu), and whether the domain already exists in Mailgun. Confirm whether the user wants guidance only or wants the agent to create/update domain configuration.
Workflow
- Inspect the existing domain record when it exists.
- Verify DNS through Mailgun before suggesting changes.
- Explain SPF, DKIM, MX, CNAME/tracking, and inbound route implications separately.
- Point out region mismatch risks. EU domains must use EU hosts and US domains must use US hosts.
- When DNS is missing or stale, provide exact records and a verification checklist.
- If the user wants account changes, confirm the domain, region, and desired action before calling mutating tools.
Review Checks
- SPF should include the Mailgun sending include for the domain's region and stay under the DNS lookup limit.
- DKIM must publish the selector records Mailgun expects for the domain.
- DMARC can start at monitoring mode, but production programs should have a rollout path toward enforcement.
- MX records matter for inbound routes and can also improve trust for send only domains.
- Tracking CNAME records should match the configured tracking settings before interpreting open or click gaps.
- New domains and dedicated IPs need gradual warmup before large sends.
Sender Readiness
- Confirm the From address uses a verified domain the recipient will recognize.
- For a new sender identity, recommend test mode, preview QA, or a small seed send before wider use.
- Redirect to campaign preflight when domain readiness is part of a bulk or launch send.
- Redirect to inbound routing troubleshooting when the problem is receiving mail, route matching, or inbound webhooks.
Output
Return a compact table with record type, host/name, expected value, observed state, and action needed. End with the next verification step and expected DNS propagation caveats.
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.
- 2mo ago First seen · 47 lines · 30 tokens per session scan A f67cb3a659ef
domain-onboarding-dns-verification is a skill published in the GitHub repository mailgun/mailgun-plugins (2 stars, last pushed 15d ago), licensed Apache-2.0. It adds 30 tokens to every session and 492 once invoked, about $0.0001 per session on Opus 5.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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…