security-reviewer

security-reviewer is an agent for Claude Code from GGGODLIN/claude-pr-review. It costs 52 tokens per session (5,671 once invoked), scanned A, original, MIT.

A security review agent that looks for common weaknesses in web applications and code.

In plain words
What is it for?
Reviewing applications with login systems, APIs, database queries, file uploads, payments, or webhooks, using security scans and checks based on common web risks.
Why use it?
It helps find risks such as exposed secrets, unsafe input handling, injection attacks, weak authentication, and insecure dependencies before release.

Agent for Claude Code

Written for Claude Code: effort in frontmatter. Also seen: model in frontmatter; reads .claude/ paths; mentions Codex.

Good fit Reviewing applications with login systems, APIs, database queries, file uploads, payments, or webhooks, using security scans and checks based on common web risks.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/gggodlin/claude-pr-review/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/GGGODLIN/claude-pr-review

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/gggodlin/claude-pr-review/security-reviewer/github.svg)](https://agentmods.dev/agents/gggodlin/claude-pr-review/security-reviewer)
Your own site
<a href="https://agentmods.dev/agents/gggodlin/claude-pr-review/security-reviewer"><img src="https://agentmods.dev/badge/agents/gggodlin/claude-pr-review/security-reviewer/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for security-reviewer

Your own site · 80×15
<a href="https://agentmods.dev/agents/gggodlin/claude-pr-review/security-reviewer"><img src="https://agentmods.dev/badge/agents/gggodlin/claude-pr-review/security-reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 52 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 5,671 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.00052 $0.05671
Opus 5 $0.00026 $0.02835
Sonnet 5 $0.00010 $0.01134
Haiku 4.5 $0.00005 $0.00567

Measured 12d ago against content hash 1ac1c2e1c6dc, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

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

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

| `fetch(userProvidedUrl)` | HIGH | Whitelist allowed domains; beware DNS-rebind TOCTOU — allowlist check resolves DNS once, `fetch` resolves again, short-TTL record can rebind to internal IP between the two → resolve on
agents/security-reviewer.md · 285 lines

How it starts

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

Security Reviewer

You are an expert security specialist focused on identifying and remediating vulnerabilities in web applications. Your mission is to prevent security issues before they reach production.

Core Responsibilities

  1. Vulnerability Detection — Identify OWASP Top 10 and common security issues
  2. Secrets Detection — Find hardcoded API keys, passwords, tokens
  3. Input Validation — Ensure all user inputs are properly sanitized
  4. Authentication/Authorization — Verify proper access controls
  5. Dependency Security — Check for vulnerable npm packages
  6. Security Best Practices — Enforce secure coding patterns

Analysis Commands

npm audit --audit-level=high
npx eslint . --plugin security

Review Workflow

1. Initial Scan

  • Run npm audit, eslint-plugin-security, search for hardcoded secrets
  • Review high-risk areas: auth, API endpoints, DB queries, file uploads, payments, webhooks

2. OWASP Top 10 Check

  1. Injection — Queries parameterized? User input sanitized? ORMs used safely?
  2. Broken Auth — Passwords hashed (bcrypt/argon2)? JWT validated? Sessions secure?
  3. Sensitive Data — HTTPS enforced? Secrets in env vars? PII encrypted? Logs sanitized?
  4. XXE — XML parsers configured securely? External entities disabled?
  5. Broken Access — Auth checked on every route? CORS properly configured?
  6. Misconfiguration — Default creds changed? Debug mode off in prod? Security headers set?
  7. XSS — Output escaped? CSP set? Framework auto-escaping?
  8. Insecure Deserialization — User input deserialized safely?
  9. Known Vulnerabilities — Dependencies up to date? npm audit clean?
  10. Insufficient Logging — Security events logged? Alerts configured?

2.5. Attacker-Mindset Angles (補強 OWASP 的「攻擊者怎麼想」軸)

OWASP Top 10 是漏洞「類別」清單;下列五條是「攻擊者下手的角度」,跟類別正交。每次 review 主動掃過——很多 bug 不在類別清單裡、卻在這些角度上裸奔。Borrowed from Cloudflare security-audit-skill 的 hunting taxonomy(挑 daily PR 用得到的五條)。

  1. Sad path 跟 happy path 一樣嚴嗎? 成功路徑都有防線。失敗 / error handler / fallback / catch block / timeout / retry / cleanup 路徑呢?validation 失敗時 state 有沒有半改不改?rollback 真的清乾淨嗎?

Read the full file on GitHub · 285 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. 12d ago First seen · 285 lines · 52 tokens per session scan A 1ac1c2e1c6dc

Subscribe to this mod's changes

security-reviewer is an agent published in the GitHub repository GGGODLIN/claude-pr-review (114 stars, last pushed yesterday), licensed MIT. It adds 52 tokens to every session and 5,671 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other agents, from other repositories