What is security-audit?

A command for checking a codebase for security weaknesses, including exposed credentials, unsafe input handling, injection risks, and authentication or permission problems.

Use it to scan source files and configuration for secrets, unsafe database or shell commands, path traversal risks, and authentication-related code.

It provides a systematic search for common security issues that may otherwise be missed during ordinary development.

security-audit — Command by cassler

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add commands/cassler/awesome-claude-code-setup/security-audit

Clone the repo

git clone --depth 1 https://github.com/cassler/awesome-claude-code-setup

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 781 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00000	$0.00781
Opus 5	$0.00000	$0.00391
Sonnet 5	$0.00000	$0.00156
Haiku 4.5	$0.00000	$0.00078

Measured 3d ago against content hash c91e4f0859f1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

security-audit scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

commands/security-audit.md · 124 lines

How it starts

The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Security Audit

Please perform a comprehensive security audit of this codebase:

1. Secrets and Credentials Scan

Search for exposed sensitive information:

# Common patterns for secrets
chs find-code "password\s*=\s*['\"]|api_key\s*=\s*['\"]|secret\s*=\s*['\"]"
chs find-code "token\s*=\s*['\"]|private.*key\s*=|aws_.*=\s*['\"]"

# Environment files
chs find-file "\.env*" 
# Check if .env files are in .gitignore!

# Common secret file names
chs find-file "*secret*\|*credential*\|*private*"

2. Injection Vulnerabilities

SQL Injection

# String concatenation in queries
chs find-code "query.*\+.*\|\".*SELECT.*\+\|\".*INSERT.*\+\|\".*UPDATE.*\+"

# Direct variable interpolation
chs find-code "query.*\$\{.*\}|query.*\${.*}"

Command Injection

# Dangerous functions
chs find-code "exec\(|spawn\(|system\(|eval\("

# Shell command building
chs find-code "shell.*\+\|cmd.*\+\|exec.*\$"

Path Traversal

# Path manipulation
chs find-code "\.\./\|\.\.\\\\|\.\./\.\."
chs find-code "path\.join.*req\.|path\.join.*user"

3. Authentication & Authorization

Find Auth Code

chs find-code "auth\|login\|session\|jwt\|token"
chs find-file "*auth*\|*login*\|*session*"

Check for Issues

Hardcoded credentials
Weak password requirements
Missing authorization checks
Session fixation risks
Insecure token storage

4. Data Validation & Sanitization

# Find user input handling
chs find-code "req\.body\|req\.query\|req\.params"

# Check for validation
chs find-code "validate\|sanitize\|escape"

# Dangerous operations without validation
chs find-code "innerHTML\|dangerouslySetInnerHTML"

5. Dependencies Security

# Run security audits
ch ts audit  # For npm projects

# Check for known vulnerable packages
chs find-code "require\(|import.*from" | grep -E "(lodash|moment|axios|express)" 
# Then check versions against known vulnerabilities

6. HTTPS & Security Headers

# Check for HTTP usage
chs find-code "http://|createServer\(|\.listen\("

# Security headers
chs find-code "helmet\|cors\|csp\|x-frame-options"

Read the full file on GitHub · 124 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

3d ago First seen · 124 lines · 0 tokens per session scan A c91e4f0859f1

Subscribe to this mod's changes

security-audit is a command published in the GitHub repository cassler/awesome-claude-code-setup (267 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 781 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.