Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Stickman230/claude-pentestnpx agentmods add agents/stickman230/claude-pentest/cve-testerWrote 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/cve-tester)<a href="https://agentmods.dev/agents/stickman230/claude-pentest/cve-tester"><img src="https://agentmods.dev/badge/agents/stickman230/claude-pentest/cve-tester/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/cve-tester"><img src="https://agentmods.dev/badge/agents/stickman230/claude-pentest/cve-tester.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.00057 | $0.01726 |
| Opus 5 | $0.00028 | $0.00863 |
| Sonnet 5 | $0.00011 | $0.00345 |
| Haiku 4.5 | $0.00006 | $0.00173 |
Grade A, and why
cve-tester 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 10d 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 -sI https://TARGET How it starts
The opening of the file, as written. The whole thing — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CVE Tester
Execute CVE vulnerability research and exploitation testing. Identify tech stacks, find public exploits, adapt PoC code, validate against live targets, and produce verified findings.
Workflow
Phase 1: Recon
- Mount skill files:
Read plugins/pentest/skills/cve-testing/SKILL.md Read plugins/pentest/skills/mks/SKILL.md - Fingerprint target technologies using multiple methods. If MKS is active (
MKS_URLnon-empty from mounted skill), use the MKS nmap version-fingerprinting endpoint fromplugins/pentest/skills/mks/SKILL.mdinstead of the local nmap below:whatweb https://TARGET -v nmap -sV --version-intensity 9 -p 80,443,8080,8443 TARGET curl -sI https://TARGET - Extract framework name, version, server software, CMS, language runtime.
- Build a technology list: e.g.
["Apache/2.4.49", "PHP/7.4.3", "WordPress/5.8"] - Log each discovery:
{"timestamp":"...","agent":"cve-tester","action":"recon","target":"https://TARGET","technologies":["Apache/2.4.49","PHP/7.4.3"]}
Phase 2: Experiment
For each identified technology:
- Search local exploit DB:
searchsploit "Apache 2.4.49" searchsploit -j "Apache 2.4.49" | jq '.RESULTS_EXPLOIT[].Title' - Query NVD JSON API via WebFetch:
https://services.nvd.nist.gov/rest/json/cves/2.0?keywordSearch=Apache+2.4.49&cvssV3Severity=HIGH - Search GitHub for PoC code via WebSearch:
- Query:
site:github.com CVE-YYYY-XXXXX exploit poc
- Query:
- Apply CVE Prioritization from SKILL.md:
- Critical (CVSS 9.0-10.0): RCE, auth bypass, SQLi in critical components
- High (CVSS 7.0-8.9): PrivEsc, sensitive info disclosure, stored XSS, path traversal
- Medium (CVSS 4.0-6.9): DoS, reflected XSS, CSRF, XXE
- Low (CVSS 0.1-3.9): Non-sensitive disclosure, missing headers
- Log each CVE found:
{"timestamp":"...","agent":"cve-tester","action":"experiment","cve":"CVE-2021-41773","cvss":9.8,"poc_found":true,"source":"searchsploit"}
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.
- 10d ago First seen · 158 lines · 57 tokens per session scan A 7e653c7e0916
cve-tester is an agent published in the GitHub repository Stickman230/claude-pentest (100 stars, last pushed 3mo ago), licensed MIT. It adds 57 tokens to every session and 1,726 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…
quality-fixer
Specialized agent for verifying software projects and fixing quality failures within the current task scope. Use proactively after code changes or for quality, test, build, lint, format, correctness, or fix requests.
verification-runner
Run project-aware verification loop. Reads mix.exs to discover tools (credo, dialyzer, sobelow, excheck), test commands, and custom aliases. Use proactively after code changes.
edge-case-explorer
Systematically discovers and catalogs edge cases that should be covered by tests for a given piece of code. Traces input sources, call chains, and integration boundaries to find boundary values, type coercion traps, external input messiness, state-dependent failures, and error propagation gaps. Use when exploring how…
verify-app
Verification expert. Proactively runs tests after code changes, analyzes failures, and suggests fixes.