Skip to main content
subagent CX Codex

security-reviewer · zebbern — Claude Code subagent: what it does, how to install

security-reviewer audits code changes for reachable exploits and trust boundary violations without editing project files.

MIT ★ 4,719 updated 2026-10-30

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/agents/security-reviewer.md
Open on GitHub

What security-reviewer does

The subagent examines trust boundaries and attack paths across your codebase. It runs on the opus model with maximum effort in plan mode, utilizing Read, Grep, Glob, and Bash to inspect code flow. The agent operates passively and never edits your files.

Verification focuses on untrusted parameters reaching sensitive sinks through authorization checks and state mutations. Findings require verified reachability; otherwise, the review exits with inconclusive or blocked status. Every confirmed issue includes exact path:line references, preconditions, and remediation guidance.

What it helps with

  • trace untrusted input to sensitive application sinks
  • audit authorization logic across trust boundaries
  • confirm exploit reachability before reporting issues
  • locate sibling security flaws across the codebase

Example prompts for the agent

  • Check the file upload endpoint for path traversal risks
  • Review the authentication token handler for trust boundary flaws
  • Audit sensitive sinks in the newly added billing webhook

How to install security-reviewer

Manually: put the files in place

.claude/agents/security-reviewer.md

For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean

Questions about security-reviewer

How do I install security-reviewer in Claude Code?

Add the agent configuration to .claude/agents/security-reviewer.md in your project repository.

What does security-reviewer do?

It traces attacker-controlled inputs to sensitive sinks and reports verified exploit paths.

Does security-reviewer modify files?

No, the subagent performs audit analysis only and never edits source files.

Source text

security-reviewer.md · MIT
---
name: security-reviewer
description: "Use proactively when attacker-controlled input, trust boundaries, authorization decisions, sensitive sinks, secrets, or security-impacting changes require exploitability analysis. Do not use for generic correctness review without a meaningful security boundary."
tools:
  - Read
  - Grep
  - Glob
  - Bash
  - PowerShell
  - LSP
model: opus
permissionMode: plan
effort: max
---

# Mission

Determine whether the assigned code or change creates a credible security failure. Own trust-boundary and exploit-path analysis; do not edit source.

## Method

1. Define assets, trust boundaries, attacker capabilities, entry points, and security invariants.
2. Trace attacker-controlled data and identity through validation, authorization, state changes, and sensitive sinks.
3. Construct candidate attack paths and validate reachability, preconditions, defaults, and operational assumptions.
4. Distinguish root cause, exploit primitive, impact, and defense-in-depth gaps.
5. Search for sibling occurrences and report only confirmed or strongly evidenced findings.

## Constraints

- Do not edit files, exploit external systems, expose secrets, or report a vulnerability without a credible path.
- Separate observed facts, assumptions, and unresolved evidence.
- Suppress generic best-practice advice that does not change exploitability.
- Prefer precise remediation of the violated invariant over broad hardening.

## Output

Begin with:

ROLE: security-reviewer
STATUS: complete|blocked|inconclusive

Then list findings by severity. Each finding must include confidence, `path:line` evidence, attacker preconditions, source-to-sink or authorization path, impact, violated invariant, and remediation direction. Include scope and an evidence-backed no-findings statement when applicable.

## Stop conditions

Return `blocked` when the relevant trust model, deployment assumption, or authorization policy is unavailable. Return `inconclusive` when reachability or attacker control cannot be established from available evidence.

© zebbern · MIT · zebbern/claude-code-guide

Similar subagents

All subagents for Security →

security-reviewer by other authors comes first.

security-reviewer Affaan Mustafa The security-reviewer subagent for Claude Code scans code for SQL injections, hardcoded secrets, unsafe crypto, and OWASP Top 10 issues after work on user input, authentication, or API endpoints. CX Codex ★ 6,739repo stars security-reviewer sangrokjung security-reviewer scans a diff for OWASP Top 10 flaws, hardcoded secrets and shaky dependencies, then ranks what it finds. You get a report with secure code samples. CX Codex ★ 880repo stars security-reviewer shinpr security-reviewer weighs finished code against the security rules your project set for itself and answers with the fixes that cannot be skipped. CX Codex ★ 720repo stars security-reviewer yahor-punko security-reviewer audits changed code for security issues and reports specific fixes. Use it when work touches API routes, file parsers, authentication, or third-party integrations. CX Codex ★ 121repo stars opus-reviewer davepoon The opus-reviewer subagent for Claude Code performs a tier 3 architectural review after initial logic and syntax checks pass. It flags contract issues, null propagation, and task drift without editing code. CX Codex ★ 3,785repo stars auth-security-reviewer patricio0312rev auth-security-reviewer walks through sessions, CSRF, cookies and login flows in your code, lists the holes and suggests fixes with severity. CX Codex +1 357installs code-reviewer official Anthropic The code-reviewer subagent checks code changes for bugs, security issues, and project-rule violations. Use it when a review should focus on findings that matter. CX Codex 31,050installs enterprise-security-reviewer Alysson Franklin enterprise-security-reviewer — a Claude subagent that reviews B2B SaaS projects against SOC 2, GDPR and ISO 27001, checks tenant isolation, and preps the codebase for an audit. ★ 1,013repo stars convex-reviewer convex convex-reviewer walks Convex code through auth, validator, index and reactivity checks. Useful before you ship backend functions. CX Codex +1 44,100installs multi-reviewer-patterns Seth Hobson The multi-reviewer-patterns skill coordinates parallel reviews across code-quality dimensions and merges the results into one report. Use it when a change needs several review angles. CX Codex +1 9,800installs

From the same set86

The whole set →
perf-visibility-toggle perf-visibility-toggle guides the AI to toggle the visible prop on Three.js components rather than conditionally unmounting them, avoiding GPU shader recompilation. CX Codex +1 ★ 4,719repo stars perf-r3f-perf The perf-r3f-perf rule teaches Claude Code about r3f-perf, a performance monitoring library for Three.js scenes in real time. Spot frame drops, memory leaks, and unnecessary matrix recalculations as they happen. CX Codex +1 ★ 4,719repo stars codebase-mapper codebase-mapper maps repository structure, call chains, and data flows before code changes without mutating any files. CX Codex ★ 4,719repo stars solution-architect solution-architect is a subagent for Claude Code, Codex, and Cursor that compares architectural options and recommends one based on constraints. It is used when requirements are set but several designs are viable. CX Codex ★ 4,719repo stars runtime-verifier The runtime-verifier subagent for Claude Code verifies acceptance criteria through real CLI, service, browser, or filesystem boundaries without modifying code. CX Codex ★ 4,719repo stars official-docs-researcher The official-docs-researcher subagent checks official sources when a decision hinges on a current API, release, schema, model, or version-specific behavior. CX Codex ★ 4,719repo stars change-implementer change-implementer — a subagent that carries one pre-approved change through to the end: edits the code, runs it for real, and reports what it observed. CX Codex ★ 4,719repo stars tsl-why-use tsl-why-use — a rule that pushes the coding agent to build custom Three.js materials from TSL nodes rather than patching shaders through onBeforeCompile. CX Codex +1 ★ 4,719repo stars

Project sponsors

Companies that keep this analytics open