security-review-audit
Full codebase security audit with OWASP Top 10 guidance, language-specific patterns, checklists, and fix examples. Use for comprehensive audits split by module/area.
Best use case
security-review-audit is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Full codebase security audit with OWASP Top 10 guidance, language-specific patterns, checklists, and fix examples. Use for comprehensive audits split by module/area.
Teams using security-review-audit should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/security-review-audit/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How security-review-audit Compares
| Feature / Agent | security-review-audit | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Full codebase security audit with OWASP Top 10 guidance, language-specific patterns, checklists, and fix examples. Use for comprehensive audits split by module/area.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# Security Code Review Guide ## Overview Perform thorough security reviews of code to identify vulnerabilities, misconfigurations, and security anti-patterns. This skill helps you think like an attacker while providing actionable fixes. --- # Process ## Phase 1: Reconnaissance Before diving into code, understand the attack surface: ### 1.1 Identify Entry Points - HTTP endpoints (routes, controllers, handlers) - API endpoints (REST, GraphQL, gRPC) - WebSocket handlers - File upload handlers - Authentication endpoints - Admin/privileged endpoints ### 1.2 Identify Data Flows - User input sources (forms, query params, headers, cookies) - Database queries and ORM usage - External API calls - File system operations - Command execution - Serialization/deserialization ### 1.3 Identify Trust Boundaries - Authentication checks - Authorization/permission checks - Input validation layers - Output encoding layers --- ## Phase 2: Vulnerability Hunting Systematically check for each vulnerability class: ### 2.1 Injection Vulnerabilities **SQL Injection** - Look for string concatenation in queries - Check ORM usage for raw queries - Verify parameterized queries are used - Check stored procedures for dynamic SQL **Command Injection** - Find all `exec`, `system`, `popen`, `subprocess` calls - Check for user input in command arguments - Verify proper escaping or allowlisting **XSS (Cross-Site Scripting)** - Find all places user input is rendered in HTML - Check for proper output encoding - Look for `innerHTML`, `dangerouslySetInnerHTML`, `v-html` - Check CSP headers **Template Injection** - Find template rendering with user input - Check for SSTI in Jinja2, Twig, ERB, etc. ### 2.2 Authentication & Session **Authentication Flaws** - Password hashing (bcrypt/argon2 vs MD5/SHA1) - Timing-safe comparison for secrets - Account enumeration via error messages - Brute force protection - Password reset flow security **Session Management** - Session token entropy - Secure cookie flags (HttpOnly, Secure, SameSite) - Session fixation protection - Session timeout/invalidation ### 2.3 Authorization **Broken Access Control** - IDOR (Insecure Direct Object References) - Missing function-level access control - Privilege escalation paths - JWT validation issues ### 2.4 Cryptography **Crypto Weaknesses** - Hardcoded secrets/keys - Weak algorithms (MD5, SHA1, DES, RC4) - ECB mode usage - Missing or weak random number generation - Certificate validation disabled ### 2.5 Data Exposure **Sensitive Data** - Secrets in logs - PII in error messages - Sensitive data in URLs - Missing encryption at rest - Verbose error messages in production --- ## Phase 3: Reporting For each finding, document: 1. **Vulnerability Type**: CWE ID and name 2. **Severity**: Critical/High/Medium/Low 3. **Location**: File, line number, function 4. **Description**: What the vulnerability is 5. **Impact**: What an attacker could do 6. **Proof of Concept**: How to exploit (if safe) 7. **Remediation**: Specific fix with code example --- ## Phase 4: Fix Verification After fixes are applied: - Verify the fix addresses the root cause - Check for regression in related code - Ensure fix doesn't introduce new issues - Add tests to prevent regression --- # Reference Files Load these as needed during review: - [OWASP Top 10](./reference/owasp_top_10.md) - Most critical web vulnerabilities - [Language Patterns](./reference/language_patterns.md) - Language-specific vulnerability patterns - [Secure Coding Checklist](./reference/checklist.md) - Quick reference checklist - [Common Fixes](./reference/common_fixes.md) - Code examples for common fixes --- # Quick Reference: OWASP Top 10 (2021) | # | Vulnerability | What to Look For | |---|--------------|------------------| | A01 | Broken Access Control | Missing auth checks, IDOR, privilege escalation | | A02 | Cryptographic Failures | Weak hashing, hardcoded secrets, missing encryption | | A03 | Injection | SQL, command, XSS, template injection | | A04 | Insecure Design | Missing threat modeling, insecure patterns | | A05 | Security Misconfiguration | Default creds, verbose errors, missing headers | | A06 | Vulnerable Components | Outdated dependencies with known CVEs | | A07 | Auth Failures | Weak passwords, missing MFA, session issues | | A08 | Data Integrity Failures | Insecure deserialization, missing integrity checks | | A09 | Logging Failures | Missing audit logs, sensitive data in logs | | A10 | SSRF | Unvalidated URLs, internal network access |
Related Skills
telecom-security
Assess telecommunications infrastructure security including VoIP/SIP, SS7/Diameter, cellular networks, SMS-based authentication, and telephony-integrated applications. Identifies vulnerabilities in phone-based verification, call routing, and telecom protocol implementations. Use when auditing SMS 2FA, VoIP systems, IVR applications, or any telephony-dependent security controls.
technical-review
No description provided.
tauri-security-rules
Security-related rules for Tauri application development.
system-reality-auditor
Performs a triple-point audit to synchronize codebase, database schema, and project documentation states. Use this skill to align the PRD, Gap Analysis, and Execution Plan with the actual system reality.
sqlserver-security
Audits and hardens SQL Server security including login management, permission reviews, TDE encryption, SQL Server Audit configuration, and surface area reduction. Use when performing security reviews, setting up new instances, responding to security incidents, or preparing for compliance audits.
spring-security
Spring Security 6 patterns for authentication, authorization, and OAuth2
solidity-security
Master smart contract security best practices to prevent common vulnerabilities and implement secure Solidity patterns. Use when writing smart contracts, auditing existing contracts, or implementin...
software-security-appsec
Modern application security patterns aligned with OWASP Top 10 (2021) and OWASP Top 10:2025 Release Candidate, OWASP API Security Top 10 (2023), NIST SSDF, zero trust, supply chain security, authentication, authorization, input validation, and cryptography.
slack-auth-security
OAuth flows, token management, and security best practices for Slack apps. Use when implementing app distribution, multi-workspace installations, token storage and rotation, managing scopes and permissions, or securing production Slack applications.
securitytrails-automation
Automate Securitytrails tasks via Rube MCP (Composio). Always search tools first for current schemas.
security
Use this skill when designing or reviewing systems where security is a concern - authentication, authorization, data protection, input handling, or any system processing untrusted input. Applies adversarial thinking to specifications, designs, and implementations.
security-workflow
Use when creating backlog tasks from security findings, integrating security scans into workflow states, or managing security remediation tracking. Invoked for security workflow integration and task automation.