From communitytools
Orchestrates a professional web/API/cloud penetration test from a scope file with mandatory surface expansion, OWASP attack-class coverage, reversible exploitation, and PDF report generation.
How this skill is triggered — by the user, by Claude, or both
Slash command
/communitytools:pentest-engagementThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Orchestrates a scoped pentest end-to-end via the `pentest-engagement` workflow. It is the breadth-complete, coverage-gated counterpart to the flag-shaped `htb-solve` — same engines (`coordinator-loop`, `validate-findings`), but driven by an attack-class **coverage matrix** instead of a flag, with surface expansion and root-cause severity baked in.
Orchestrates a scoped pentest end-to-end via the pentest-engagement workflow. It is the breadth-complete, coverage-gated counterpart to the flag-shaped htb-solve — same engines (coordinator-loop, validate-findings), but driven by an attack-class coverage matrix instead of a flag, with surface expansion and root-cause severity baked in.
A web / API / cloud engagement defined by a scope file (assets, credentials, rules of engagement) — not a CTF/flag target. For HackTheBox/CTF use hackthebox (htb-solve) instead.
Workflow('pentest-engagement', { scope_file: 'projects/pentest/<engagement>-scope.md' })
or inline scope:
Workflow('pentest-engagement', { scope: { engagement_name, apex_domains:[], assets:[...], creds_env:[...], roe, business_tier } })
Options: maxConcurrent (default 3), dryRun (expand surface + work list only, no exploitation), max_experiments, business_tier, report (default true).
Write the scope file per reference/scope-file-format.md. Credentials are referenced by env-var name only and read from the repo .env via python3 tools/env-reader.py — never inline secret values.
env-reader creds, parse scope, OUTPUT_DIR = projects/pentest/<date>_<engagement>/, STARTED Slack (gated).crt.sh, certspotter, subfinder, origin-discovery for CDN/WAF-fronted hosts). Scope = the discovered surface, not the handoff. Builds the per-asset work list + seeds each asset's coverage matrix.coordinator-loop in coverage mode (drives the OWASP API+Web attack-class matrix to completion; reversible active exploitation; root-cause severity) → validate-findings (authoritative).attack-path-stitcher + risk-prioritiser across all validated findings → ranked org roadmap.INCOMPLETE_coverage with the untested classes named.npx claudepluginhub transilienceai/communitytoolsOrchestrates penetration testing workflows: reconnaissance, user-approved planning, deploys specialized agents for SQLi/XSS/SSRF attacks, aggregates findings, generates DOCX reports.
Guides scoping and executing penetration tests, including defining rules of engagement, selecting methodology, and building remediation processes for compliance.
Guides planning, execution, and follow-up of penetration tests with scope definition, threat enumeration, and budget considerations.