agentleFS
Sign inStart free
JkudjoJkudjo/oh-my-cursor/skills/security-review/SKILL.md

security-review

Skill1 starsChanged 7 months agoMITView on GitHub

Security-focused audit — OWASP Top 10, secrets, auth, injection, supply chain

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 168 edited versions we read keep these.

  • 2

    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 shipping anything that handles auth, user data, or external input

    line 13
  2. Distinctive:

    When adding new API endpoints or third-party integrations

    line 14

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

Dedicated security audit. More thorough than @review's security section.

When to use

  • Before shipping anything that handles auth, user data, or external input
  • When adding new API endpoints or third-party integrations
  • Periodic security audits of sensitive subsystems

What it covers

  • Injection — SQL, command, HTML, template injection
  • Auth — broken authentication, missing authorization, JWT issues
  • Secrets — hardcoded credentials, tokens, keys in code or git history
  • Input validation — unvalidated input reaching dangerous operations
  • Dependencies — known CVEs in package.json / requirements
  • IDOR — direct object references without ownership checks
  • CSRF/XSS — missing protections in web-facing code
  • Data exposure — sensitive fields in logs, API responses, or error messages
  • Supply chain — suspicious packages, loose version pins

Output

Report with findings:

  • Severity: CRITICAL / HIGH / MEDIUM / LOW
  • File:line reference
  • Attack vector description
  • Recommended fix

Verdict: SECURE | ISSUES FOUND (N critical, N high)

Download now (ZIP)

  • Other versions191 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 191

    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. compozy/compozy★ 2.8ksame name
    8. getsentry/sentry-python★ 2.2ksame name
    9. trycompai/comp★ 2ksame name
    10. xu-xiang/everything-claude-code-zh★ 1.9ksame name

    181 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.

  • Used alongsideProjects with it also use dependency-cve-sweep, fleet-standard-adoption 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.
    • 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

    • 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 12 projects that use this

    • ysyecustSkill

      brand-discovery

      Use when a brand needs to discover or articulate its identity through structured multi-session interviews. Covers purpose, positioning, audience, personality, voice, narrative, and founder-brand tension across 8 modules using laddering, 5 Whys, and projective techniques. Produces a resumable session with disk-persisted state and a master brandbook (90_SYNTHESIS.md).

      Also in 5 projects that use this

    • InfopibeSkill

      everything-claude-code

      Also in 11 projects that use this

    • junimnjwSkill

      ralphinho-rfc-pipeline

      RFC-driven multi-agent DAG execution pattern with quality gates, merge queues, and work unit orchestration.

      Also in 10 projects that use this

    • +2 more from berntpopp
  • In this repository22 other files it gives its agents.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

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