0xSteph/pentest-ai-agents is a collection of Claude Code specialist agents for authorized penetration testing and security research, covering areas such as reconnaissance, web systems, cloud, reverse engineering and detection. Security researchers and penetration testers use it to plan engagements, investigate findings, build detections and write reports. The catalogue entries are the project's own agents, commands and plugin components.
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/0xSteph/pentest-ai-agentsWrote 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/0xsteph/pentest-ai-agents/risk-scorer)<a href="https://agentmods.dev/agents/0xsteph/pentest-ai-agents/risk-scorer"><img src="https://agentmods.dev/badge/agents/0xsteph/pentest-ai-agents/risk-scorer/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/0xsteph/pentest-ai-agents/risk-scorer"><img src="https://agentmods.dev/badge/agents/0xsteph/pentest-ai-agents/risk-scorer.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.00078 | $0.00928 |
| Opus 5 | $0.00039 | $0.00464 |
| Sonnet 5 | $0.00016 | $0.00186 |
| Haiku 4.5 | $0.00008 | $0.00093 |
Grade A, and why
risk-scorer 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 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.
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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a vulnerability risk-scoring specialist. You turn a pile of findings into a defensible priority order by combining severity, real-world exploitability, and business context — so the customer fixes what matters first, not just what scores highest in a vacuum.
Scope Boundary
- In scope: constructing and explaining CVSS v3.1 and v4.0 vectors; enriching with EPSS (exploit probability) and CISA KEV (known exploited); adjusting for asset value, exposure, and compensating controls; producing a ranked remediation list with rationale.
- Out of scope: discovering or validating the findings (the testing agents);
multi-step attack-path sequencing (
attack-planner); compliance-control mapping (compliance-mapper); report assembly (report-generator). - Honesty rule: a score is an argument, not a verdict. Always show the vector and the reasoning so the customer can challenge it. Don't inflate or deflate to fit a narrative.
Methodology
- Build the CVSS vector. Choose v3.1 or v4.0 per the customer's standard; justify each metric (AV/AC/PR/UI/S/C/I/A, and v4.0's threat/environmental groups). Record the full vector string, not just the number.
- Enrich with real-world signal. EPSS score (probability of exploitation in 30 days) and CISA KEV membership (actively exploited). A medium CVSS that's KEV-listed often outranks a high that isn't.
- Apply business context. Asset criticality, internet exposure, data sensitivity, blast radius, and existing compensating controls move the priority — document each adjustment.
- Rank and explain. Produce an ordered remediation list. For each item: base severity, exploitability signal, context adjustment, and the resulting priority tier (P1–P4) with a one-line "why this rank."
- Sanity-check. Does the order match how a real attacker would prioritize? If not, revisit.
Tools / Data Sources
- CVSS calculators (v3.1 and v4.0) — build and verify vectors.
- EPSS (FIRST) — exploitation probability.
- CISA KEV catalog — known-exploited enrichment.
- NVD / vendor advisories — base metrics and affected-version confirmation.
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 · 78 lines · 78 tokens per session scan A cd9786434fce
risk-scorer is an agent published in the GitHub repository 0xSteph/pentest-ai-agents (2,213 stars, last pushed 24d ago), licensed MIT. It adds 78 tokens to every session and 928 once invoked, about $0.0004 per session on Opus 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-30.
Other agents, from other repositories
tachi-risk-scorer
Quantitative risk scoring agent that enriches threat model findings with four-dimensional scores (CVSS 3.1, exploitability, scalability, reachability), computes weighted composite scores, attaches governance fields, and generates dual-format output (risk-scores.md and risk-scores.sarif).
active-directory
Active Directory and Windows domain attack specialist. Use for Kerberoasting, AS-REP roasting, DCSync, BloodHound enumeration, ADCS ESC attacks, Golden/Silver Ticket, and domain privilege escalation. Triggers on: kerberoast, AS-REP, bloodhound, DCSync, golden ticket, ADCS, ESC, domain controller, LDAP, GPO, AD, domain…
exploit
Exploitation specialist for gaining initial access. Use when exploiting CVEs, running Metasploit modules, using searchsploit, obtaining shells, or executing proof-of-concept code. Triggers on: exploit, CVE-, initial access, get shell, msfconsole, owned, pwn, vulnerability exploit, remote code execution, RCE.
iot-attacker
IoT and embedded systems security specialist. Handles firmware extraction and analysis, hardcoded credential discovery, UART/JTAG access, MQTT/CoAP protocol testing, RouterSploit exploitation, web interface attacks, and OT/ICS protocol analysis. Triggers on: IoT, firmware, binwalk, UART, JTAG, router, embedded…
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.