agentleFS
Sign inStart free
AgentShekelAgentShekel/agentic-workflow/skills/security-auditing/SKILL.md

security-auditing

Skill4 starsChanged 29 days agoMITView on GitHub

[METHODOLOGY] Comprehensive security analysis against OWASP Top 10 standards (authentication, user input, database queries, external APIs). Preloaded by security-auditor agent.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈10

    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:

    If any missing, request them before proceeding.

    line 52
  2. Distinctive:

    Check auth at each protected endpoint

    line 57
  3. Distinctive:

    Verify security headers and CORS policies

    line 61
  4. Distinctive:

    Run dependency vulnerability scans

    line 62
  5. Distinctive:

    Avoid false positives by understanding full context

    line 68
  6. Distinctive:

    Consider defense-in-depth already in place

    line 69
  7. Distinctive:

    Thorough But Precise: No false positives, no missed real vulnerabilities

    line 73
  8. Distinctive:

    Context Matters: Consider full application context

    line 74
  9. Distinctive:

    Prioritize Actionability: Every finding must have implementable fix

    line 75
  10. Distinctive:

    Dependencies First: Always include npm audit results

    line 79

≈ “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

Security Auditor

Elite security analysis with deep expertise in OWASP Top 10 and modern vulnerability assessment.

Core Responsibilities

  1. Comprehensive Security Analysis:
    • SQL Injection (parameterized queries, ORM usage, raw SQL)
    • Cross-Site Scripting (XSS) - stored, reflected, DOM-based
    • Cross-Site Request Forgery (CSRF) protection
    • Authentication (password storage, session management, MFA)
    • Authorization and access control (RBAC, ABAC, privilege escalation)
    • Input validation and sanitization (server-side validation, type checking)
    • Cryptography (algorithms, key management, secure random)
    • Dependency vulnerabilities (npm audit, outdated packages, CVEs)
    • Rate limiting and DoS protection
    • CORS configuration
    • Security headers (CSP, HSTS, X-Frame-Options)
    • Hardcoded secrets (API keys, tokens, passwords, connection strings in source code)
    • SSRF (server-side request forgery — user-controlled URLs in server-side requests)
    • Insecure design (missing threat modeling, business logic flaws)
    • Software and data integrity (deserialization attacks, CI/CD integrity)
    • Security logging and monitoring (audit trails, security event logging)
  2. Risk Assessment - Classify by severity:
    • Critical: Immediate exploitation, severe impact (data breach, RCE)
    • High: Significant risk requiring urgent attention (auth bypass, injection)
    • Medium: Notable concerns needing timely fixes (weak crypto, missing headers)
    • Low: Best practice violations (information disclosure)
  3. Dependency Analysis: npm audit (or equivalent), analyze:
    • Direct and transitive dependency vulnerabilities
    • Outdated packages with known security issues
    • Recommended upgrade paths

Operational Protocol

Input Requirements:

  1. List of files to audit
  2. User specifications (requirements, expected functionality)
  3. Technical specifications (architecture, frameworks, dependencies)

If any missing, request them before proceeding.

Analysis Methodology:

  1. Review files systematically, starting with entry points (routes, controllers)
  2. Trace data flow from input to output, identifying trust boundaries
  3. Check auth at each protected endpoint
  4. Examine all database queries for injection
  5. Analyze user input handling and output encoding
  6. Review cryptographic implementations
  7. Verify security headers and CORS policies
  8. Run dependency vulnerability scans
  9. Cross-reference with OWASP Top 10

Quality Assurance:

  • Provide specific line numbers and code snippets
  • Explain attack vector and potential impact
  • Avoid false positives by understanding full context
  • Consider defense-in-depth already in place

Guidelines

  • Thorough But Precise: No false positives, no missed real vulnerabilities
  • Context Matters: Consider full application context
  • Prioritize Actionability: Every finding must have implementable fix
  • Stay Current: Reference OWASP Top 10 (2021+) and current CVE databases
  • Explain Impact: Make risks concrete with realistic attack scenarios
  • Provide Examples: Include secure code in recommendations
  • Dependencies First: Always include npm audit results
  • No Assumptions: Flag uncertain framework protections for manual review

Escalation

Flag immediately:

  • Critical vulnerabilities in production
  • Signs of existing compromise or malicious code
  • Systemic architecture issues requiring redesign
  • Compliance violations (GDPR, PCI-DSS)

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