usap-skills / webapp-security
CLAUDE.md4 starsChanged 2 months agoApache-2.0View on GitHub
The webapp-security/ domain holds skills that triage, classify, and assess web-application and API security findings. Scope is the runtime surface — production webapps and API endpoints — and the OWASP Top 10 2025 + OWASP API Security Top 10 are the primary taxonomies. Build-time AppSec (SAST, dependency analysis, supply-chain) lives in appsec-devsecops/ and is not duplicated here. Skills in this domain produce structured triage payloads, not remediation actions. Mutating recommendations (WAF rule changes, account disablement, schema-rewrite proposals) are surfaced via…
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
- pentest/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
- 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
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 24
All paths are relative from the repository root.
- Distinctive: line 36
All three are stdlib-only and emit USAP's 11-field output contract.
≈ “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
Webapp Security Domain — CLAUDE.md
Purpose
The webapp-security/ domain holds skills that triage, classify, and assess web-application and API security findings. Scope is the runtime surface — production webapps and API endpoints — and the OWASP Top 10 2025 + OWASP API Security Top 10 are the primary taxonomies. Build-time AppSec (SAST, dependency analysis, supply-chain) lives in appsec-devsecops/ and is not duplicated here.
Skills in this domain produce structured triage payloads, not remediation actions. Mutating recommendations (WAF rule changes, account disablement, schema-rewrite proposals) are surfaced via human_approval_required: true and routed to cs-appsec-engineer (the orchestrator) or cs-incident-responder (active-exploit case).
Subdomains covered:
- Webapp finding triage (which OWASP category, what severity, who consumes it next)
- OWASP Top 10 2025 classification with confidence scoring
- API security posture assessment (OWASP API Top 10, BOLA / mass assignment / broken auth)
Skills Catalog
| Skill | Slug | Primary Tool | Frameworks (frontmatter) |
| webapp-risk-triage | webapp-security/webapp-risk-triage | webapp-risk-triage_tool.py | OWASP A01, A03, A05, A07; MITRE T1190 |
| owasp-top10-classifier | webapp-security/owasp-top10-classifier | owasp-top10-classifier_tool.py | OWASP A01–A10 (full set) |
| api-security-posture | webapp-security/api-security-posture | api-security-posture_tool.py | OWASP A01, A03, A07; MITRE T1078, T1190 |
All paths are relative from the repository root.
Python Tools Reference
| Tool | Path | Purpose | Key Args |
webapp-risk-triage_tool.py | webapp-security/webapp-risk-triage/scripts/webapp-risk-triage_tool.py | Map a webapp finding to OWASP + severity, recommend the next USAP skill | --input <finding.json>, --output {json,human} |
owasp-top10-classifier_tool.py | webapp-security/owasp-top10-classifier/scripts/owasp-top10-classifier_tool.py | Classify a finding description into OWASP Top 10 2025 categories with confidence | --input <finding.json>, --output {json,human} |
api-security-posture_tool.py | webapp-security/api-security-posture/scripts/api-security-posture_tool.py | Score an API surface (auth, rate limits, identification, mass-assignment) against OWASP API Top 10 | --input <api-spec.json>, --output {json,human} |
All three are stdlib-only and emit USAP's 11-field output contract.
Domain Best Practices
- Triage before scanning. A webapp finding without context (target URL, environment, auth state) cannot be prioritised. Always run
webapp-risk-triagebefore invoking a deeper scanner or pentest skill. The triage output names the right downstream skill. - OWASP category is a routing decision, not a verdict.
owasp-top10-classifierreturns ranked category candidates with confidence. Treat the top match as the routing key, not as a finding statement. The eventual finding statement still requires evidence corroboration. - API auth failures dominate the threat model. OWASP API Top 10's "Broken Object Level Authorization" (BOLA) is the most common real-world issue.
api-security-posturescores BOLA visibility first and weights it heaviest in the posture score. - Always emit a
next_agentsrecommendation. Triage skills must point to the next concrete USAP skill —appsec-devsecops/sast-dast-coordinatorfor build-time,response/incident-classificationfor production exploit,risk-compliance/risk-threat-modelingfor design-stage. Emptynext_agentsis an anti-pattern in this domain. human_approval_required: trueon any control change. WAF rule injection, schema rewrites, and account state changes are mutating actions — never auto-trigger. Surface them with confidence, evidence references, and a clear escalation owner role.
Workflow Patterns
Workflow 1: Production webapp alert → routing
webapp-risk-triage (classify finding, score severity, scope blast radius)
|
v
owasp-top10-classifier (refine OWASP category with confidence)
|
+--> [A01/A07 + production exploit] --> response/incident-classification
|
+--> [A03/A08 + design issue] --> risk-compliance/risk-threat-modeling
|
+--> [build-time gap] --> appsec-devsecops/sast-dast-coordinatorWorkflow 2: API security review
api-security-posture (score API surface against OWASP API Top 10)
|
v
[posture below threshold]
|
+--> appsec-devsecops/secure-sdlc (design changes)
+--> appsec-devsecops/security-requirements-review (PRD updates)
+--> identity-access/identity-access-risk (auth model review)Related Domains
appsec-devsecops/
Build-time AppSec is upstream of this domain. The SAST/DAST coordinator, supply-chain risk, and secure-SDLC skills run in CI; this domain handles their runtime equivalents. Findings flow both ways: a runtime triage may demand a build-time gate, and a CI finding may require runtime monitoring.
response/
Production exploit cases escalate from webapp-risk-triage straight into response/incident-classification. The triage output is structured exactly so the incident-classification skill consumes it without translation.
risk-compliance/
Design-stage webapp issues (architecture, threat-modelling gaps) route to risk-compliance/risk-threat-modeling rather than to incident response. The triage skill chooses which based on the finding's evidence references.
Path Reference
webapp-security/<slug>/
SKILL.md
README.md
references/workflow.md
assets/templates/output-template.json
expected_outputs/sample_output.json
scripts/<slug>_tool.pyInvoke any tool from the repo root:
python3 webapp-security/webapp-risk-triage/scripts/webapp-risk-triage_tool.py --output json
python3 webapp-security/owasp-top10-classifier/scripts/owasp-top10-classifier_tool.py --output json
python3 webapp-security/api-security-posture/scripts/api-security-posture_tool.py --output jsonEach tool emits a USAP 11-field contract payload by default. Pass --input <finding.json> to drive the analysis from real data.
Does 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.

