A coordinator for authorised penetration testing, which is a controlled attempt to find security weaknesses in websites, applications, APIs, networks, or cloud systems.

Defining testing scope, mapping the systems being tested, choosing checks such as SQL injection or cross-site scripting, coordinating test agents, and documenting findings.

It organises reconnaissance, testing plans, specialised security checks, results, and reports in one engagement process. It also requires approval before testing begins.

pentest — Skill for Claude Code by Stickman230

Install

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.

Any agent

npx skills add Stickman230/claude-pentest --skill pentest

Clone the repo

git clone --depth 1 https://github.com/Stickman230/claude-pentest

Made for: Claude Code.

Or install pentest, the plugin that ships this one along with the rest of its 7 skills, 5 commands, 15 agents.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/stickman230/claude-pentest/pentest/github.svg)](https://agentmods.dev/skills/stickman230/claude-pentest/pentest)

Your own site

<a href="https://agentmods.dev/skills/stickman230/claude-pentest/pentest"><img src="https://agentmods.dev/badge/skills/stickman230/claude-pentest/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/stickman230/claude-pentest/pentest"><img src="https://agentmods.dev/badge/skills/stickman230/claude-pentest/pentest.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,023 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00050	$0.02023
Opus 5	$0.00025	$0.01012
Sonnet 5	$0.00010	$0.00405
Haiku 4.5	$0.00005	$0.00202

Measured 10d ago against content hash d87585b2028b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

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 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.

plugins/pentest/skills/pentest/SKILL.md · 160 lines

How it starts

The opening of the file, as written. The whole thing — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Coordinate penetration testing. Deploy executors, aggregate results, generate reports. Use it when user requests pentesting, security assessment, or vulnerability testing.

Workflow

Phase 1: Initialization

Gather scope: Target URL, restrictions, testing window
Create engagement folder: outputs/{engagement-name}/

Phase 2: Reconnaissance (Read reference/RECONNAISSANCE_OUTPUT.md to get outputs format)

Select reconnaissance tools based on asset type (domains, web apps, APIs, network, cloud)
Run recon in parallel via the inventory agents (web-application-mapping) and domain-assessment
Generate asset-specific inventory files in outputs/{engagement}/inventory/ (JSON per asset type) using the defined output format
Generate the consolidated analysis/attack-surface.md and analysis/testing-checklist.md using the defined output format

Phase 3: Planning & Approval (MANDATORY)

Analyze reconnaissance findings from outputs/{engagement}/inventory/ and outputs/{engagement}/analysis/
Create test plan: Executors to deploy, attack surface justification, testing approach
Present plan to user via AskUserQuestion
Get explicit approval if not already approved in the first phase: "Approve plan?", "Modify executors?", "Cancel?"
CRITICAL: Do NOT proceed to Phase 4 without user approval

Phase 4: Vulnerability Testing

Deploy approved executors in parallel (single Task call with run_in_background=True)
Monitor progress: Periodic TaskOutput(block=False)
Recursive spawning: New discoveries trigger new executors (ask approval if major change)

Phase 5: Aggregation

Collect findings from all executors
Deduplicate (same vuln + location = duplicate)
Identify exploit chains
Calculate severity metrics

Phase 6: Reporting (Read reference/FINAL_REPORT.md - includes DOCX conversion)

CRITICAL: Create folder structure FIRST: report/ and processed/ with subdirectories
Move ALL working files to processed/: reconnaissance/, findings/, activity/ → processed/
Move ALL intermediate files: ANY .md files, drafts, analysis → processed/intermediate-reports/
Generate markdown report: Use reference/FINAL_REPORT.md template → processed/intermediate-reports/pentest-final-report.md
REQUIRED: Generate .docx: Run pandoc command → report/Penetration-Test-Report.docx (cover page, TOC, body, appendix section)
Optional: Generate PDF: If LaTeX available → report/Penetration-Test-Report.pdf, else skip (DOCX is primary deliverable)
Copy referenced evidence: Organize by finding → report/appendix/finding-{id}/
Create report README: Document deliverables in report/README.md
VERIFY CLEAN STRUCTURE: ls -la outputs/{engagement}/ shows ONLY report/ and processed/
CRITICAL: NO intermediate files in root or report/ - Everything goes to processed/ except final deliverables (.docx, .json, README, appendix/)

Read the full file on GitHub · 160 lines

Files

What ships with it

60 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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 · 160 lines · 50 tokens per session scan A d87585b2028b

Subscribe to this mod's changes

pentest is a skill published in the GitHub repository Stickman230/claude-pentest (100 stars, last pushed 3mo ago), licensed MIT. It adds 50 tokens to every session and 2,023 once invoked, about $0.0003 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.

Claude Code Security ai-pentesting claude claude-code-plugin cybersecurity pentesting

api-security-testing

Security-test a REST, GraphQL, or gRPC API with Strix — autonomous agents that enumerate endpoints from an OpenAPI/GraphQL schema (or by crawling), then actually exploit the API-specific vulnerability classes in the OWASP API Security Top 10 (2023) — broken object-level authorization (BOLA/IDOR), broken object…

usestrix/strix · 144 tokens

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…

usestrix/strix · 124 tokens

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…

usestrix/strix · 151 tokens

find-security-vulnerabilities-in-code

Find security vulnerabilities in a codebase or repository with Strix — a white-box AI security review that reads your source, reasons about the actual data flow and authorization model, then exploits what it finds in a live sandbox so every reported issue has a working proof-of-concept instead of a noisy…

usestrix/strix · 129 tokens

web-app-penetration-testing

Pentest a web app or website end to end — black-box testing of a live URL, staging environment, or local dev server that finds and exploits real vulnerabilities (auth bypass, broken access control, IDOR, injection, XSS, SSRF, business logic) and proves each one with a working proof-of-concept instead of a signature…