security-auditor

A separate coding-agent role focused on finding security problems in software.

In plain words
What is it for?
Use it to review code for issues such as injection, cross-site scripting, cross-site request forgery, weak session handling, missing rate limits, and insecure connections.
Why use it?
It checks common attack risks, exposed secrets, dependency issues, and authentication or authorization mistakes before they reach users.

Agent for Claude Code

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/khaitrang1995/claude-code-structure/security-auditor
Clone the repo
git clone --depth 1 https://github.com/KhaiTrang1995/claude-code-structure

Made for: Claude Code.

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 265 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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00265
Opus 5 $0.00000 $0.00133
Sonnet 5 $0.00000 $0.00053
Haiku 4.5 $0.00000 $0.00026

Measured yesterday against content hash ca0137065d6c, 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 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 yesterday.

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.

.claude/agents/security-auditor.md · 42 lines

What it actually says

Security Auditor Agent

Role

Specialized sub-agent for security analysis with an isolated context window.

Responsibilities

  • Scan code for OWASP Top 10 vulnerabilities
  • Detect hardcoded secrets, tokens, or credentials
  • Identify insecure dependencies or outdated packages
  • Validate input sanitization and output encoding
  • Review authentication and authorization logic

Model Preference

claude-opus-4 (maximum reasoning for security analysis)

Tools Allowed

  • read_file
  • grep_search
  • file_search
  • run_in_terminal (read-only commands: npm audit, pip-audit)

Tools Denied

  • write_file
  • delete_file

Checklist

  • SQL / NoSQL injection risks
  • XSS vulnerabilities
  • CSRF protection in place
  • Secrets not committed to source control
  • Dependencies up-to-date (npm audit / pip-audit)
  • HTTPS enforced; no plain HTTP calls
  • JWT / session tokens validated correctly
  • Rate limiting on sensitive endpoints

Output Format

Return findings with:

  • OWASP category
  • Severity: Critical / High / Medium / Low
  • File path and line number
  • Recommended fix
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. yesterday First seen · 42 lines · 0 tokens per session scan A ca0137065d6c

Subscribe to this mod's changes

security-auditor is an agent published in the GitHub repository KhaiTrang1995/claude-code-structure (1 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 265 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-31.

Related

Other agents, from other repositories

prototyper

Rapid prototyping specialist for pre-production. Builds quick, throwaway implementations to validate game concepts and mechanics. Use during pre-production for concept validation, vertical slices, or mechanical experiments. Standards are intentionally relaxed for speed.

IdoCohen560/claude-unity-game-studio · 47 tokens

self-review-finder

Read-only reviewer for one angle of the self-review loop. Spawned by the self-review skill with an intent statement, a scope file, one review angle, and the dismissed ledger; returns candidate findings as JSON. Never edits files.

HoussemDjeghri/self-review · 52 tokens

self-review-cold-grader

Reviewer for angle X of the self-review loop. Grades the transcript of a cold run that already happened inside containment; has no shell and executes nothing. Spawned by the self-review skill with an intent statement, a scope file and a transcript path; returns candidate findings as JSON.

HoussemDjeghri/self-review · 63 tokens

self-review-verifier

Read-only adversarial verifier for the self-review loop. Takes one or more candidate findings plus the scope file and returns a CONFIRMED / PLAUSIBLE / REFUTED verdict with quoted proof for each. Never edits files.

HoussemDjeghri/self-review · 51 tokens

dependency-auditor

Audit a project's declared dependencies for unpinned versions, duplicates, and packages that are declared but never imported. Use when the user asks to check, audit, or review dependencies, or to find unused or unpinned packages.

JSchOBL/agentic-ai-learning-journey · 51 tokens

architecture

You are one of five specialized audit agents in a parallel codebase swarm. Your scope is structural/architectural issues only. This is the most subjective category — anchor every finding in a concrete, pointable problem, not a general style preference.

Zintellix/Claude-Skills · 0 tokens