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 woohyun212/security-skill --skill dns-recongit clone --depth 1 https://github.com/woohyun212/security-skillWrote 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/woohyun212/security-skill/dns-recon)<a href="https://agentmods.dev/skills/woohyun212/security-skill/dns-recon"><img src="https://agentmods.dev/badge/skills/woohyun212/security-skill/dns-recon/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/woohyun212/security-skill/dns-recon"><img src="https://agentmods.dev/badge/skills/woohyun212/security-skill/dns-recon.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.00019 | $0.01648 |
| Opus 5 | $0.00010 | $0.00824 |
| Sonnet 5 | $0.00004 | $0.00330 |
| Haiku 4.5 | $0.00002 | $0.00165 |
Grade B, and why
dns-recon scanned grade B 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 9d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo apt-get install -y dnsutils How it starts
The opening of the file, as written. The whole thing — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What this skill does
Performs a full DNS record lookup on a target domain using dig, host, and nslookup. Enumerates A/AAAA/MX/NS/TXT/CNAME records, checks for zone transfer (AXFR) vulnerabilities, and verifies DNSSEC configuration.
When to use
- When mapping a domain's infrastructure (mail servers, name servers, IP ranges)
- When detecting misconfigured DNS zone transfer vulnerabilities
- When auditing SPF/DKIM/DMARC configuration status
- When identifying subdomain takeover candidates
Prerequisites
- Install the
dnsutilspackage (includes dig, host, nslookup):# Ubuntu/Debian sudo apt-get install -y dnsutils # CentOS/RHEL sudo yum install -y bind-utils - Environment variable
SECSKILL_TARGET_DOMAIN: target domain
Inputs
| Variable | Required | Description |
|---|---|---|
SECSKILL_TARGET_DOMAIN |
required | Domain to query (e.g. example.com) |
SECSKILL_OUTPUT_DIR |
optional | Directory for saving results (default: ./output) |
SECSKILL_DNS_RESOLVER |
optional | DNS resolver IP to use (default: system default) |
Workflow
Step 1: Prepare environment
export TARGET="${SECSKILL_TARGET_DOMAIN:?Set the SECSKILL_TARGET_DOMAIN environment variable}"
export OUTDIR="${SECSKILL_OUTPUT_DIR:-./output}"
export RESOLVER="${SECSKILL_DNS_RESOLVER:-}"
mkdir -p "$OUTDIR"
RESOLVER_OPT=""
[ -n "$RESOLVER" ] && RESOLVER_OPT="@${RESOLVER}"
echo "[*] Starting DNS recon: $TARGET"
Step 2: Query basic records (A, AAAA, MX, NS, TXT, CNAME)
OUTFILE="$OUTDIR/dns_records_${TARGET}.txt"
echo "===== DNS Record Query: $TARGET =====" > "$OUTFILE"
echo "Query time: $(date -u '+%Y-%m-%dT%H:%M:%SZ')" >> "$OUTFILE"
echo "" >> "$OUTFILE"
for RTYPE in A AAAA MX NS TXT CNAME SOA; do
echo "--- ${RTYPE} record ---" | tee -a "$OUTFILE"
dig $RESOLVER_OPT "$TARGET" "$RTYPE" +noall +answer 2>/dev/null \
| tee -a "$OUTFILE"
echo "" >> "$OUTFILE"
done
echo "[+] Basic record query complete"
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.
- 9d ago First seen · 173 lines · 19 tokens per session scan B 267d68a2fefe
dns-recon is a skill published in the GitHub repository woohyun212/security-skill (21 stars, last pushed 4mo ago), licensed MIT. It adds 19 tokens to every session and 1,648 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…