What problem does it solve? Manual web application penetration testing is slow, inconsistent, and easy to do unsafely. This Skill enforces a disciplined, authorization-gated pentest workflow where every finding requires reproducible proof and every active request stays inside a pre-declared scope. ## Core Features & Use Cases - Phased engagement workflow: Moves through engagement setup, optional source-code pre-recon, live read-only recon, per-class vulnerability analysis, proof-based exploitation, and structured reporting. - Hard safety guardrails: Requires written authorization before scanning, enforces a scope.txt allowlist on every request, rate-limits traffic, and demands approval for destructive payloads. - Proof-based findings: Promotes candidates through L1-L4 evidence levels and only reports L3/L4 findings with CVSS scoring, request/response proof, and reproduction steps. - Use Case: Point the agent at your own staging application, confirm authorization, and receive a structured pentest report covering SQLi, XSS, auth, IDOR, SSRF, and infrastructure misconfigurations with curl reproducers for each confirmed finding. ## Quick Start Ask the agent to pentest your staging application URL and reply authorized when it presents the engagement confirmation prompt.