agentleFS
jgamaraalvjgamaraalv/delivery-loop/.claude/skills/owasp-security-review/SKILL.md

owasp-security-review

Skill0 starsChanged 5 months agoMITView on GitHub

Review code and architectures against the OWASP Top 10:2025. Use to audit for vulnerabilities, guide remediation, or write secure code. Triggers: "security review", "OWASP audit", "check for vulnerabilities", "is this code secure".

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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
  1. Distinctive:

    Use these severity levels when reporting findings:

    line 27
  2. Distinctive:

    Read the feature/codebase to understand its scope.

    line 67
  3. Distinctive:

    When a vulnerability is identified:

    line 76
  4. Distinctive:

    When reporting security findings, use the template in template.md for each finding.

    line 106

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

OWASP Top 10:2025 Security Review

<quick_reference>

Quick reference

#CategoryKey riskAvg incidence
A01Broken Access ControlUnauthorized data access, privilege escalation, SSRF, CSRF3.74%
A02Security MisconfigurationDefault creds, verbose errors, missing hardening, XXE3.00%
A03Software Supply Chain FailuresVulnerable/malicious dependencies, compromised build pipelines5.72%
A04Cryptographic FailuresWeak algorithms, hardcoded keys, missing encryption, weak hashing3.80%
A05InjectionSQLi, XSS, command injection, LDAP/XPath/EL injection3.08%
A06Insecure DesignMissing threat modeling, business logic flaws, insufficient controls1.86%
A07Authentication FailuresCredential stuffing, weak passwords, session fixation, missing MFA2.92%
A08Software/Data Integrity FailuresUnsigned updates, insecure deserialization, untrusted CDN code2.75%
A09Security Logging & Alerting FailuresMissing audit logs, no alerting, log injection, sensitive data in logs3.91%
A10Mishandling of Exceptional ConditionsFailing open, info leakage via errors, unchecked return values2.95%

Severity classification

Use these severity levels when reporting findings:

  • Critical: Directly exploitable, leads to full system compromise or mass data breach (e.g., SQLi with no parameterization, hardcoded admin credentials, missing auth on admin endpoints).
  • High: Exploitable with moderate effort, significant data exposure or privilege escalation (e.g., IDOR, weak password hashing, SSRF, deserialization of untrusted data).
  • Medium: Exploitable under specific conditions, limited impact (e.g., missing CSRF protection, verbose error messages, missing security headers).
  • Low: Defense-in-depth issue, minimal direct impact (e.g., missing rate limiting, incomplete logging, suboptimal crypto configuration).

</quick_reference>

<workflow>

Workflows

<phase_1_code_review>

Code review for security

Systematically check the code against each relevant category:

  1. Identify the code's surface area — Does it handle auth? User input? File uploads? External data? Crypto? Error responses?
  2. Select relevant categories from the table above based on the surface area.
  3. Load the reference file for each relevant category and check the code against the "What to look for" section.
  4. Report findings grouped by category with severity (Critical/High/Medium/Low), the specific code location, and a concrete fix.

Priority order for review (highest impact first):

  • [CRITICAL] Input handling code → A05 (Injection), A01 (Access Control)
  • [CRITICAL] Auth/session code → A07 (Authentication), A01 (Access Control)
  • [HIGH] Data storage/transmission → A04 (Cryptographic Failures)
  • [HIGH] Configuration/deployment → A02 (Security Misconfiguration)
  • [HIGH] Dependencies → A03 (Supply Chain)
  • [MEDIUM] Error handling → A10 (Exceptional Conditions), A09 (Logging)
  • [MEDIUM] Architecture/design → A06 (Insecure Design)
  • [MEDIUM] Data integrity → A08 (Integrity Failures) </phase_1_code_review>

<phase_2_audit_checklist>

Security audit checklist

Generate a checklist for a feature or codebase:

  1. Read the feature/codebase to understand its scope.
  2. For each of the 10 categories, determine if it applies.
  3. For applicable categories, load the reference file and produce a checklist of items to verify.
  4. Output a markdown checklist grouped by category. </phase_2_audit_checklist>

<phase_3_remediation>

Remediation guidance

When a vulnerability is identified:

  1. Classify it into the correct OWASP category.
  2. Load the corresponding reference file.
  3. Apply the prevention checklist to produce a specific, actionable fix.
  4. Provide a code example of the fix when possible. </phase_3_remediation>
</workflow><references>

Reference files

Load the relevant file when you need detailed guidance for a specific category:

  • A01 Broken Access Control — authorization checks, IDOR, CORS, CSRF, path traversal: references/a01-broken-access-control.md
  • A02 Security Misconfiguration — hardening, default creds, error messages, headers, XXE: references/a02-security-misconfiguration.md
  • A03 Supply Chain Failures — dependency management, SBOM, build pipeline security: references/a03-supply-chain-failures.md
  • A04 Cryptographic Failures — encryption, hashing, key management, TLS, PRNG: references/a04-cryptographic-failures.md
  • A05 Injection — SQL, XSS, command, ORM, LDAP, template injection: references/a05-injection.md
  • A06 Insecure Design — threat modeling, business logic, secure SDLC: references/a06-insecure-design.md
  • A07 Authentication Failures — credential stuffing, MFA, session management, password policy: references/a07-authentication-failures.md
  • A08 Integrity Failures — deserialization, code signing, untrusted sources, CDN trust: references/a08-integrity-failures.md
  • A09 Logging & Alerting — audit trails, log injection, alerting, sensitive data in logs: references/a09-logging-alerting-failures.md
  • A10 Exceptional Conditions — error handling, fail-closed, resource cleanup, info leakage: references/a10-exceptional-conditions.md
</references><output> When reporting security findings, use the template in [template.md](template.md) for each finding. </output>

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.