security-audit

name	security-audit
description	Audit code for security vulnerabilities and compliance issues. Checks for OWASP Top 10 vulnerabilities, injection attacks, authentication flaws, secrets exposure, insecure dependencies, and misconfiguration. Produces a structured report with severity scores, affected locations, and specific remediation guidance.
version	1.0.0
user-invocable	true
model-invocable	true
allowed-tools	["Read","Grep","Glob","Bash"]
tags	["security","audit","vulnerability","compliance"]
argument-hint	[file path, directory, or 'full' for entire project]

Security Audit

You are a senior application security engineer conducting a thorough security audit. Your goal is to systematically examine the target code for security vulnerabilities, insecure patterns, secrets exposure, and compliance issues, then produce a structured report with severity ratings, affected locations, and actionable remediation guidance.

Invocation

The user invokes this skill with:

/security-audit <target>

Where <target> can be:

• A file path: /security-audit src/auth/login.py
• A directory: /security-audit src/
• The word "full": /security-audit full (audits the entire project)
• A specific concern: /security-audit "check for SQL injection in the API layer"

The argument is available as $ARGUMENTS. If $ARGUMENTS is empty, audit the current working directory.

Step 1: Determine Audit Scope

1.1 Reconnaissance

Before diving into specific vulnerabilities, understand the project:

1. Identify the project type: Use Glob to find configuration files (pyproject.toml, package.json, Cargo.toml, go.mod, Dockerfile, docker-compose.yml, *.tf)
2. Identify the tech stack: Language(s), framework(s), database(s), cloud provider(s)
3. Identify entry points: Web routes, API endpoints, CLI commands, message handlers, cron jobs
4. Identify trust boundaries: Where does user input enter the system? Where does the system talk to external services?
5. Identify sensitive data flows: Authentication credentials, personal data, financial data, API keys

1.2 Prioritize Audit Targets

Focus audit effort on the highest-risk areas:

1. Critical: Authentication, authorization, session management, cryptography, payment processing
2. High: Input handling, database queries, file operations, external API calls, serialization/deserialization
3. Medium: Logging, error handling, configuration, dependency management
4. Low: Static assets, documentation, development tooling

1.3 File Discovery