agentleFS
Sign inStart free
NikoxkxNikoxkx/Agent-Skills/skills/security/owasp-checker/SKILL.md

owasp-checker

Skill1 starsChanged 5 months agoApache-2.0View on GitHub

Reviews a web application against the OWASP Top 10 vulnerabilities. Use when performing a security review or preparing a security assessment report.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 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.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Look for specific anti-patterns (e.g., string concatenation in SQL queries, missing HttpOnly on cookies, direct object references without …

    line 51
  2. Distinctive:

    Test with real (or realistic) data and different user roles.

    line 52
  3. Very specific:

    Use CVSS or a simple Critical/High/Medium/Low.

    line 55
  4. Distinctive:

    Client-side only protections: Always flag as insufficient.

    line 74

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

Overview

Reviews a web application against the OWASP Top 10 (2021) vulnerabilities with code-level indicators, automated scanner integration, manual test procedures, remediation examples, and a structured finding report template. Provides a practical, developer-friendly checklist that can be used in code reviews, architecture reviews, or as input to a penetration test.

When to Use This Skill

  • Performing a security review of a web application or feature.
  • Preparing for a penetration test or bug bounty launch.
  • Training developers on common web vulnerabilities.
  • The user asks for an "OWASP Top 10 review" or "web app security audit".

Prerequisites

  • Access to the application source code and a running instance (staging ideal).
  • Ability to perform both automated scans and manual testing.
  • (Helpful) Previous findings or known issues.

Steps

  1. OWASP Top 10 2021 quick reference (with detection + remediation for each):
    • A01:2021 – Broken Access Control
    • A02:2021 – Cryptographic Failures
    • A03:2021 – Injection (SQL, NoSQL, Command, etc.)
    • A04:2021 – Insecure Design
    • A05:2021 – Security Misconfiguration
    • A06:2021 – Vulnerable and Outdated Components
    • A07:2021 – Identification and Authentication Failures
    • A08:2021 – Software and Data Integrity Failures
    • A09:2021 – Security Logging and Monitoring Failures
    • A10:2021 – Server-Side Request Forgery (SSRF)
  2. Automated scanning:
    • DAST: OWASP ZAP, Burp Suite, Nikto, Nuclei.
    • SAST: Semgrep (with OWASP rules), SonarQube, CodeQL, Snyk Code.
    • SCA: Snyk, Dependabot, Trivy.
    • Record findings with location and severity.
  3. Manual / code review per category:
    • Look for specific anti-patterns (e.g., string concatenation in SQL queries, missing HttpOnly on cookies, direct object references without authz checks, etc.).
    • Test with real (or realistic) data and different user roles.
  4. Prioritized findings:
    • Use CVSS or a simple Critical/High/Medium/Low.
    • Include reproduction steps, impact, and concrete remediation (with code example when possible).
  5. Output:
    • Structured OWASP Top 10 review report (Markdown) with:
      • Summary table (Axx | Status | Severity | # Findings)
      • Detailed findings per category (or "None found" with evidence of review).
      • Positive security controls observed.
      • Prioritized remediation roadmap.
    • Code search patterns / Semgrep rules for the common issues.
    • Manual test checklist.

Examples

A complete OWASP Top 10 review for a realistic web application (with findings in Broken Access Control, Injection, Security Misconfiguration, Vulnerable Components, and Identification failures, plus "clean" categories with the checks that were performed) is included, along with remediation code snippets and a sample executive summary.

Edge Cases & Error Handling

  • Modern frameworks mitigate many issues by default (e.g., parameterized queries in ORMs, auto-escaping in templates): still verify they are actually being used and not bypassed.
  • Client-side only protections: Always flag as insufficient.
  • Third-party components: Cross-reference with SCA results.

Verification

  1. The review covers all 10 categories with evidence (scans + code review + manual tests).
  2. High/critical findings have clear reproduction and impact.
  3. Remediation guidance is specific and actionable (not "fix the vulnerability").
  4. Re-review after fixes shows improvement.
  5. Success: The application has a documented security posture against the OWASP Top 10, with known gaps tracked and prioritized.

References

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.

Check your setup, free