security-review
Skill2 starsChanged 9 months agoMITView on GitHub
Security audit checklist for code changes. Run before committing to catch vulnerabilities.
- 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 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
- 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
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 repository27 other files it gives its agents.
- Agent BrowserSkill
- agent-governanceSkill
- agent-system-learning-loopSkill
- agent-system-live-quality-opsSkill
- agent-system-memory-proactivity-opsSkill
- agent-system-output-hygiene-opsSkill
- agent-system-stability-opsSkill
- auto-updaterSkill
- deep-researchSkill
- domaindetailsSkill
- hnSkill
- humanizerSkill
- memory-hygieneSkill
- model-usageSkill
- nano-pdfSkill
- news-aggregator-skillSkill
- orchestrator-loopSkill
- prompt-guardSkill
- self-improvementSkill
- structured-brainstormingSkill
- subagent-executionSkill
- summarizeSkill
- systematic-debuggingSkill
- tavilySkill
- tdd-workflowSkill
- topic-monitorSkill
- verification-gateSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 167 edited versions we read keep these.
3
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 13
Run against all modified files before commit:
- Distinctive: line 66
CRITICAL: Must fix before commit (secrets exposure, SQL injection)
- Distinctive: line 67
HIGH: Should fix before merge (missing auth, XSS)
“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
Automated security review checklist for code changes. Covers OWASP Top 10, dependency vulnerabilities, secret exposure, and injection vectors.
Checklist
Run against all modified files before commit:
1. Input Validation
- All user inputs validated and sanitized
- SQL queries use parameterized statements (no string concatenation)
- Shell commands use safe argument passing (no interpolation)
- Path traversal prevented (no
../in user paths) - File uploads validated (type, size, name)
2. Authentication & Authorization
- Auth checks on all protected endpoints
- Session tokens are cryptographically random
- Password hashing uses bcrypt/argon2 (not MD5/SHA1)
- API keys not hardcoded in source
3. Secrets Management
- No secrets in source code (API keys, passwords, tokens)
.envfiles in.gitignore- Environment variables used for configuration
- No secrets in log output or error messages
4. Dependency Security
- Dependency audit passes
- No known CVEs in dependencies
- Lock files committed and up to date
- Minimal dependency footprint
5. Error Handling
- Error messages don't leak internal details
- Stack traces not exposed to users
- Graceful degradation on failure
- Timeouts configured for external calls
6. Data Protection
- Sensitive data encrypted at rest
- HTTPS enforced for all external communication
- PII handling follows minimum exposure principle
- Logs don't contain sensitive user data
7. Injection Prevention
- XSS: Output encoding applied
- CSRF: Tokens used for state-changing operations
- Command injection: Safe argument passing, no shell interpolation with user data
- SSRF: External URL validation
8. Configuration
- Debug mode disabled in production
- CORS configured restrictively
- Security headers set (CSP, HSTS, X-Frame-Options)
- Rate limiting on sensitive endpoints
Severity Levels
- CRITICAL: Must fix before commit (secrets exposure, SQL injection)
- HIGH: Should fix before merge (missing auth, XSS)
- MEDIUM: Fix in same sprint (missing rate limiting, verbose errors)
- LOW: Track and fix later (minor header issues)
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.