usap-skills / pentest
CLAUDE.md4 starsChanged 2 months agoApache-2.0View on GitHub
The Pentest domain contains skills for conducting authorized penetration testing and compiling the results into stakeholder-ready reports. Skills span structured web application assessment (OWASP Testing Guide v4.2, OWASP Top 10 2021) and penetration test report generation (PTES, OWASP reporting standards). Pentest skills operate strictly within written authorization and defined Rules of Engagement. They classify findings by OWASP category, CVSS v3.1, and MITRE ATT&CK, assess real-world exploitability, and produce sanitized remediation guidance — never weaponized exploit code. Active-testing skills set human_approval_required:…
In this repository100 other files it gives its agents.
- agents/CLAUDE.mdCLAUDE.md
- appsec-devsecops/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- cloud-infra/CLAUDE.mdCLAUDE.md
- detection/CLAUDE.mdCLAUDE.md
- governance/CLAUDE.mdCLAUDE.md
- identity-access/CLAUDE.mdCLAUDE.md
- platform-ai/CLAUDE.mdCLAUDE.md
- red-team/CLAUDE.mdCLAUDE.md
- response/CLAUDE.mdCLAUDE.md
- risk-compliance/CLAUDE.mdCLAUDE.md
- system-security/CLAUDE.mdCLAUDE.md
- webapp-security/CLAUDE.mdCLAUDE.md
- agent-integrity-monitorSkill
- ai-agent-securitySkill
- ai-ethics-governanceSkill
- ai-red-teamingSkill
- api-security-postureSkill
- appsec-code-reviewSkill
- appsec-customizeSkill
- attack-path-analysisSkill
- attack-surface-managementSkill
- behavioral-analyticsSkill
- build-integritySkill
- ciso-brief-generatorSkill
- cloud-security-postureSkill
- cloud-workload-protectionSkill
- compliance-mappingSkill
- container-image-scanSkill
- containment-advisorSkill
- continuous-pentestingSkill
- credential-attacksSkill
- cryptography-key-managementSkill
- cyber-insuranceSkill
- data-security-classificationSkill
- deception-honeypotSkill
- detection-engineeringSkill
- devsecops-pipelineSkill
- endpoint-os-securitySkill
- enterprise-risk-assessmentSkill
- findings-trackerSkill
- finding-triageSkill
- forensicsSkill
- guardrailSkill
- iac-securitySkill
- identity-access-riskSkill
- incident-classificationSkill
- incident-commanderSkill
- insider-physical-riskSkill
- internal-audit-assuranceSkill
- knowledge-managementSkill
- metrics-reportingSkill
- network-exposureSkill
- orchestratorSkill
- os-hardeningSkill
- ot-iot-device-securitySkill
- owasp-top10-classifierSkill
- patch-candidateSkill
- pentest-reportingSkill
- persona-coverage-auditSkill
- The first 60 shown.
The file
We split this CLAUDE.md into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 22
All skill paths are relative from the repository root as pentest/<slug>/.
- Distinctive: line 37
No active testing without confirmed written authorization (target, test window, Rules of Engagement).
- Distinctive: line 39
No weaponized exploit code in any output — proof-of-concept material is sanitized to reproduction steps.
- Very specific: line 47
Validate scope and authorization as step zero: No reconnaissance, scanning, or exploitation guidance is produced until written …
- Distinctive: line 51
Deduplicate across sources before reporting: When findings arrive from multiple skills (web-app-pentest, network-pentest, …
≈ “Common” is an estimate: at least 1 in 5 of the 27,641 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Pentest Domain — CLAUDE.md
Purpose
The Pentest domain contains skills for conducting authorized penetration testing and compiling the results into stakeholder-ready reports. Skills span structured web application assessment (OWASP Testing Guide v4.2, OWASP Top 10 2021) and penetration test report generation (PTES, OWASP reporting standards).
Pentest skills operate strictly within written authorization and defined Rules of Engagement. They classify findings by OWASP category, CVSS v3.1, and MITRE ATT&CK, assess real-world exploitability, and produce sanitized remediation guidance — never weaponized exploit code. Active-testing skills set human_approval_required: true.
Subdomains covered by this domain:
- Web application and API penetration testing (OWASP Top 10)
- Penetration test report generation and CVSS-based risk rating
Skills Catalog
| Skill | Slug | Primary Tool | MITRE Coverage |
| web-app-pentest | pentest/web-app-pentest | web-app-pentest_tool.py | T1190, T1078, T1110, T1040, T1090 |
| pentest-reporting | pentest/pentest-reporting | pentest-reporting_tool.py | (Reporting / governance) |
All skill paths are relative from the repository root as pentest/<slug>/.
Python Tools Reference
| Tool | Path | Purpose | Key Args |
| web-app-pentest_tool.py | pentest/web-app-pentest/scripts/web-app-pentest_tool.py | Emits the skill status payload for orchestration | --input, --output |
| pentest-reporting_tool.py | pentest/pentest-reporting/scripts/pentest-reporting_tool.py | Emits the skill status payload for orchestration | --input, --output |
Authorization and Safety
- No active testing without confirmed written authorization (target, test window, Rules of Engagement).
- Out-of-scope systems are never tested, even when access is incidentally available.
- No weaponized exploit code in any output — proof-of-concept material is sanitized to reproduction steps.
- Active-testing findings set
human_approval_required: true. - Critical findings (RCE, auth bypass with data access) escalate immediately, ahead of the full report.
Domain Best Practices
- Validate scope and authorization as step zero. No reconnaissance, scanning, or exploitation guidance is produced until written authorization and the target list are confirmed. Missing authorization returns an
adviseoutput requesting the RoE. - Rate every finding with CVSS v3.1 and a patch SLA. Severity drives the remediation deadline: Critical = 24h, High = 7d, Medium = 30d, Low = 90d.
- Deduplicate across sources before reporting. When findings arrive from multiple skills (web-app-pentest, network-pentest, red-team-operations, sast-dast-coordinator), merge duplicates and keep the highest severity.
- Translate technical severity into business impact for executives. A report read only by engineers has failed half its audience — pair each finding with the business consequence.
- Route findings onward.
sast-dast-coordinatorcorrelates code-level findings;compliance-mappingmaps control gaps;findings-trackertracks remediation to closure.
Related Domains
appsec-devsecops/— sast-dast-coordinator correlates pentest findings with code-level findingsred-team/— red-team-operations and safe-exploitation feed pentest-reportingrisk-compliance/— compliance-mapping consumes findings for control-gap analysis
Path Reference
pentest/<slug>/
README.md -- skill overview and quick commands
SKILL.md -- full skill specification and methodology
scripts/ -- executable Python tools
references/ -- supporting documentation
expected_outputs/ -- representative tool outputs for validation
assets/ -- supporting data filesDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

