SKILL.md
OWASP Audit — Source Code Security Review
Perform a systematic security audit of application source code against the OWASP Top 10:2025. Every candidate is traced, then independently challenged, before it becomes a finding. Coverage is recorded per surface and trust boundary, so "clean" means someone actually read the code.
Cross-references:
api-auditfor a surface-driven pass over every API endpoint (shares the recon, verification, and orchestration references)web-pentest"Combined white-box + black-box mode" when you have both the source and a running instance you're authorized to testbusiness-logic-testingto prove race conditions and logic flaws dynamically (A06)dependency-auditfor the full A03 supply-chain picture;secrets-auditfor leaked credentialsthreat-modelingfor the principal / trust-boundary vocabulary used in reconfinding-triageto take a single finding from this report to a defensible disposition
Authorization and Mode
Only audit code the user owns or is authorized to review. Any live check (for example curl -I against a deployed
origin) needs the same authorization for that host and stays non-destructive.