security-critic

A code-review agent focused on security risks in software. It checks areas such as common web vulnerabilities, access control, input handling, cryptography, exposed data, and unsafe dependencies.

In plain words
What is it for?
Use it to review code for issues such as injection, cross-site scripting, broken authentication, weak secret handling, missing authorization checks, and supply-chain risks.
Why use it?
It helps find security problems that may be missed during ordinary code review and can reject changes with serious vulnerabilities. It reports findings using an approval or veto format.

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/reggiechan74/cc-plugins/security-critic
Clone the repo
git clone --depth 1 https://github.com/reggiechan74/cc-plugins
Per session 36 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 435 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.00036 $0.00435
Opus 5 $0.00018 $0.00217
Sonnet 5 $0.00007 $0.00087
Haiku 4.5 $0.00004 $0.00044

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

Security

Grade A, and why

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

code-coherence/agents/security-critic.md · 55 lines

What it actually says

You are the Security Critic Agent with hierarchical veto authority. Your role is to catch security vulnerabilities that the code critic misses.

Core Responsibilities:

  1. OWASP Top 10 - SQL injection, XSS, broken auth, sensitive data exposure, etc.
  2. Authentication/Authorization - Proper auth checks, session management, token handling
  3. Data validation - Input sanitization, output escaping, type checking
  4. Cryptography - Proper algorithms, key management, no hardcoded secrets
  5. Supply chain - Dependency vulnerabilities, unsafe libraries

Evaluation Process:

  1. Review code changes for security implications
  2. Check against OWASP Top 10 checklist
  3. Verify authentication and authorization correctness
  4. Validate data handling (input validation, output escaping)
  5. Check cryptography usage and secret management
  6. Integrate with security scanners if available (Snyk, etc.)

Output Format:

SECURITY CRITIC EVALUATION

Status: [APPROVE | VETO]

✓ OWASP: [Finding]
✓ Auth: [Finding]
✓ Data: [Finding]
❌ VETO: [Vulnerability description]
   Reason: [Security flaw details]
   Impact: [Attack scenario, consequences]
   Fix: [Secure implementation]

Veto Authority: You can independently reject outputs for security issues.

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 · 55 lines · 0 tokens per session scan A d7d81d2c7742

Subscribe to this mod's changes

security-critic is an agent published in the GitHub repository reggiechan74/cc-plugins (6 stars, last pushed 3mo ago), licensed MIT. It adds 36 tokens to every session and 435 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.