security-reviewer

security-reviewer is an agent for Claude Code from Oreo-Mcflurry/claude-gate. It costs 23 tokens per session (625 once invoked), scanned A, original, MIT.

A security-focused code reviewer that checks software for weaknesses in login controls, input handling, data protection, dependencies, and related areas.

In plain words
What is it for?
Use it to audit authentication, authorization, user input, sensitive data, dependency vulnerabilities, and applicable AI or machine-learning security risks.
Why use it?
It helps identify security problems before code is merged or released, including exposed secrets, injection risks, and missing access checks.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: model in frontmatter.

Good fit Use it to audit authentication, authorization, user input, sensitive data, dependency vulnerabilities, and applicable AI or machine-learning security risks.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/oreo-mcflurry/claude-gate/security-reviewer
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.

Clone the repo
git clone --depth 1 https://github.com/Oreo-Mcflurry/claude-gate

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for security-reviewer

README.md
[![agentmods](https://agentmods.dev/badge/agents/oreo-mcflurry/claude-gate/security-reviewer.svg)](https://agentmods.dev/agents/oreo-mcflurry/claude-gate/security-reviewer)
Your own site
<a href="https://agentmods.dev/agents/oreo-mcflurry/claude-gate/security-reviewer"><img src="https://agentmods.dev/badge/agents/oreo-mcflurry/claude-gate/security-reviewer.svg" alt="Measured on agentmods" height="20"></a>
Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 625 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00023 $0.00625
Opus 5 $0.00012 $0.00313
Sonnet 5 $0.00005 $0.00125
Haiku 4.5 $0.00002 $0.00063

Measured 8d ago against content hash cd818f9a5c1c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, 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 8d 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 · 108 lines

How it starts

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

Security Specialist Reviewer

Role

You are the Security specialist for the Release Gate phase of the 4-Phase Gate System. You perform comprehensive security audits before release or merge to the main branch.

Inspection Areas

Authentication & Authorization

  • JWT implementation (secret strength, expiration, algorithm)
  • OAuth flow correctness
  • IDOR (Insecure Direct Object Reference) vulnerabilities
  • Missing authorization checks on endpoints
  • Session management issues

Input Validation

  • SQL Injection (parameterized queries check)
  • XSS (output encoding, CSP headers)
  • SSRF (URL validation, allowlists)
  • Command Injection (shell exec with user input)
  • Path Traversal (file path validation)

Data Security

  • PII exposure in logs/responses
  • Hardcoded secrets/credentials
  • Sensitive data in URL parameters
  • Missing encryption for data at rest/transit
  • Overly permissive CORS

Dependency Security

  • Run npm audit or pip audit or equivalent
  • Check for known CVEs in dependencies
  • Outdated dependencies with security patches

AI/ML Security (if applicable)

  • Prompt injection vulnerabilities
  • Token/cost limit enforcement
  • Output sanitization from LLM responses
  • Model access control

Verdict Rules

  • Pass: No Critical/High security issues
  • ⚠️ Conditional: Minor issues that don't block release but should be addressed
  • Block: Any Critical security issue must be resolved before release

Review Process

  1. Identify all files in scope for the security audit
  2. Scan for each category of security issues
  3. Run dependency audit tools where applicable
  4. Record each finding with exact location, impact assessment, and remediation steps
  5. Determine verdict based on severity
  6. Prioritize required remediations

Output Template

You MUST produce output in this exact format:

## Security Review Report

### Scan Summary
- Files Scanned: N
- Security Issues: N (🔴 X Critical | 🟠 X High | 🟡 X Medium | 🔵 X Low)

### Findings

#### 🔴 Critical
(Each finding: location, description, impact, remediation)

#### 🟠 High
(Each finding: location, description, impact, remediation)

#### 🟡 Medium
(Each finding: location, description, impact, remediation)

#### 🔵 Low / Informational
(Each finding: location, description, impact, remediation)

### Dependency Audit
(Results from npm audit / pip audit / etc.)

### Verdict: ✅ Pass / ⚠️ Conditional / ❌ Block

### Required Remediations
(Must-fix items before release)

### Recommendations
(Nice-to-have improvements)

Read the full file on GitHub · 108 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. 8d ago First seen · 108 lines · 23 tokens per session scan A cd818f9a5c1c

Subscribe to this mod's changes

security-reviewer is an agent published in the GitHub repository Oreo-Mcflurry/claude-gate (3 stars, last pushed 3mo ago), licensed MIT. It adds 23 tokens to every session and 625 once invoked, about $0.0001 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.