agentleFS
Sign inStart free
imrangadzhievimrangadzhiev/anti-slop/skills/security-review/SKILL.md

security-review

Skill27 starsChanged 4 months agoMITView on GitHub

Review code for security issues before merge — authz gaps, injection, secrets, unsafe defaults, SSRF, path traversal. Use when reviewing a PR, auditing a diff, shipping auth/payments/uploads, or when the user asks for a security review or OWASP check.

192 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use linkerd-patterns, dependency-cve-sweep and 10 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.
  • xfstudioSkill

    linkerd-patterns

    Implement Linkerd service mesh patterns for lightweight, security-focused service mesh deployments. Use when setting up Linkerd, configuring traffic policies, or implementing zero-trust networking with minimal overhead.

    Also in 5 projects that use this

  • berntpoppSkill

    dependency-cve-sweep

    Use when handling Dependabot PRs, CodeQL/Trivy alerts, or doing a routine dependency/CVE sweep for this repo.

    Also in 12 projects that use this

  • berntpoppSkill

    fleet-standard-adoption

    Use when bringing this repo into compliance with a GeneFoundry fleet standard (tool-naming, response-envelope, container-hardening, versioning, MCP transport, or logging) or closing its tracking issue.

    Also in 12 projects that use this

  • HABUBUSSSkill

    project-guidelines-example

    Also in 16 projects that use this

  • niloykumarbarmanSkill

    agent-sort

    Build an evidence-backed ECC install plan for a specific repo by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes. Use when ECC should be trimmed to what a project actually needs instead of loading the full bundle.

    Also in 13 projects that use this

  • royaluniondesign-sysSkill

    configure-ecc

    Interactive installer for Everything Claude Code — guides users through selecting and installing skills and rules to user-level or project-level directories, verifies paths, and optionally optimizes installed files.

    Also in 11 projects that use this

  • +2 more from berntpopp
  • Other versions192 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 192

    1. affaan-m/ECC★ 246ksame name
    2. github/awesome-copilot★ 41ksame name
    3. langfuse/langfuse★ 37ksame name
    4. nearai/ironclaw★ 13ksame name
    5. joe-bell/cva★ 6.9ksame name
    6. doorkeeper-gem/doorkeeper★ 5.5ksame name
    7. github/squad★ 3.4ksame name
    8. compozy/compozy★ 2.9ksame name
    9. getsentry/sentry-python★ 2.2ksame name
    10. trycompai/comp★ 2.1ksame name

    182 more not listed

    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 repository2 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 167 edited versions we read keep these.

  • 1

    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:

    If no issues: say so explicitly and list what you checked.

    line 61

“Common” is measured: kept by at least 6 in 10 of the 167 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 Review

Review the current change like a security-minded senior. Prefer concrete findings over generic advice.

Scope

Focus on the diff and directly related call paths. Do not audit the whole repo unless asked.

Checklist

Auth & access

  • Every sensitive action checks authentication and authorization
  • IDs from the client are not trusted for ownership (userId in body ≠ proof)
  • Admin/debug routes are gated; no "temporary" open endpoints

Input & data

  • User input is validated at the boundary (type, length, allowlist)
  • SQL/NoSQL/search queries are parameterized — no string concat
  • HTML/Markdown/user content is escaped or sanitized where rendered
  • File uploads: size limits, type allowlist, stored outside web root, randomized names
  • Path joins cannot escape intended directories (../)

Secrets & config

  • No secrets in source, logs, client bundles, or example env files with real values
  • New env vars documented; defaults are safe for production
  • Tokens/passwords not written to analytics or error trackers

Network & server

  • Outbound fetches do not accept raw user URLs without allowlisting (SSRF)
  • CORS is least-privilege; credentials only when required
  • Cookies: HttpOnly, Secure, SameSite where applicable

Dangerous APIs

  • No eval, dangerouslySetInnerHTML, shell exec with unsanitized input
  • Deserialization of untrusted data is avoided or hardened
  • Crypto/auth libraries are standard — no home-rolled JWT/crypto

Output format

Group findings:

SeverityRuleWhereWhy it mattersFix
Critical / High / Medium / Low / Noteshort namefile:line or symbol1 sentenceconcrete change

End with:

  • Blockers — must fix before merge
  • Safe to ship with follow-ups — optional

If no issues: say so explicitly and list what you checked.

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