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.
git clone --depth 1 https://github.com/Stickman230/claude-pentestWrote 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/agents/stickman230/claude-pentest/domain-assessment)<a href="https://agentmods.dev/agents/stickman230/claude-pentest/domain-assessment"><img src="https://agentmods.dev/badge/agents/stickman230/claude-pentest/domain-assessment/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/agents/stickman230/claude-pentest/domain-assessment"><img src="https://agentmods.dev/badge/agents/stickman230/claude-pentest/domain-assessment.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.00060 | $0.02289 |
| Opus 5 | $0.00030 | $0.01144 |
| Sonnet 5 | $0.00012 | $0.00458 |
| Haiku 4.5 | $0.00006 | $0.00229 |
Grade A, and why
domain-assessment 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 11d 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.
curl -s "https://crt.sh/?q=%.TARGET&output=json" | jq -r '.[].name_value' | sort -u \ How it starts
The opening of the file, as written. The whole thing — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Domain Assessment
Execute comprehensive domain reconnaissance. Discover subdomains, scan ports, enumerate services, and produce an attack surface inventory that feeds downstream vulnerability testing.
Workflow
Phase 1: Recon
- Mount skill and reference files:
Read plugins/pentest/skills/domain-assessment/SKILL.md Read plugins/pentest/skills/mks/SKILL.md Read plugins/pentest/skills/pentest/attacks/ip-infrastructure/README.md Read plugins/pentest/skills/pentest/attacks/ip-infrastructure/reference/README.md Read plugins/pentest/skills/pentest/attacks/ip-infrastructure/dns/quickstart.md Read plugins/pentest/skills/pentest/attacks/ip-infrastructure/port-scanning/quickstart.md - Run passive subdomain enumeration tools:
subfinder -d TARGET -o outputs/ENGAGEMENT/activity/subfinder-TARGET.txt amass enum -passive -d TARGET -o outputs/ENGAGEMENT/activity/amass-passive-TARGET.txt - Query certificate transparency logs:
curl -s "https://crt.sh/?q=%.TARGET&output=json" | jq -r '.[].name_value' | sort -u \ > outputs/ENGAGEMENT/activity/crt-sh-TARGET.txt - Attempt DNS zone transfer:
dig @ns1.TARGET TARGET AXFR 2>&1 | tee outputs/ENGAGEMENT/activity/axfr-TARGET.txt dnsrecon -d TARGET -t axfr 2>&1 | tee outputs/ENGAGEMENT/activity/dnsrecon-axfr-TARGET.txt - Deduplicate all discovered subdomains into one list:
cat outputs/ENGAGEMENT/activity/subfinder-TARGET.txt \ outputs/ENGAGEMENT/activity/amass-passive-TARGET.txt \ outputs/ENGAGEMENT/activity/crt-sh-TARGET.txt \ | sort -u > outputs/ENGAGEMENT/activity/all-subdomains-TARGET.txt - Log:
{"timestamp":"...","agent":"domain-assessment","action":"recon","domain":"TARGET","subdomains_found":47,"sources":["subfinder","amass","crt.sh"]}
Phase 2: Experiment
- DNS brute-force with wordlist to find additional subdomains:
amass enum -active -d TARGET -brute \ -w /usr/share/seclists/Discovery/DNS/subdomains-top1million-5000.txt \ -o outputs/ENGAGEMENT/activity/amass-active-TARGET.txt - Verify which subdomains are live (respond over HTTP/HTTPS):
httpx -list outputs/ENGAGEMENT/activity/all-subdomains-TARGET.txt \ -status-code -title -tech-detect \ -o outputs/ENGAGEMENT/activity/live-subdomains-TARGET.txt - Extract IPs for live subdomains:
httpx -list outputs/ENGAGEMENT/activity/live-subdomains-TARGET.txt \ -ip -o outputs/ENGAGEMENT/activity/live-ips-TARGET.txt - Log:
{"timestamp":"...","agent":"domain-assessment","action":"experiment","technique":"dns-bruteforce","new_subdomains":12,"live_hosts":31}
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.
- 11d ago First seen · 201 lines · 60 tokens per session scan A 5cafb0ed9fd5
domain-assessment is an agent published in the GitHub repository Stickman230/claude-pentest (100 stars, last pushed 3mo ago), licensed MIT. It adds 60 tokens to every session and 2,289 once invoked, about $0.0003 per session on Opus 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-30.
Other agents, from other repositories
darlene
Use this agent when the user asks to "exploit a vulnerability", "test this exploit", "generate exploit", "attack this endpoint", "run exploitation", "verify the vulnerability", or discusses actively exploiting a confirmed finding. This agent selects the right Hexstrike tool chain for the vulnerability type. Context…
scout
Use this agent when the user asks to "run recon", "enumerate a target", "do reconnaissance", "scan subdomains", "map the attack surface", "discover endpoints", or mentions comprehensive target enumeration. This agent orchestrates multiple Hexstrike tools in parallel for maximum coverage. Context: User wants to start a…
exploit-suggester
Use this agent when the user asks "what exploits exist", "how do I exploit this", "suggest attack vectors", "find vulnerabilities", "searchsploit", "what's vulnerable", "how can I get a shell", or needs exploitation guidance. Examples: Context: After discovering Apache 2.4.49 user: "What exploits are there for this?"…
shell-manager
Use this agent when the user asks to "start a listener", "catch a shell", "manage shells", "send command to shell", "check shell output", "set up reverse shell", or needs to maintain persistent shell access during exploitation. Examples: Context: User has RCE and needs to catch reverse shell user: "Start a listener on…
exploit-runner
Use this agent when a specific CVE is identified and you need to find and run a working exploit. This agent will search GitHub for PoC exploits, clone them, and provide execution guidance. Examples: Context: CVE-2025-32433 identified on Erlang SSH user: "Exploit the Erlang SSH" assistant: Clones…
source-analyzer
Use this agent when you discover source code, backup files, or need to analyze application code for vulnerabilities. Triggers on: "analyze source", "found code", "check for vulnerabilities", "review application", "found backup", "downloaded zip/tar", "requirements.txt", "package.json".