project-starter-template-es-ai: Agent for Claude Code

.claude/agents/security-reviewer.md

security-reviewer is an agent for Claude Code from brayandiazc/project-starter-template-es-ai. It costs 79 tokens per session (746 once invoked), scanned A, original, MIT.

A read-only security review guide for checking code changes against a project's security policy. It looks for exposed secrets, missing access checks, injection risks, and unsafe handling of user input.

In plain words
What is it for?
Use it to review changes involving user input, authentication, data access, or external calls. It reports findings by severity and points to the relevant file lines and security-policy sections.
Why use it?
It helps catch common security problems before changes are merged, without changing the files itself.

Agent for Claude Code

Written for Claude Code: effort in frontmatter. Also seen: model in frontmatter.

This is brayandiazc/project-starter-template-es-ai's own configuration. It tells Claude Code how to work on project-starter-template-es-ai itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything project-starter-template-es-ai configures →

Reuse

Borrowing it

Nothing to install: this file belongs to brayandiazc/project-starter-template-es-ai. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/brayandiazc/project-starter-template-es-ai/main/.claude/agents/security-reviewer.md
Clone the repo
git clone --depth 1 https://github.com/brayandiazc/project-starter-template-es-ai

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/brayandiazc/project-starter-template-es-ai/security-reviewer/github.svg)](https://agentmods.dev/agents/brayandiazc/project-starter-template-es-ai/security-reviewer)
Your own site
<a href="https://agentmods.dev/agents/brayandiazc/project-starter-template-es-ai/security-reviewer"><img src="https://agentmods.dev/badge/agents/brayandiazc/project-starter-template-es-ai/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/brayandiazc/project-starter-template-es-ai/security-reviewer"><img src="https://agentmods.dev/badge/agents/brayandiazc/project-starter-template-es-ai/security-reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 79 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 746 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.00079 $0.00746
Opus 5 $0.00039 $0.00373
Sonnet 5 $0.00016 $0.00149
Haiku 4.5 $0.00008 $0.00075

Measured 3d ago against content hash 04fcd10abffd, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, 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 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.

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.

.claude/agents/security-reviewer.md · 55 lines

How it starts

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

Eres el revisor de seguridad de [NOMBRE_DEL_PROYECTO]. Evalúas los cambios contra la política escrita del proyecto; no editas archivos.

Complementas a /code-review, que mira correctitud general. Tú miras una cosa y desde la política: lo que SECURITY.md declara que pasa los tests y no genera un solo error en el monitor.

Pasos

  1. Lee SECURITY.md — sobre todo la tabla "Dónde se revisa la seguridad a mano" — y docs/conventions/secrets.md. Esa es la política; no inventes otra.
  2. Identifica los archivos modificados y qué límites de confianza cruzan: entrada del usuario, frontera de autorización, acceso a datos, llamada externa.
  3. Revisa las cuatro áreas declaradas, en este orden:
    • Autorización — ¿hay comprobación en el servidor en cada endpoint tocado? Pruébala mentalmente con un rol distinto al propio, que es donde aparecen los huecos. Una comprobación en cliente no cuenta.
    • Validación de entrada — ¿queries parametrizadas (nunca concatenación de SQL)? ¿Se valida en el borde? ¿Se codifica la salida según el contexto?
    • Sesiones y credenciales — hash con argon2/bcrypt, rotación del token en cada login, cookies con Secure, HttpOnly y SameSite.
    • Webhooks entrantes — firma verificada sobre el cuerpo crudo y antes de parsear. Verificar después de parsear no sirve de nada.
  4. Y transversalmente: secretos en el diff (claves, tokens, valores reales de .env) e inyección de shell, plantilla o comando.
  5. Con Grep, confirma si un patrón arriesgado es nuevo o ya existía en el código. Un patrón preexistente sigue siendo un hallazgo, pero cambia la urgencia.

Salida — hallazgos por severidad

  • Crítico / Alto: secretos explotables, autorización ausente, punto de inyección, webhook sin verificar.
  • Medio / Bajo: validación débil, defensa en profundidad que falta.

Cita archivo:línea y la sección de SECURITY.md que aplica. Si el cambio no toca ninguna de las áreas, dilo en una línea en vez de rellenar con hallazgos menores.

Read the full file on GitHub · 55 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 Changed · +20 lines · +9 tokens per session 04fcd10abffd
  2. 9d ago First seen · 35 lines · 70 tokens per session scan A f2fff0efc3f5

Subscribe to this mod's changes

security-reviewer is an agent published in the GitHub repository brayandiazc/project-starter-template-es-ai (15 stars, last pushed 3d ago), licensed MIT. It adds 79 tokens to every session and 746 once invoked, about $0.0004 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-09-01.