agentleFS
troskatertroskater/flowdeck-claude/skills/security-scan/SKILL.md

security-scan

Skill0 starsChanged 23 days agoMITView on GitHub

Pre-commit security scan covering secrets, injection, auth, CVE dependencies. Returns PASS/FAIL verdict with severity-ranked findings and specific remediations.

89 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use django-security, deployment-patterns and 6 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • mstuder-slalomSkill

    django-security

    Django security best practices, authentication, authorization, CSRF protection, SQL injection prevention, XSS prevention, and secure deployment configurations.

    Also in 5 projects that use this

  • royaluniondesign-sysSkill

    deployment-patterns

    Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications.

    Also in 5 projects that use this

  • mstuder-slalomSkill

    springboot-security

    Spring Security best practices for authn/authz, validation, CSRF, secrets, headers, rate limiting, and dependency security in Java Spring Boot services.

    Also in 4 projects that use this

  • DonTiziSkill

    dependency-check

    Analyze project dependencies for outdated packages, security vulnerabilities, and licensing issues. Use for dependency audits and maintenance.

    Also in 3 projects that use this

  • RojiosSkill

    security-bounty-hunter

    Hunt for exploitable, bounty-worthy security issues in repositories. Focuses on remotely reachable vulnerabilities that qualify for real reports instead of noisy local-only findings.

    Also in 3 projects that use this

  • royaluniondesign-sysSkill

    search-first

    Research-before-coding workflow. Search for existing tools, libraries, and patterns before writing custom code. Invokes the researcher agent.

    Also in 6 projects that use this

  • +1 more from mstuder-slalom

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 80 edited versions we read keep these.

  • 10

    Distinctive

    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:

    Before merging any PR that touches auth, data access, or API routes

    line 14
  2. Distinctive:

    Before every production deployment

    line 15
  3. Distinctive:

    When adding new dependencies

    line 16
  4. Distinctive:

    When changing environment variable handling

    line 17
  5. Distinctive:

    Every finding includes a specific remediation

    line 22
  6. Distinctive:

    No exceptions without documented risk acceptance

    line 24
  7. Distinctive:

    Check for hardcoded secrets (grep patterns)

    line 28
  8. Distinctive:

    Check for injection vulnerabilities (SQL, command, template)

    line 29
  9. Distinctive:

    Verify auth middleware on protected routes

    line 30
  10. Distinctive:

    Check input validation at API boundaries

    line 31

“Common” is measured: kept by at least 6 in 10 of the 80 edited versions of this file we could read. “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 Scan Skill

Catches security issues before they reach production. Returns a severity-ranked report with specific remediations.

When to Activate

Activate:

  • Before merging any PR that touches auth, data access, or API routes
  • Before every production deployment
  • When adding new dependencies
  • When changing environment variable handling

Core Principles

  • Security takes priority over convenience
  • Every finding includes a specific remediation
  • CRITICAL or HIGH = must fix before merge
  • No exceptions without documented risk acceptance

Workflow

  1. Check for hardcoded secrets (grep patterns)
  2. Check for injection vulnerabilities (SQL, command, template)
  3. Verify auth middleware on protected routes
  4. Check input validation at API boundaries
  5. Run npm audit --audit-level=moderate
  6. Review sensitive data in logs
  7. Produce verdict

OWASP Top 10 Quick Reference

IDNameCheck For
A01Broken Access ControlMissing auth checks, IDOR, privilege escalation
A02Cryptographic FailuresHTTP for sensitive data, MD5/SHA1 for passwords
A03InjectionSQL/NoSQL/cmd/template injection via string concat
A04Insecure DesignMissing rate limiting, no lockout after failed logins
A05Security MisconfigurationDebug mode in prod, default credentials, verbose errors
A06Vulnerable ComponentsCVEs in dependencies (run npm audit)
A07Auth FailuresMissing middleware, weak JWT, no session invalidation
A08Integrity FailuresMissing input validation, unsafe deserialization
A09Logging FailuresPasswords/tokens in logs, insufficient logging
A10SSRFUser-controlled URLs fetched by server without validation

Scan Commands

# Dependency vulnerabilities
npm audit --audit-level=moderate

# Hardcoded secrets (grep patterns)
grep -r "password\s*=\s*['\"]" src/ --include="*.ts"
grep -r "api_key\s*=\s*['\"]" src/ --include="*.ts"
grep -r "secret\s*=\s*['\"]" src/ --include="*.ts"

# SQL string concatenation
grep -r "query\`.*\${" src/ --include="*.ts"
grep -rn "query.*+.*req\." src/ --include="*.ts"

Output Format

## Security Scan Report

### 🔴 Critical
| # | File | Line | Issue | Remediation |
|---|------|------|-------|-------------|

### 🟠 High
| # | File | Line | Issue | Remediation |
|---|------|------|-------|-------------|

### 🟡 Medium
| # | File | Line | Issue | Remediation |
|---|------|------|-------|-------------|

### Dependencies
- npm audit: 0 critical, 0 high, 2 moderate (tracked)

### Verdict: PASS ✅ | FAIL ❌ | PASS_WITH_NOTES ⚠️

FAIL if any Critical or High findings.
PASS_WITH_NOTES if only Medium or Low findings.

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.