agentleFS
Sign inStart free
aprameyakaprameyak/coding-skills/security-review/SKILL.md

security-review

Skill1 starsChanged 41 days agoMITView on GitHub

Audit code for common security vulnerabilities. Use when reviewing auth, input handling, crypto, secrets, or when the user asks for a security review.

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

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 167 edited versions we read keep these.

  • 4

    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:

    Verify authZ on every sensitive operation.

    line 25
  2. Distinctive:

    Check secret handling and logging.

    line 26
  3. Distinctive:

    Prefer concrete exploit paths over speculative fear.

    line 41
  4. Distinctive:

    Do not request production secret values.

    line 42

“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

Focus Areas

  • Injection (SQL, command, template, LDAP)
  • XSS and unsafe HTML sinks
  • AuthN/AuthZ gaps; IDOR; privilege escalation
  • SSRF, path traversal, open redirects
  • Insecure deserialization
  • Secret exposure in code, logs, or client bundles
  • Weak crypto, hardcoded keys, missing TLS verification
  • CSRF on state-changing cookie sessions
  • Unsafe file uploads and content-type trust
  • Dependency risk for known critical CVEs in touched packages

Process

  1. Identify trust boundaries and entrypoints.
  2. Trace untrusted data to sinks.
  3. Verify authZ on every sensitive operation.
  4. Check secret handling and logging.
  5. Report findings with severity and exploit precondition.

Output

Finding: ...
Severity: critical|high|medium|low
Location: file:line
Impact: ...
Fix: ...

Rules

  • Prefer concrete exploit paths over speculative fear.
  • Do not request production secret values.
  • Recommend fixes that match the stack’s idioms.

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