claude-pentest-skills
Structured web application penetration testing with OWASP methodology, curated payload references, 6-gate validation, and professional report generation
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Badge for your README
Markdown
[](/listings/frendysanusi--claude-pentest-skills)HTML
<a href="/listings/frendysanusi--claude-pentest-skills"><img src="/api/listings/frendysanusi--claude-pentest-skills/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
**Step 1 — Clone**
git clone https://github.com/frendysanusi/claude-pentest-skills.git cd claude-pentest-skills
**Step 2 — (Optional) Set up tools**
# Burp Suite MCP cp .mcp.json.example .mcp.json # Edit with your local paths # PDF report generation python3 -m venv .venv .venv/bin/pip install markdown weasyprint
**Step 3 — Hunt**
claude # Start Claude Code in the project dir /scope target.com # Define authorization (REQUIRED first step) /recon target.com # Map attack surface /hunt injection # Test for SQLi, NoSQLi, CMDi, SSTI, XXE /validate # 6-gate quality check /report --full # Generate pentest report
<br>
---
<br>
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
SKILL.md · Manifest · 108 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
- ---
- name: claude-pentest-skills
- description: Structured web application penetration testing with OWASP methodology, curated payload references, 6-gate validation, and professional report generation
- ---
- # Claude Pentest Skills
- Structured methodology, curated payload references, and strict validation processes for **authorized** web application penetration testing.
- ## When to use
- Use this skill when performing authorized web application penetration testing. It provides:
- - A structured engagement workflow: scope definition, reconnaissance, vulnerability hunting, finding validation, and report generation
- - OWASP Web Security Testing Guide (WSTG) methodology with coverage tracking
- - 18 vulnerability class references with PayloadAllTheThings links
- - A 6-gate validation process that eliminates false positives
- - Professional pentest report generation (markdown + PDF)
- **Only use against systems you own or have explicit written authorization to test.**
- ## Instructions
- ### Standard Workflow
- ```
- /scope <target> → Define authorization (REQUIRED first step)
- /recon <target> → Map attack surface (endpoints, tech stack, inputs)
- /hunt <vuln-class> → Test for a specific vulnerability class
- /validate → Run 6-gate quality check on findings
- /report --full → Generate professional pentest report
- /status → View engagement progress dashboard
- ```
- ### Safety Rules (Non-Negotiable)
- 1. **Never** test without running `/scope` first
- 2. **Never** send requests to out-of-scope domains or paths
- 3. **Always** log every payload attempt before analyzing the response
- 4. **Stop and ask** the user if uncertain whether an action is in scope
- 5. **Warn and get confirmation** before testing destructive payloads (DELETE, data modification)
- 6. **Never** send attack payloads to third-party services (Auth0, AWS, etc.) — only test the client's own infrastructure
- ### Hunt Targets
- Valid arguments for `/hunt`:
- | Group | Includes |
- |-------|----------|
- | `injection` | SQLi, NoSQLi, CMDi, SSTI, XXE |
- | `auth-access` | IDOR, JWT, OAuth, privilege escalation |
- | `server-side` | SSRF, path traversal, file upload, deserialization, request smuggling |
- | `client-side` | XSS, CSRF, open redirect |
- | `session` | Session fixation, token weakness, cookie security |
- | `business-logic` | Race conditions, workflow bypass, logic flaws |
- | `config` | Security headers, CORS, TLS, info disclosure |
- | `ai-llm` | Prompt injection, LLM tool abuse, system prompt leakage |
- Specific sub-classes also work: `/hunt sqli`, `/hunt xss`, `/hunt ssrf`, `/hunt idor`, `/hunt prompt-injection`, etc.
- ### Agent Personas
- Three specialized personas are activated by commands:
- - **Recon Agent** (`/recon`) — Systematic mapper. Passive-first, methodical, records everything.
- - **Hunter Agent** (`/hunt`) — Creative attacker. Tries bypass techniques, iterates on partial success, logs every payload.
- - **Validator Agent** (`/validate`) — Skeptical critic. Assumes false positive until proven otherwise. Runs the 6-gate quality check.
- When no command is active, behave as a general security consultant.
- ### 6-Gate Validation
- Every finding must pass all 6 gates to be included in reports:
- 1. **Reproducible PoC** — Complete HTTP request that triggers the vulnerability
- 2. **HTTP Evidence** — Both request AND response captured
- 3. **Impact Verified** — Concrete and demonstrated, not theoretical
- 4. **In-Scope** — Endpoint is within authorized scope
- 5. **Real Vulnerability** — Not informational or best-practice observation
- 6. **Client Reproducible** — A third party can follow the documented steps
- ### Engagement State
- All engagement data is stored in `engagements/<target>/`:
- - `scope.md` — Authorization and scope boundaries
- - `findings.md` — Finding table with detailed evidence
- - `payload-log.md` — Append-only payload testing history
- - `coverage.md` — OWASP WSTG test coverage tracker
- - `tech-stack.md` — Discovered technologies
- - `notes.md` — Observations and hypotheses
- ### Tool Integration
- - **Burp Suite** — Available via MCP for proxy and traffic analysis (see `mcp/burp-suite/setup.md`)
- - **SQLMap** — Use via bash **only after** manual detection confirms SQL injection
- - **Commix** — Use via bash **only after** manual detection confirms command injection
- - **Custom scripts** — Generate and execute Python/Bash scripts for race conditions, token analysis, and custom payload delivery
- ### File Loading
- When a slash command is invoked, load files in this order:
- 1. `commands/<command>.md` — Command orchestration
- 2. `agents/<agent>.md` — Agent persona (if command activates one)
- 3. `skills/<skill>.md` — Methodology
- 4. `payloads/<payload>.md` — Payload reference (if hunting)
- 5. `engagements/<target>/<state-files>` — Current engagement state
- Load on demand, not all at startup.
README.md · README · 391 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
- <div align="center">
- # Claude Pentest Skills
- ### Structured Web Application Penetration Testing with Claude Code
- *OWASP-based methodology, curated payload references, strict validation gates, and report generation — all orchestrated through slash commands.*
- <br>
- [](https://docs.anthropic.com/en/docs/claude-code)
- [](https://owasp.org/www-project-web-security-testing-guide/)
- <br>
- <a href="#-quick-start">Quick Start</a> | <a href="#-how-it-works">How It Works</a> | <a href="#-commands">Commands</a> | <a href="#-vulnerability-coverage">Coverage</a> | <a href="#-project-structure">Structure</a> | <a href="#-contributing">Contributing</a>
- <br>
- ```
- 6 slash commands · 3 agent personas · 18 vuln classes
- 6-gate validation · OWASP WSTG mapped · PDF report gen
- ```
- </div>
- <br>
- ---
- <br>
- ## The Problem
- Pentesting with AI is powerful, but without structure it's chaotic:
- - Claude sends payloads to **out-of-scope** targets
- - Findings are **false positives** that waste report-writing time
- - No consistent **methodology** — different approach every session
- - **Payload knowledge** scattered across bookmarks and notes
- - Reports are **written from scratch** every engagement
- <br>
- ## The Solution
- Claude Pentest Skills is a **structured skill pack** for Claude Code. It enforces scope, follows OWASP methodology, validates findings through a 6-gate quality process, and generates professional reports — all through simple slash commands.
- <br>
- <div align="center">
- | Before | After |
- |:---|:---|
- | Ad-hoc testing, no structure | OWASP WSTG methodology with coverage tracking |
- | False positives in reports | 6-gate validation kills bad findings before they waste your time |
- | "Is this in scope?" uncertainty | Mandatory `/scope` gate — refuses to test without authorization |
- | Write reports from scratch | `/report --full` generates professional markdown + PDF |
- | Forget what you tested | Payload log + coverage tracker across sessions |
- | Search PayloadAllTheThings manually | Curated methodology + direct references per vuln class |
- </div>
- <br>
- ---
- <br>
- ## Quick Start
- **Step 1 — Clone**
- ```bash
- git clone https://github.com/frendysanusi/claude-pentest-skills.git
- cd claude-pentest-skills
- ```
- **Step 2 — (Optional) Set up tools**
- ```bash
- # Burp Suite MCP
- cp .mcp.json.example .mcp.json
- # Edit with your local paths
- # PDF report generation
- python3 -m venv .venv
- .venv/bin/pip install markdown weasyprint
- ```
- **Step 3 — Hunt**
- ```bash
- claude # Start Claude Code in the project dir
- /scope target.com # Define authorization (REQUIRED first step)
- /recon target.com # Map attack surface
- /hunt injection # Test for SQLi, NoSQLi, CMDi, SSTI, XXE
- /validate # 6-gate quality check
- /report --full # Generate pentest report
- ```
- <br>
- ---
- <br>
- ## How It Works
- ```
- YOU
- |
- ┌─────▼─────┐
- │ Claude │ <── Burp MCP (optional)
- │ Code │
- └─────┬─────┘
- |
- ┌───────────────┼───────────────┐
- | | |
- ┌─────▼──────┐ ┌──────▼─────┐ ┌─────▼─────┐
- │ Recon │ │ Hunter │ │ Validator │
- │ Agent │ │ Agent │ │ Agent │
- └─────┬──────┘ └──────┬─────┘ └─────┬─────┘
- | | |
- curl / Burp payloads/ 6-gate check
- JS analysis PASS / REJECT
- tech fingerprint NEEDS-WORK
- | | |
- ┌─────▼───────────────▼───────────────▼──────┐
- │ engagements/<target>/ │
- │ │
- │ scope.md · findings.md · payload-log.md │
- │ coverage.md · tech-stack.md · notes.md │
- └────────────────────────────────────────────┘
- |
- ┌─────▼─────┐
- │ /report │ ──> Markdown + PDF
- └───────────┘
- ```
- Each command loads the right agent persona, methodology skill, and payload references. State is tracked per engagement in `engagements/<target>/`.
- <br>
- ---
- <br>
- ## Commands
- | Command | What It Does |
- |:---|:---|
- | `/scope <target>` | Define target scope and confirm authorization. **Must run first.** |
- | `/recon <target>` | Map attack surface — tech stack, endpoints, input vectors, WAF detection |
- | `/hunt <vuln-class>` | Test for a specific vulnerability class using OWASP methodology |
- | `/validate` | Run 6-gate quality check on all unvalidated findings |
- | `/report --full` | Generate complete pentest report (exec summary, findings, remediation) |
- | `/report --finding F-001` | Generate report for a single finding |
- | `/status` | Show engagement dashboard — findings, coverage, payload stats |
- <br>
- ### Hunt Targets
- ```bash
- /hunt injection # SQLi, NoSQLi, CMDi, SSTI, XXE
- /hunt auth-access # IDOR, JWT, OAuth, privilege escalation
- /hunt server-side # SSRF, path traversal, file upload, deserialization
- /hunt client-side # XSS, CSRF, open redirect
- /hunt session # Session fixation, token weakness, cookie security
- /hunt business-logic # Race conditions, workflow bypass, logic flaws
- /hunt config # Headers, CORS, TLS, info disclosure
- /hunt ai-llm # Prompt injection, LLM tool abuse, system prompt leakage
- # Or target specific sub-classes:
- /hunt sqli /hunt xss /hunt ssrf
- /hunt idor /hunt jwt /hunt prompt-injection
- ```
- <br>
- ---
- <br>
- ## Agent Personas
- 3 specialized personas, each activated by the relevant command:
- | Agent | Activated By | Personality | Role |
- |:---|:---|:---|:---|
- | **Recon Agent** | `/recon` | Systematic, methodical | Maps the full attack surface before exploitation |
- | **Hunter Agent** | `/hunt` | Creative, persistent | Tries bypass techniques, iterates on partial success |
- | **Validator Agent** | `/validate` | Skeptical, adversarial | Assumes false positive until proven otherwise |
- When no command is active, Claude behaves as a general security consultant.
- <br>
- ---
- <br>
- ## Validation Gate
- Every finding must pass **all 6 gates** to reach the report. One failure = REJECTED or NEEDS-WORK.
- ```
- Finding ──> Gate 1: Reproducible PoC?
- Gate 2: HTTP evidence captured?
- Gate 3: Impact verified (not theoretical)?
- Gate 4: Target in scope?
- Gate 5: Real vulnerability (not informational)?
- Gate 6: Client can reproduce it?
- │
- ┌──────────┼──────────┐
- │ │ │
- VALIDATED REJECTED NEEDS-WORK
- (→ report) (killed) (fix & retry)
- ```
- This process eliminates false positives, ensures evidence quality, and produces findings that clients can verify independently.
- <br>
- ---
- <br>
- ## Vulnerability Coverage
- <details>
- <summary><b>18 Vulnerability Classes</b> — click to expand</summary>
- <br>
- | Class | Sub-Classes |
- |:---|:---|
- | **SQL Injection** | Union, blind, time-based, error-based, auth bypass |
- | **XSS** | Reflected, stored, DOM, CSP bypass, polyglots |
- | **SSRF** | Internal access, cloud metadata, protocol abuse, IP bypass |
- | **SSTI** | Jinja2, Twig, Freemarker, Pebble, Mako, ERB |
- | **Command Injection** | Metacharacters, blind detection, space/quote bypass |
- | **XXE** | Classic, blind OOB, SVG upload, XInclude, PHP filter |
- | **Path Traversal** | Encoding bypass, null byte, overlong UTF-8 |
- | **File Upload** | Extension bypass, MIME spoof, magic bytes, polyglots |
- | **IDOR** | Sequential ID, UUID harvest, GraphQL node, HPP |
- | **JWT Attacks** | alg:none, RS256→HS256, KID injection, claim tampering |
- | **OAuth/OIDC** | Redirect URI bypass, state absence, PKCE downgrade |
- | **NoSQL Injection** | MongoDB operator injection, $regex blind, $where |
- | **Deserialization** | Java/PHP/Python/.NET/Ruby/YAML gadgets |
- | **CSRF** | Auto-submit forms, JSON CSRF, SameSite bypass |
- | **Open Redirect** | Protocol-relative, encoding chains, @ symbol tricks |
- | **Request Smuggling** | CL.TE, TE.CL, HTTP/2 downgrade, TE obfuscation |
- | **Race Condition** | TOCTOU, coupon reuse, rate limit bypass, double spend |
- | **Prompt Injection** | Direct override, system prompt extraction, persona hijack, encoding bypass, tool abuse, indirect injection |
- </details>
- <br>
- ---
- <br>
- ## Project Structure
- ```
- claude-pentest-skills/
- ├── commands/
- │ ├── scope.md # /scope — define target authorization
- │ ├── recon.md # /recon — map attack surface
- │ ├── hunt.md # /hunt — test vulnerability class
- │ ├── validate.md # /validate — 6-gate quality check
- │ ├── report.md # /report — generate pentest report
- │ └── status.md # /status — engagement dashboard
- │
- ├── agents/ # Agent persona definitions
- │ ├── recon-agent.md
- │ ├── hunter-agent.md
- │ └── validator-agent.md
- │
- ├── skills/
- │ ├── recon.md # Reconnaissance phases
- │ ├── validate.md # 6-gate validation process
- │ ├── report.md # Report templates + CVSS guide
- │ └── hunting/ # Per-vuln-class methodology
- │ ├── injection.md │ auth-access.md │ server-side.md
- │ ├── client-side.md │ session.md │ business-logic.md
- │ ├── config.md │ ai-llm.md
- │
- ├── payloads/ # Methodology + payload references
- │ ├── sqli.md │ xss.md │ ssrf.md │ ssti.md │ xxe.md
- │ ├── cmdi.md │ idor.md │ jwt.md │ oauth.md │ nosqli.md
- │ ├── csrf.md │ path-traversal.md │ file-upload.md
- │ ├── deserialization.md │ open-redirect.md
- │ ├── request-smuggling.md│ race-condition.md
- │ └── prompt-injection.md
- │
- ├── mcp/ # MCP server integration docs
- │ └── burp-suite/ # Burp Suite proxy setup
- │
- ├── tools/ # Utilities
- │ └── md2pdf.py # Markdown → styled PDF report
- │
- ├── engagements/ # Per-target state (gitignored)
- │ └── <target>/
- │ ├── scope.md │ findings.md │ payload-log.md
- │ ├── coverage.md │ tech-stack.md │ notes.md
- │ └── report-*.md / report-*.pdf
- │
- ├── local-payloads/ # Full curated payloads (gitignored)
- ├── CLAUDE.md # Master config for Claude Code
- └── .mcp.json.example # MCP config template
- ```
- <br>
- ---
- <br>
- ## Tool Integration
- | Tool | Integration | Use |
- |:---|:---|:---|
- | **Burp Suite** | MCP server | Proxy, traffic analysis, request replay |
- | **SQLMap** | Bash (post-detection) | Automated SQL injection exploitation |
- | **Commix** | Bash (post-detection) | Automated command injection exploitation |
- | **Custom scripts** | Claude generates on the fly | Race conditions, token analysis, encoding |
- | **md2pdf.py** | Python (weasyprint) | Convert report markdown to styled PDF |
- > SQLMap and Commix are used **only after manual detection** confirms the vulnerability. Never as first-pass scanners.
- <br>
- ---
- <br>
- ## Local Payloads
- The public `payloads/` directory contains methodology and payload references. For curated payload lists with full exploit code, add them to `local-payloads/` (gitignored):
- ```bash
- mkdir local-payloads
- # Add your curated .md files with full payloads here
- # The hunt skills will reference both payloads/ and local-payloads/
- ```
- <br>
- ---
- <br>
- ## Safety Rules
- These are enforced in `CLAUDE.md`. Non-negotiable.
- ```
- 1. SCOPE FIRST /scope must run before any other command
- 2. CHECK EVERY REQUEST verify against scope.md before sending
- 3. LOG BEFORE ANALYZE write payload to log BEFORE reading response
- 4. NO OUT-OF-SCOPE refuse requests to excluded domains/paths
- 5. ASK IF UNCERTAIN stop and confirm with user when scope is ambiguous
- 6. WARN ON DESTRUCTIVE get explicit approval for DELETE/data modification
- ```
- <br>
- ---
- <br>
- ## Contributing
- Contributions are welcome. Please read **[CONTRIBUTING.md](CONTRIBUTING.md)** before opening a pull request.
- <br>
- ---
- <br>
- <div align="center">
- **For authorized security testing only.**
- <br>
- Only test systems you own or have explicit written permission to test.
- </div>
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.