security-review
Skill0 starsChanged 5 months agoMITView on GitHub
Run a read-only security audit of sensitive code (auth, data isolation, secret handling, payments, input validation) before merging or deploying. Ships with a reviewer-agent definition. Block on critical/high findings.
192 other projects use a version of this.
Adopted by
Most recently taken up by
- AOSSIE-Org/Resonate-Websitetheir own version, first seen Nov 9, 2026
- dimastriann/odoo-erp-mcptheir own version, first seen Nov 8, 2026
- ksprashu/agent-skill-forgetheir own version, first seen Nov 8, 2026
- enes-alatas/spooltheir own version, first seen Nov 8, 2026
- sgaabdu4/appwrite-backendtheir own version, first seen Nov 8, 2026
- AndersonAndrad/skillstheir own version, first seen Nov 8, 2026
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.
xfstudioSkilllinkerd-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
berntpoppSkilldependency-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
berntpoppSkillfleet-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
HABUBUSSSkillproject-guidelines-example
Also in 16 projects that use this
niloykumarbarmanSkillagent-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-sysSkillconfigure-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
- affaan-m/ECC★ 246ksame name
- github/awesome-copilot★ 41ksame name
- langfuse/langfuse★ 37ksame name
- nearai/ironclaw★ 13ksame name
- joe-bell/cva★ 6.9ksame name
- doorkeeper-gem/doorkeeper★ 5.5ksame name
- github/squad★ 3.4ksame name
- compozy/compozy★ 2.9ksame name
- getsentry/sentry-python★ 2.2ksame name
- 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 repository7 other files it gives its agents.
- ai-proxy-guardSkill
- consent-complianceSkill
- context-checkpointSkill
- monorepo-bootstrapSkill
- review-gateSkill
- rls-securitySkill
- test-and-fixSkill
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
- Distinctive: line 28
Read-only (no edits) = bounded cost.
“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.
Files
security-review
A bounded, read-only audit you run before shipping anything sensitive. Pair it with the
security-reviewer.md agent definition in this folder (pin it to a frontier model).
What it audits
- Data isolation — per-user/tenant rows are protected (e.g. row-level security); a user cannot read or write another user's data. Confirm an isolation test exists and passes.
- Secret handling — no API keys, service keys, or tokens in client bundles, logs, or git.
- Auth — sessions expire; no privilege escalation; OAuth/MFA configured where claimed.
- Payments (if any) — entitlement is verified server-side; webhooks verified; no way to unlock paid features without paying.
- LLM endpoints (if any) — keys server-side; inputs validated; prompt-injection considered for any user free-text passed to a model.
- Input validation & headers — schema validation on inputs; security headers (CSP, HSTS).
Output format
For each finding: Severity (CRITICAL|HIGH|MEDIUM|LOW) | file:line | issue | concrete fix.
End with VERDICT: PASS (no critical/high open) or VERDICT: BLOCK (list blockers).
Block on any CRITICAL or HIGH.
Token tactics
Read-only (no edits) = bounded cost. Run once per convergence/PR, not per commit. Review only the diff/paths given, never crawl the whole repo.
Bundled agent: security-reviewer
Copy the following into your agent's sub-agent folder (e.g. .claude/agents/security-reviewer.md)
and pin it to a frontier model:
---
name: security-reviewer
description: Read-only security audit of critical code before merge/deploy.
model: <frontier-model>
tools: [Read, Bash]
---
You are a senior application security engineer. You audit; you do not edit. Be specific and cite
file:line. Audit: data isolation, secret handling, auth, payments, LLM endpoints, input
validation, and security headers (see the security-review skill). For each finding output
`Severity | file:line | issue | fix`. End with `VERDICT: PASS` or `VERDICT: BLOCK`. Block on any
CRITICAL or HIGH. Review only the paths given; do not crawl the repo.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
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.

