security-reviewer
Skill1 starsChanged 58 days agoMITView on GitHub
Use when performing security-focused code reviews, threat modeling, or assessing OWASP Top 10 / LLM security risks. Covers Zero Trust and enterprise security standards.
35 other projects use a version of this.
Adopted by
Most recently taken up by
- AutomatedMarketer/claude-skillstheir own version, first seen Nov 16, 2026
- lamb92009/claude-skillstheir own version, first seen Nov 16, 2026
- GarphenGate/moltline-osstheir own version, first seen Nov 10, 2026
- santiago-migoni/claude-skillstheir own version, first seen Nov 8, 2026
- AxlZero21/Skillstheir own version, first seen Nov 8, 2026
- lsyamsiar/claude-skillstheir own version, first seen Nov 1, 2026
Used with
Projects with it also use api-contract-reviewer, ddd-architect 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.
conectlensSkillapi-contract-reviewer
Review Supabase RPC/PostgREST API contracts for DTO correctness, response consistency, validation quality, and backward-compatibility risk. Use when changing libs/api/*, shared response types, or API-facing behavior.
Also in 4 projects that use this
u9401066Skillddd-architect
Ensure code follows DDD architecture and DAL separation principles. Triggers: DDD, arch, 架構, 新功能, 新模組, new feature, scaffold, 骨架, domain.
Also in 4 projects that use this
JohnJBorenSkilltest-engineer
Testing strategy, test patterns, and coverage optimization for unit, integration, and E2E tests
Also in 3 projects that use this
u9401066Skilltest-generator
Generate comprehensive test suites including static analysis, unit tests, integration tests, E2E tests, and coverage reports. Triggers: TG, test, 測試, 寫測試, coverage, 覆蓋率, pytest, unittest, 驗證.
Also in 3 projects that use this
victoralbinoSkillspec-writer
Activity planning via deep interview. Use when the user asks to plan, specify, or detail any activity. Accepts an existing file or a direct description. Interviews with AskUserQuestion and writes the final spec.
Also in 3 projects that use this
StrayDragonSkillui-ux-pro-max
UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient.
Also in 8 projects that use this
Other versions35 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 35
- Jeffallan/claude-skills★ 12ksame name
- kumaran-is/claude-code-onboarding★ 35same name
- codeApe-7/ai-agent-workflowGroup★ 18same name
- conectlens/lenserfight★ 18same name
- PIXARTSeu/Synapse★ 9same name
- Ecoa-PUC-Rio/GAIDE★ 8same name
- jcarlos78/GAIDE★ 8same name
- itsthatladydev/my-agent-skills★ 6same name
- k1lgor/virtual-company★ 4same name
- ralvarez-ai/ralvaskills★ 4same name
25 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 repository28 other files it gives its agents.
- journal-coachSkill
- github-templatesSkill
- node-ciSkill
- renovateSkill
- create-readmeSkill
- markdown-styleSkill
- mermaid-syntaxSkill
- obsidian-vaultSkill
- ste100Skill
- forge-detectSkill
- forgejo-issueSkill
- forgejo-prSkill
- web-frontendSkill
- docker-pythonSkill
- pyproject-tomlSkill
- python-ciSkill
- python-cliSkill
- python-devcontainerSkill
- python-projectSkill
- architecture-briefSkill
- design-advisorSkill
- saas-anti-pattern-reviewSkill
- saas-transition-chain-reviewSkill
- saas-transition-reviewSkill
- saas-transition-strategySkill
- technical-debt-reviewSkill
- commit-messageSkill
- discord-sendSkill
The file
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 32 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
- Distinctive: line 40
Check for these (see OWASP Top 10):
- Distinctive: line 53
Every request must be authenticated and authorized regardless of network origin.
“Common” is measured: kept by at least 6 in 10 of the 32 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 Reviewer
Prevent production security failures through comprehensive security review.
Your Mission
Review code for security vulnerabilities with focus on OWASP Top 10, Zero Trust principles, and AI/ML security (LLM and ML specific threats).
Step 0: Create Targeted Review Plan
Analyze what you're reviewing:
- Code type?
- Web API -> OWASP Top 10
- AI/LLM integration -> OWASP LLM Top 10
- ML model code -> OWASP ML Security
- Authentication -> Access control, crypto
- Risk level?
- High: Payment, auth, AI models, admin
- Medium: User data, external APIs
- Low: UI components, utilities
- Business constraints?
- Performance critical -> Prioritize performance checks
- Security sensitive -> Deep security review
- Rapid prototype -> Critical security only
Create Review Plan:
Select 3-5 most relevant check categories based on context.
Step 1: OWASP Top 10 Security Review
Check for these (see OWASP Top 10):
- A01 - Broken Access Control: Missing auth, IDOR, privilege escalation. Verify authorization on every endpoint, not just authentication.
- A02 - Cryptographic Failures: Weak hashes (MD5, SHA1), hardcoded secrets, missing TLS. Use scrypt/bcrypt/argon2 for passwords; env vars for secrets.
- A03 - Injection: SQL, NoSQL, command, template injection. Use parameterized queries, ORMs, input sanitization. Never interpolate user input.
Step 1.5: OWASP LLM Top 10 (AI Systems)
- LLM01 - Prompt Injection: Sanitize user input before LLM prompts. Isolate instructions from user content with clear delimiters.
- LLM06 - Information Disclosure: Strip PII/sensitive data from LLM context. Filter outputs before returning to user.
Step 2: Zero Trust Implementation
Every request must be authenticated and authorized regardless of network origin. Validate all inputs, verify service tokens on internal APIs, apply least-privilege access.
Step 3: Reliability
External calls need timeouts, retries with exponential backoff, and circuit breakers. Handle network failures and non-2xx responses explicitly.
Document Creation
After Every Review, CREATE:
Code Review Report - Save to docs/code-review/[date]-[component]-review.md
- Include specific code examples and fixes
- Tag priority levels
- Document security findings
Report Format:
# Code Review: [Component]
**Ready for Production**: [Yes/No]
**Critical Issues**: [count]
## Priority 1 (Must Fix) :no_entry:
- [specific issue with fix]
## Recommended Changes
[code examples]Remember: Goal is enterprise-grade code that is secure, maintainable, and compliant.
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.

