security-review
Skill153 starsChanged 8 months agoMITView on GitHub
Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment/sensitive features. Provides comprehensive security checklist and patterns.
- Reads credentials
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 9 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
- 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
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
ysyecustSkillbrand-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
- +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 repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- rules/agents.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- backend-patternsSkill
- clickhouse-ioSkill
- cloudnative-writing-baselineSkill
- coding-standardsSkill
- eval-harnessSkill
- frontend-patternsSkill
- project-guidelines-exampleSkill
- prompt-patternsSkill
- strategic-compactSkill
- tdd-workflowSkill
- verification-loopSkill
- web-content-extractionSkill
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 40
Before ANY production deployment, confirm ALL of the following:
“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 Skill
Ensures all code follows security best practices and identifies potential vulnerabilities.
When to Activate
- Implementing authentication or authorization
- Handling user input or file uploads
- Creating new API endpoints
- Working with secrets or credentials
- Implementing payment features
- Storing or transmitting sensitive data
- Integrating third-party APIs
Security Checklist Categories
Review each category. See references/vulnerability-patterns.md for WRONG/CORRECT code examples.
- Secrets Management -- No hardcoded secrets; all in env vars;
.env*gitignored - Input Validation -- Schema validation; file upload size/type/extension checks
- SQL Injection -- Parameterized queries only; no string concatenation
- Auth & Authorization -- httpOnly cookies; RBAC; row-level/object-level authorization where needed
- XSS Prevention -- DOMPurify for user HTML; CSP headers configured
- CSRF Protection -- CSRF tokens on state-changing ops; SameSite=Strict cookies
- Rate Limiting -- All endpoints rate-limited; stricter on expensive operations
- Data Exposure -- No secrets in logs; generic error messages to users
- High-Risk Integrations -- Payments, wallets, third-party APIs, and webhooks validated when present
- Dependencies --
npm auditclean; lock files committed; Dependabot enabled
Full checkbox checklist: assets/security-checklist.md
Pre-Deployment Checklist
Before ANY production deployment, confirm ALL of the following:
- No hardcoded secrets, all in env vars
- All user inputs validated
- All queries parameterized
- User content sanitized (XSS)
- CSRF protection enabled
- Proper token handling (httpOnly cookies)
- Authorization role checks in place
- Rate limiting on all endpoints
- HTTPS enforced
- Security headers configured (CSP, X-Frame-Options)
- No sensitive data in error messages or logs
- Dependencies up to date, no vulnerabilities
- CORS properly configured
- File uploads validated (size, type)
References
references/vulnerability-patterns.md-- All WRONG/CORRECT code examples by vulnerability typeassets/security-checklist.md-- Full security review checklist (markdown checkboxes)- OWASP Top 10
- Next.js Security
- Web Security Academy
Security is not optional. One vulnerability can compromise the entire platform. When in doubt, err on the side of caution.
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.