security-audit · centminmod — Claude Code command: audit and install
The security-audit command scans a codebase for vulnerabilities and unsafe patterns across a project or a specific module.
MIT ★ 2,744 updated 2026-10-08
.claude/commands/security-audit.mdWhat security-audit does
The command checks code for common security issues, including weak password handling, access-control gaps, SQL injection, XSS, exposed secrets, and vulnerable dependencies. It draws on OWASP guidance and covers frontend, backend, database, and infrastructure code.
Its report groups findings by severity and gives each issue a location, an explanation of potential impact, and a remediation suggestion. It also provides general recommendations. The prompt asks for file locations and line numbers; findings still need contextual review to avoid false positives.
What it helps with
- find SQL injection risks in a codebase
- review authentication and permission checks
- locate hardcoded secrets and API keys
- check file-upload handling for security risks
- organize findings by severity and suggested fixes
Example prompts for the agent
/security-auditAudit this project for security issues and write a report with remediation steps./security-auditReview the authentication module for problems with password handling and access control./security-auditLook for SQL injection and unsafe file-upload handling.
How to install security-audit
Manually: put the files in place
.claude/commands/security-audit.mdCall it with /security-audit. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/security-audit.mdCall it with /prompts:security-audit. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/security-audit.prompt.mdManually: put the files in place
.gemini/commands/security-audit.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about security-audit
How do I install security-audit in Claude Code?
Place the command file at .claude/commands/security-audit.md.
What does security-audit do?
It scans code for vulnerabilities and unsafe patterns, then reports their severity, location, impact, and possible fixes.
Which parts of a project does security-audit review?
It checks frontend, backend, database, and infrastructure code. The checklist includes authentication, input handling, API security, and data protection.
Source text
security-audit.md · MIT
# Security Audit Perform a comprehensive security audit of the codebase to identify potential vulnerabilities, insecure patterns, and security best practice violations. ## Usage Examples ### Basic Usage "Run a security audit on this project" "Check for security vulnerabilities in the authentication module" "Scan the API endpoints for security issues" ### Specific Audits "Check for SQL injection vulnerabilities" "Audit the file upload functionality for security risks" "Review authentication and authorization implementation" "Check for hardcoded secrets and API keys" ## Instructions for Claude When performing a security audit: 1. **Systematic Scanning**: Examine the codebase systematically for common vulnerability patterns 2. **Use OWASP Guidelines**: Reference OWASP Top 10 and other security standards 3. **Check Multiple Layers**: Review frontend, backend, database, and infrastructure code 4. **Prioritize Findings**: Categorize issues by severity (Critical, High, Medium, Low) 5. **Provide Remediation**: Include specific fixes for each identified issue ### Security Checklist #### Authentication & Authorization - Password storage and hashing methods - Session management security - JWT implementation and validation - Access control and permission checks - Multi-factor authentication support #### Input Validation & Sanitization - SQL injection prevention - XSS (Cross-Site Scripting) protection - Command injection safeguards - Path traversal prevention - File upload validation #### Data Protection - Encryption in transit (HTTPS/TLS) - Encryption at rest - Sensitive data exposure - API key and secret management - PII handling compliance #### Common Vulnerabilities - CSRF protection - Clickjacking prevention - Security headers configuration - Dependency vulnerabilities - Insecure direct object references #### API Security - Rate limiting implementation - API authentication methods - Input validation on endpoints - Error message information leakage - CORS configuration ### Output Format Provide a structured security report with: ```markdown ## Security Audit Report ### Summary - Total issues found: X - Critical: X, High: X, Medium: X, Low: X ### Critical Issues #### 1. [Issue Name] - **Location**: file.js:line - **Description**: Detailed explanation - **Impact**: Potential consequences - **Remediation**: Specific fix with code example ### High Priority Issues [Similar format] ### Medium Priority Issues [Similar format] ### Low Priority Issues [Similar format] ### Recommendations - General security improvements - Best practices to implement - Tools and libraries to consider ``` Remember to: - Be specific about file locations and line numbers - Provide code examples for fixes - Explain the security impact clearly - Avoid false positives by understanding the context
© centminmod · MIT · centminmod/my-claude-code-setup
Similar slash commands
All slash commands for Security →security-audit by other authors comes first.