Borrowing it
Nothing to install: this file belongs to Suzu-Testing/metasploit-cursor-harness. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Suzu-Testing/metasploit-cursor-harness/main/.cursor/skills/dns-pentest/SKILL.mdgit clone --depth 1 https://github.com/Suzu-Testing/metasploit-cursor-harnessWrote 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/suzu-testing/metasploit-cursor-harness/dns-pentest)<a href="https://agentmods.dev/skills/suzu-testing/metasploit-cursor-harness/dns-pentest"><img src="https://agentmods.dev/badge/skills/suzu-testing/metasploit-cursor-harness/dns-pentest/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/suzu-testing/metasploit-cursor-harness/dns-pentest"><img src="https://agentmods.dev/badge/skills/suzu-testing/metasploit-cursor-harness/dns-pentest.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.00031 | $0.01573 |
| Opus 5.5 | $0.00012 | $0.00629 |
| Sonnet 5.5 | $0.00006 | $0.00315 |
| Haiku 4.5 | $0.00003 | $0.00157 |
Grade A, and why
dns-pentest 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 — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DNS Pentest
Prerequisites
- Target is in scope (
scope/scope-master.txt, engagement ROE). - Do not run recursion amplification attacks. Document only.
Ports and detection
| Port | Service |
|---|---|
| 53/tcp, 53/udp | DNS |
| 5353/udp | mDNS (related enumeration) |
Version fingerprint
MSF MCP (preferred):
msf_run_auxiliary_module(
module_name="auxiliary/gather/enum_dns",
engagement_id="<id>",
options={"DOMAIN": "<domain>", "NAMESERVER": "<target>", "THREADS": 5}
)
CLI fallback:
dig version.bind CHAOS TXT @<target>
nmap -sU -sT -p53 --script dns-nsid,dns-recursion <target>
fpdns <target>
Workflow
Task Progress:
- [ ] Version and banner fingerprint
- [ ] Zone transfer (AXFR) attempt
- [ ] SPF/DMARC/DKIM record review
- [ ] Subdomain and SRV enumeration
- [ ] DNSSEC NSEC walking
- [ ] Document findings
Zone transfer (AXFR)
MSF MCP (preferred):
msf_run_auxiliary_module(
module_name="auxiliary/gather/enum_dns",
engagement_id="<id>",
options={"DOMAIN": "<domain>", "NAMESERVER": "<target>"}
)
CLI fallback:
dig axfr @<target> <domain>
dig axfr @<target>
fierce --domain <domain> --dns-servers <target>
dnsrecon -d <domain> -a -n <target>
Record queries
MSF MCP (preferred):
msf_run_auxiliary_module(
module_name="auxiliary/gather/enum_dns",
engagement_id="<id>",
options={"DOMAIN": "<domain>", "NAMESERVER": "<target>"}
)
CLI fallback:
dig ANY @<target> <domain>
dig A <domain> @<target>
dig AAAA <domain> @<target>
dig MX <domain> @<target>
dig NS <domain> @<target>
dig TXT <domain> @<target>
dig SOA <domain> @<target>
dig -x <IP> @<target>
host -a <domain> <target>
SPF / DMARC / DKIM queries
MSF: No direct module; use CLI.
CLI fallback:
dig txt <domain> @<target>
dig txt _dmarc.<domain> @<target>
dig txt default._domainkey.<domain> @<target>
dig mx <domain> @<target>
# Weak SPF: +all, ~all with no strict includes
# Weak DMARC: p=none or no record
host -t TXT <domain> <target>
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 · 229 lines · 31 tokens per session scan A 22231c1df62c
dns-pentest is a skill published in the GitHub repository Suzu-Testing/metasploit-cursor-harness (3 stars, last pushed 2mo ago), licensed MIT. It adds 31 tokens to every session and 1,573 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…