agentleFS
Sign inStart free
batterfried-philosophy172batterfried-philosophy172/Agent-Startup-Skills/skills/security-auditor-saas/SKILL.md

security-auditor-saas

Skill2 starsChanged 7 months agoMITView on GitHub

Application security agent that audits code for OWASP Top 10 vulnerabilities, hardcoded secrets, and common security flaws. Triggers on: security audit, vulnerability scan, OWASP check, security review, penetration test, hardening.

  • Reads credentials

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 1

    1. Aizaz-Noor/Agent-Startup-Skills★ 2100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository8 other files it gives its agents.

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:

    After code and tests are complete

    line 18
  2. Distinctive:

    When the user asks "is this code secure?"

    line 20
  3. Distinctive:

    All 10 OWASP categories are checked

    line 89
  4. Distinctive:

    All Critical/High findings are remediated

    line 90

≈ “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 — Hardening Agent

Purpose

Identify and remediate security vulnerabilities before the product is deployed. Prevent data breaches, unauthorized access, and common attack vectors.

When to Use

  • After code and tests are complete
  • Before deployment planning
  • When the user asks "is this code secure?"

Audit Checklist (OWASP Top 10 Aligned)

1. Injection (SQL, NoSQL, Command)

  • All database queries use parameterized statements or ORM
  • No string concatenation in queries
  • User input is never passed directly to system commands

2. Broken Authentication

  • Passwords are hashed with bcrypt/argon2 (never plain text, never MD5/SHA)
  • Sessions expire after a reasonable timeout
  • Login has rate limiting or brute-force protection
  • Password reset tokens are single-use and time-limited

3. Sensitive Data Exposure

  • No secrets in source code (API keys, passwords, tokens)
  • .env files are in .gitignore
  • HTTPS is enforced in production
  • Sensitive data is not logged

4. Broken Access Control

  • Users cannot access other users' data by changing IDs in URLs
  • Admin routes are protected with role checks
  • API endpoints verify the requesting user's permissions

5. Security Misconfiguration

  • CORS is configured to allow only known origins
  • Debug mode is disabled in production config
  • Default credentials are changed
  • Error messages do not expose stack traces to users

6. Cross-Site Scripting (XSS)

  • All user-generated content is escaped/sanitized before rendering
  • Content-Security-Policy headers are set
  • React/Vue/Angular auto-escaping is not bypassed (no dangerouslySetInnerHTML)

7. Cross-Site Request Forgery (CSRF)

  • CSRF tokens are used on state-changing forms
  • SameSite cookie attribute is set

8. Insecure Dependencies

  • No known vulnerable dependencies (check npm audit / pip audit)
  • Dependencies are pinned to specific versions

9. Insufficient Logging

  • Failed login attempts are logged
  • Access to sensitive data is logged
  • Logs do not contain passwords or tokens

10. Input Validation

  • All inputs have type, length, and format validation
  • File uploads are restricted by type and size
  • Email addresses are validated

Output

Produce a security_audit.md with:

#FindingSeverityLocationRemediation
1Hardcoded API keyCRITICALsrc/lib/api.js:14Move to .env

Rules

  • Critical/High findings MUST be fixed before deployment.
  • Present fixes to the CEO for approval.
  • Re-audit after fixes are applied.

Exit Criteria

  • All 10 OWASP categories are checked
  • All Critical/High findings are remediated
  • Audit report is complete with pass/fail for each category

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