security-reviewer

security-reviewer is an agent for coding agents from mturac/everything-openai-codex. It costs 52 tokens per session (979 once invoked), scanned A, original, MIT.

A code-review agent focused on finding and fixing common security weaknesses in web applications. It checks areas such as user input, login controls, secrets, dependencies, and database queries.

In plain words
What is it for?
Use it after writing security-sensitive code to look for issues such as injection, exposed passwords or keys, unsafe authentication, and other OWASP Top 10 risks.
Why use it?
It helps catch security problems before code reaches production, especially in code that handles accounts, APIs, payments, uploads, or private data.

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/mturac/everything-openai-codex/security-reviewer
Clone the repo
git clone --depth 1 https://github.com/mturac/everything-openai-codex

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/mturac/everything-openai-codex/security-reviewer.svg)](https://agentmods.dev/agents/mturac/everything-openai-codex/security-reviewer)
Your own site
<a href="https://agentmods.dev/agents/mturac/everything-openai-codex/security-reviewer"><img src="https://agentmods.dev/badge/agents/mturac/everything-openai-codex/security-reviewer.svg" alt="Measured on agentmods" 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 979 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.00052 $0.00979
Opus 5 $0.00026 $0.00490
Sonnet 5 $0.00010 $0.00196
Haiku 4.5 $0.00005 $0.00098

Measured 3d ago against content hash acb3fee8ccec, 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 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 3d 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 |
Origin

Copies of this mod

8 near-identical copies found in the catalogue:

.kiro/agents/security-reviewer.md · 110 lines

How it starts

The opening of the file, as written. The whole thing — 110 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?

3. Code Pattern Review

Flag these patterns immediately:

Pattern Severity Fix
Hardcoded secrets CRITICAL Use process.env
Shell command with user input CRITICAL Use safe APIs or execFile
String-concatenated SQL CRITICAL Parameterized queries
innerHTML = userInput HIGH Use textContent or DOMPurify
fetch(userProvidedUrl) HIGH Whitelist allowed domains
Plaintext password comparison CRITICAL Use bcrypt.compare()
No auth check on route CRITICAL Add authentication middleware
Balance check without lock CRITICAL Use FOR UPDATE in transaction
No rate limiting HIGH Add express-rate-limit
Logging passwords/secrets MEDIUM Sanitize log output

Read the full file on GitHub · 110 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. 3d ago First seen · 110 lines · 52 tokens per session scan A acb3fee8ccec

Subscribe to this mod's changes

security-reviewer is an agent published in the GitHub repository mturac/everything-openai-codex (90 stars, last pushed 10d ago), licensed MIT. It adds 52 tokens to every session and 979 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.