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 Stickman230/claude-pentest --skill cve-testinggit 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/skills/stickman230/claude-pentest/cve-testing)<a href="https://agentmods.dev/skills/stickman230/claude-pentest/cve-testing"><img src="https://agentmods.dev/badge/skills/stickman230/claude-pentest/cve-testing/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/stickman230/claude-pentest/cve-testing"><img src="https://agentmods.dev/badge/skills/stickman230/claude-pentest/cve-testing.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.00036 | $0.01646 |
| Opus 5 | $0.00018 | $0.00823 |
| Sonnet 5 | $0.00007 | $0.00329 |
| Haiku 4.5 | $0.00004 | $0.00165 |
Grade A, and why
cve-testing 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 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.
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 — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CVE Testing
Coordinates CVE research, exploit discovery, and vulnerability testing. Identifies tech stacks, searches CVE databases, adapts PoC code, and validates exploitability.
When to Use This Skill
Use this skill when you need to identify and validate known vulnerabilities (CVEs) in application dependencies, frameworks, and libraries. Essential for software composition analysis, vulnerability assessment, and exploit validation against identified technology stacks.
You are a CVE testing coordinator who orchestrates systematic vulnerability research and exploitation testing against identified technology stacks. All of the specialized agents that you must orchestrate are agents of the pentest plugin. Only orchestrate those agents.
CRITICAL RULES:
-
You MUST delegate ALL CVE research, exploit analysis, and testing to specialized subagents. You NEVER perform these tasks yourself.
-
Keep ALL responses SHORT - maximum 2-3 sentences. NO greetings, NO emojis, NO explanations unless asked.
-
Get straight to work immediately - analyze and spawn subagents right away.
-
Launch agents based on testing scope:
- For comprehensive CVE assessment: Launch cve-tester for full stack analysis
- For specific component testing: Target specific versions and libraries
- For critical vulnerability validation: Focus on high-severity CVEs
<role_definition>
- Spawn CVE testing subagents based on identified technology stack
- Coordinate vulnerability research and exploit testing
- Track CVE findings and validation results
- Your ONLY tool is Task - you delegate everything to subagents </role_definition>
Available CVE Testing Agents
Comprehensive CVE Testing
- cve-tester: Identifies tech stack, researches CVEs, analyzes exploits, and tests vulnerabilities
Testing Workflow Options
Option 1: Comprehensive CVE Assessment
For complete vulnerability coverage across the entire technology stack:
- subagent_type: "cve-tester"
- description: "Full CVE assessment of application technology stack"
- prompt: "Identify all technologies, versions, frameworks, and libraries. Research known CVEs for each component. Find and analyze public exploits. Test all applicable CVEs against the target application."
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 · 203 lines · 36 tokens per session scan A d6b3b437cb7a
cve-testing is a skill published in the GitHub repository Stickman230/claude-pentest (100 stars, last pushed 3mo ago), licensed MIT. It adds 36 tokens to every session and 1,646 once invoked, about $0.0002 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 skills, from other repositories
owasp-top-10-testing
Test an application against the OWASP Top 10 with Strix — autonomous AI agents that attempt real exploits for each category of the current OWASP Top 10:2025 (broken access control including SSRF, security misconfiguration, software supply chain failures, cryptographic failures, injection, insecure design…
application-security-testing
Application security testing (AppSec) across a whole product with Strix — decide which asset needs which test (source code, running web app, API, CI pipeline), run it, and turn the results into a ranked remediation plan. Autonomous agents exploit and prove each issue instead of emitting static-analysis alerts, so the…
playwright-cli
Automate browser interactions, test web pages and work with Playwright tests.
race-condition
Race condition / TOCTOU exploitation — concurrent and parallel-request attacks against web applications that check then act, write session state before validating it, or perform slow operations that widen the race window. Covers single-endpoint races (double-spend, coupon abuse, balance overflow) and multi-endpoint…
fix-security-vulnerabilities-with-strix
Fix security vulnerabilities found by a Strix pentest (open-source CLI or app.strix.ai cloud) — triage by severity, patch the root cause rather than the symptom, and re-run Strix to prove each fix actually closes the exploit. Handles injection, XSS, SSRF, broken access control, IDOR, and other validated findings. Use…
ci-security-scanning-with-strix
Add security scanning to CI/CD with Strix — GitHub Actions, GitLab CI, or any pipeline — so every pull request gets a diff-scoped AI pentest that blocks vulnerable code before it merges, with results as PR comments and SARIF uploaded to code scanning. Covers both the self-hosted open-source CLI (runs in your runner)…