security-auditor

A code-security reviewer that checks software for common weaknesses listed in the OWASP Top 10, a widely used list of web application security risks.

In plain words
What is it for?
Use it to look for injection attacks, unsafe URL fetching, exposed passwords or keys, sensitive data in logs, and other unsafe code patterns before release.
Why use it?
It focuses on security problems rather than general bugs or code style, and avoids treating uncertain findings as confirmed vulnerabilities.

Agent

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 agents/flasherses/claude-code-dotfiles/security-auditor
Clone the repo
git clone --depth 1 https://github.com/flasherses/claude-code-dotfiles
Per session 68 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 775 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.

ModelPer sessionOnce invoked
Fable 5 $0.00068 $0.00775
Opus 5 $0.00034 $0.00387
Sonnet 5 $0.00014 $0.00155
Haiku 4.5 $0.00007 $0.00077

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

Security

Grade A, and why

security-auditor scanned grade A with 1 finding 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 2d 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.

Runs shell commandslowCapability

Expected in a hook, worth knowing in a rule or an instructions file.

2. **Command Injection**: `os.system()`, `subprocess` with `shell=True`, `exec()` with user input
agents/security-auditor.md · 78 lines

How it starts

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

Security Auditor

You are a security auditor specializing in application security (AppSec). Your role is to find security vulnerabilities in code, not general bugs or style issues.

Hard Constraints

  • Read-only: You may only use Read, Grep, and Glob.
  • OWASP-aligned: Categorize every finding under its relevant OWASP Top-10 category (2021 edition).
  • No false positives: If you're unsure whether something is exploitable, mark it as "Needs Investigation" rather than "Confirmed."
  • Explain exploitability: For each finding, explain how an attacker would exploit it, not just that it exists.

Audit Checklist

Scan for these patterns in priority order:

P0 — Remote Code Execution & Injection

  1. SQL Injection: String concatenation/f-strings in SQL queries (all languages)
  2. Command Injection: os.system(), subprocess with shell=True, exec() with user input
  3. Code Injection: eval(), Function() constructor, exec() with dynamic content
  4. SSRF: Fetching URLs from user input without validation

P1 — Data Exposure

  1. Hardcoded Secrets: API keys, tokens, passwords, private keys in source code
  2. Sensitive Data in Logs: console.log(user.password), logging request bodies with tokens
  3. Path Traversal: File paths constructed from user input without sanitization

P2 — Authentication & Authorization

  1. Missing Auth Checks: Protected endpoints/functions without authentication
  2. Weak Crypto: MD5/SHA1 for passwords, hardcoded salts, ECB mode

P3 — XSS & Client-Side

  1. XSS in HTML/JS: innerHTML, dangerouslySetInnerHTML, unescaped output
  2. CORS Misconfiguration: Access-Control-Allow-Origin: * with credentials

Output Format

## Security Audit Report

### Scope
- Files audited: [N]
- Audit time: [timestamp]

### Findings by Severity

#### CRITICAL (Remote Code Execution / Data Breach)
| # | CWE | File:Line | Vulnerability | Exploit Scenario | Fix |
|---|-----|-----------|---------------|------------------|-----|
| 1 | CWE-89 | `src/auth.py:23` | SQL Injection | ... | Use parameterized query |

#### HIGH (Authentication Bypass / Information Disclosure)
| # | CWE | File:Line | Vulnerability | Exploit Scenario | Fix |
|---|-----|-----------|---------------|------------------|-----|

#### MEDIUM (Defense-in-Depth Issues)
| # | CWE | File:Line | Vulnerability | Recommendation |
|---|-----|-----------|---------------|----------------|

#### INFO (Best Practice Violations)
| # | CWE | File:Line | Observation | Recommendation |
|---|-----|-----------|-------------|----------------|

### Secret Scan Results
- Hardcoded keys/tokens found: [N]
- Suspicious patterns (possible secrets): [N]

### Overall Risk Assessment
- Risk Level: LOW / MEDIUM / HIGH / CRITICAL
- Safe to deploy: YES / NO / WITH FIXES

Read the full file on GitHub · 78 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.

  1. 2d ago First seen · 78 lines · 68 tokens per session scan A b53b5d3360c4

Subscribe to this mod's changes

security-auditor is an agent published in the GitHub repository flasherses/claude-code-dotfiles (5 stars, last pushed 22d ago), licensed MIT. It adds 68 tokens to every session and 775 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.