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 AI-Shell-Team/aish --skill dns-diagnosegit clone --depth 1 https://github.com/AI-Shell-Team/aishWrote 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/ai-shell-team/aish/dns-diagnose)<a href="https://agentmods.dev/skills/ai-shell-team/aish/dns-diagnose"><img src="https://agentmods.dev/badge/skills/ai-shell-team/aish/dns-diagnose/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/ai-shell-team/aish/dns-diagnose"><img src="https://agentmods.dev/badge/skills/ai-shell-team/aish/dns-diagnose.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00066 | $0.01219 |
| Opus 5.5 | $0.00026 | $0.00488 |
| Sonnet 5.5 | $0.00013 | $0.00244 |
| Haiku 4.5 | $0.00007 | $0.00122 |
Grade A, and why
dns-diagnose 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 1mo 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DNS resolution diagnosis
Troubleshoot domain resolution failures, wrong answers, or “I changed the record but it still fails” on this host.
Out of scope: editing /etc/resolv.conf or NetworkManager by default, buying domains / changing authoritative DNS for the user, HTTP 5xx, or TLS certificate issues (ssl-cert-toolkit). Path quality after resolve succeeds belongs to network-path-diagnose.
Rules
- Need a domain first: ask if missing; optional expected type (A/AAAA/CNAME/MX/TXT).
- Read-only: inspect resolution and config; do not change DNS servers or hosts unless the user explicitly asks (default is advice only).
- Stop when enough: once you can separate “local resolver” vs “authoritative/record” issues, answer.
- Missing tools: prefer
dig; elsehost/nslookup/getent. - Ask before sending internal/sensitive names to public DNS,
+trace, orwhois.
Workflow
Confirm domain & symptom → local resolver → local dig → optional external checks → answer
1. Confirm inputs
| Input | Notes |
|---|---|
| Domain | e.g. example.com or www.example.com |
| Symptom | total failure / wrong answer / recent change not visible / only on some networks |
| Record type | default A/AAAA; include MX if mail-related |
2. Local resolver
cat /etc/resolv.conf 2>/dev/null
resolvectl status 2>/dev/null || systemd-resolve --status 2>/dev/null || true
getent ahosts <domain> | head -10
grep '^hosts:' /etc/nsswitch.conf 2>/dev/null
grep -E "^\s*[0-9a-fA-F:.]+\s+.*\b<domain>\b" /etc/hosts 2>/dev/null || true
| Observation | Lean toward |
|---|---|
getent works, browser fails |
App/proxy/DoH; not only system DNS |
Bad /etc/hosts entry |
Local hijack |
| No nameserver / broken resolved | Local resolver config |
3. Local dig (default)
command -v dig
dig +noall +answer +stats <domain> A
dig +noall +answer <domain> AAAA
Without dig: host <domain> or nslookup <domain>.
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.
- 1mo ago First seen · 153 lines · 66 tokens per session scan A f3a61ba15f3c
dns-diagnose is a skill published in the GitHub repository AI-Shell-Team/aish (568 stars, last pushed 3d ago), licensed Apache-2.0. It adds 66 tokens to every session and 1,219 once invoked, about $0.0003 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-30.
Other skills, from other repositories
cloudflare-one
Design, configure, troubleshoot, or review Cloudflare One Zero Trust and SASE deployments. Use cloudflare-one-migrations for migration planning from other vendors.
cloudflare
Discover and choose Cloudflare products for apps, APIs, AI agents, storage, networking, and security. Use for architecture and product selection, including when the user describes a need without naming a Cloudflare product; then find the relevant skill or documentation.
cloudflare-one-migrations
Assess and plan migrations from existing VPN, SWG, or SASE platforms to Cloudflare One, including policy mapping, parity gaps, and rollout.
sandbox-stable
Build or maintain Cloudflare Sandbox apps on the stable @cloudflare/sandbox package. Use sandbox-next for preview apps and sandbox-migrate-to-next for stable-to-preview migrations.
wrangler
Run or troubleshoot Wrangler CLI commands and configure Worker projects for local development, Previews, deployment, and Cloudflare resource management.
sandbox-migrate-to-next
Migrate Cloudflare Sandbox apps from stable @cloudflare/sandbox to @cloudflare/sandbox@next (SDK 1.0 preview). Use sandbox-next for apps already on the preview.