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 avizmarlon/agent-skills --skill dns-and-whois-toolsgit clone --depth 1 https://github.com/avizmarlon/agent-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/avizmarlon/agent-skills/dns-and-whois-tools)<a href="https://agentmods.dev/skills/avizmarlon/agent-skills/dns-and-whois-tools"><img src="https://agentmods.dev/badge/skills/avizmarlon/agent-skills/dns-and-whois-tools/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/avizmarlon/agent-skills/dns-and-whois-tools"><img src="https://agentmods.dev/badge/skills/avizmarlon/agent-skills/dns-and-whois-tools.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.00104 | $0.01744 |
| Opus 5.5 | $0.00042 | $0.00698 |
| Sonnet 5.5 | $0.00021 | $0.00349 |
| Haiku 4.5 | $0.00010 | $0.00174 |
Grade A, and why
dns-and-whois-tools 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
2. **Google DNS API** — `curl -s "https://dns.google/resolve?name=DOMAIN&type=A"` — works from any shell, returns JSON. How it starts
The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DNS & WHOIS Tools
Investigation toolkit for DNS, WHOIS, IP reputation, and passive-DNS work. Applies to any domain or IP across public internet domains.
DNS lookup — preferred order
wsl dig— fullest output, supports+short,+noall +answer,ANY,AXFR, etc.- Google DNS API —
curl -s "https://dns.google/resolve?name=DOMAIN&type=A"— works from any shell, returns JSON. nslookup— works but some local resolvers may return "No response from server". Use only when 1 and 2 are unavailable.
Current DNS records
# A / NS / MX / CNAME / TXT via Google DNS-over-HTTPS
curl -s "https://dns.google/resolve?name=DOMAIN&type=A|NS|MX|CNAME|TXT"
# Indexed subdomains (HackerTarget)
curl -s "https://api.hackertarget.com/hostsearch/?q=DOMAIN"
Historical / passive DNS
Use these when "what nameservers did this domain use before migrating?" or "what DNS records existed historically?" matters. They reveal records that no longer resolve.
- crt.sh (Certificate Transparency):
curl -s "https://crt.sh/?q=%.DOMAIN&output=json"— reveals subdomains that ever had SSL issued (indirect evidence they existed). - SecurityTrails —
https://securitytrails.com/domain/DOMAIN/dns(WebFetch; may require account). - WhoisFreaks —
https://whoisfreaks.com/tools/dns/history/lookup/DOMAIN(WebFetch). - DNSHistory.org —
https://dnshistory.org/dns-records/DOMAIN(WebFetch). - ViewDNS.info —
https://viewdns.info/history/?domain=DOMAIN(WebFetch).
Priority order for historical nameservers: SecurityTrails (preferred, comprehensive history) → WhoisFreaks → ViewDNS.info → DNS provider customer support.
WHOIS — domain ownership and registrar information
- who.is —
https://who.is/whois/DOMAIN(WebFetch). - ICANN Lookup —
https://lookup.icann.org/en/lookup?name=DOMAIN(WebFetch). wsl whois DOMAINfor shells withwhoisavailable.
Note: some ccTLDs (.in, .de, .uk, etc.) do not expose public WHOIS for the registrant due to regional privacy regulations.
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 · 128 lines · 104 tokens per session scan A 4151ad410b63
dns-and-whois-tools is a skill published in the GitHub repository avizmarlon/agent-skills (2 stars, last pushed 4mo ago), licensed MIT. It adds 104 tokens to every session and 1,744 once invoked, about $0.0004 per session on Opus 5.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-31.
Other skills, from other repositories
subagent-driven-development
Execute plans via delegatetask subagents (2-stage review).
duckduckgo-search
Free keyless web, news, and image search via ddgs.
mcporter
List, auth, and call MCP servers/tools from the terminal.
article-writing
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
safe-refactor
Restructure code while preserving behavior. Use for extraction, consolidation, ownership moves, or cleanup where verification must bracket structural edits.