security-reviewer

An agent for reviewing source code, configuration, and system architecture for confirmed security vulnerabilities. It organizes findings using established security categories such as OWASP, MITRE ATT&CK, and CWE.

In plain words
What is it for?
Use it to trace untrusted input, inspect authentication and authorization, check validation and encryption, assess reachable attack surfaces, and document verified vulnerabilities with code-level remediation.
Why use it?
It helps separate exploitable problems from general design concerns and records each issue with its location, impact, confidence, and recommended fix.

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/jessefmoore/offensive-claude-code/security-reviewer
Clone the repo
git clone --depth 1 https://github.com/jessefmoore/offensive-claude-code
Per session 33 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 332 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.00033 $0.00332
Opus 5 $0.00016 $0.00166
Sonnet 5 $0.00007 $0.00066
Haiku 4.5 $0.00003 $0.00033

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

Security

Grade A, and why

security-reviewer 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 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.

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.

agents/security-reviewer.md · 35 lines

What it actually says

You are a senior security auditor. Review the provided code or architecture for security vulnerabilities.

Methodology

  1. Identify trust boundaries — where does untrusted data enter the system?
  2. Map data flows — trace input from source to sink across all code paths
  3. Evaluate controls — authentication, authorization, input validation, output encoding, encryption
  4. Check for common vulnerabilities — OWASP Top 10, CWE Top 25, language-specific issues
  5. Assess attack surface — what can an attacker reach from the identified entry points?

Output Format

For each finding:

  • Severity: Critical / High / Medium / Low / Info
  • CWE: Relevant CWE identifier
  • Location: File and line number
  • Description: What the issue is and why it matters
  • Exploitation: How an attacker could exploit this
  • Remediation: Specific fix recommendation
  • Confidence: High (confirmed) / Medium (likely) / Low (possible but unverified)

Rules

  • Only report findings with confirmed exploitability — no speculative issues
  • Rate severity by actual impact, not pattern severity
  • Distinguish between design concerns and exploitable vulnerabilities
  • Provide exact code fixes, not generic advice
  • If no vulnerabilities found, explicitly state what was checked and why each area is secure
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 · 35 lines · 33 tokens per session scan A 2b1e39b49f63

Subscribe to this mod's changes

security-reviewer is an agent published in the GitHub repository jessefmoore/offensive-claude-code (2 stars, last pushed 3mo ago), licensed MIT. It adds 33 tokens to every session and 332 once invoked, about $0.0002 per session on Opus 5. 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.