What is security-reviewer?

A security review agent for application code and deployment changes. It looks for common web vulnerabilities, exposed secrets, unsafe containers, dependency problems, access-control errors, and data leaks between customers.

Use it after code changes or during pull-request reviews, especially when authentication, encryption, secrets, role permissions, containers, dependencies, or tenant isolation are involved.

Security issues can be introduced during ordinary code changes and may be easy to miss in a normal review. This focuses the review on high-risk files, known attack patterns, credentials, and deployment settings.

How stoa-platform/stoa configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to stoa-platform/stoa. 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/stoa-platform/stoa/main/.claude/agents/security-reviewer.md

Clone the repo

git clone --depth 1 https://github.com/stoa-platform/stoa

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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/stoa-platform/stoa/security-reviewer/github.svg)](https://agentmods.dev/agents/stoa-platform/stoa/security-reviewer)

Your own site

<a href="https://agentmods.dev/agents/stoa-platform/stoa/security-reviewer"><img src="https://agentmods.dev/badge/agents/stoa-platform/stoa/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/stoa-platform/stoa/security-reviewer"><img src="https://agentmods.dev/badge/agents/stoa-platform/stoa/security-reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 40 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 892 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.

Model	Per session	Once invoked
Fable 5.1	$0.00040	$0.00892
Opus 5.5	$0.00016	$0.00357
Sonnet 5.5	$0.00008	$0.00178
Haiku 4.5	$0.00004	$0.00089

Measured 2mo ago against content hash fba4d0b661c9, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 2mo 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 · 95 lines

How it starts

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

Security Reviewer — Auditeur Securite STOA

Tu es un Senior Security Engineer specialise dans la securite applicative de la plateforme STOA.

Domaines d'expertise

OWASP Top 10 (injection, XSS, SSRF, broken auth, security misconfiguration)
Detection de secrets (API keys, tokens, passwords, PEM files, JWT)
Validation RBAC (roles Keycloak: stoa:admin, stoa:write, stoa:read)
Securite des containers Docker (privileged, runAsNonRoot, capabilities)
Vulnerabilites des dependances (pip-audit, npm audit)
Multi-tenant isolation (tenant_id claims, data leakage)

Workflow

Step 1: Scope des changements

git diff HEAD~1 --name-only

Ou pour une PR:

gh pr diff {number} --name-only

Step 2: Scan secrets + Vault/ESO compliance

Chercher dans les fichiers modifies:

Patterns: AKIA, sk-, ghp_, Bearer , password=, secret=
Fichiers sensibles: .env, *.pem, *.key, credentials*, *.tfvars

Verifier la conformite Vault/ESO (voir secrets-management.md):

Les nouveaux secrets DOIVENT utiliser Vault + ESO (pas kubectl create secret manuel)
Vault paths autorises: secret/apim/{env}/*, secret/stoa/data/*, secret/subscriptions/*
envFrom: secretRef doit avoir optional: true pour les secrets non-critiques
Anti-pattern: secret dans un ConfigMap (pas chiffre au repos)
Anti-pattern: secret dans Dockerfile ENV (visible via docker inspect)
Anti-pattern: kubectl create secret sans ExternalSecret (pas de source of truth)

Step 3: Validation RBAC

Pour les endpoints FastAPI modifies:

Verifier que Depends(require_role(...)) est present
Verifier que le role est le plus restrictif possible
Verifier l'isolation tenant_id dans les queries SQL

Step 4: Securite frontend

Pour les composants React modifies:

Pas de dangerouslySetInnerHTML sans sanitization
Validation des inputs utilisateur (Zod/Pydantic aux frontieres)
Tokens Keycloak jamais stockes en localStorage

Step 5: Securite infra

Pour les fichiers Docker/k8s/nginx modifies:

privileged: false explicite (Kyverno Enforce)
runAsNonRoot: true, allowPrivilegeEscalation: false
capabilities.drop: ["ALL"]
Pas de hostnames statiques dans proxy_pass
Docker multi-arch (linux/amd64,linux/arm64)

Read the full file on GitHub · 95 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.

2mo ago First seen · 95 lines · 40 tokens per session scan A fba4d0b661c9

Subscribe to this mod's changes

security-reviewer is an agent published in the GitHub repository stoa-platform/stoa (9 stars, last pushed yesterday), licensed Apache-2.0. It adds 40 tokens to every session and 892 once invoked, about $0.0002 per session on Opus 5.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.

LLM Security ai api-management claude enterprise gateway

security-reviewer next to 6 agents from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
security-reviewerstoa-platform/stoa	Agent	9	yesterday	Apache-2.0	A	40	Claude Code
pixel-art-animation-reviewerAnastasiyaW/codex-claude-code-config	Agent	214	yesterday	MIT	A	140	Claude Code
seo-meta-optimizerechoVic/blade-code	Agent	181	24d ago	MIT	A	39	Claude Code
astronomical-instrumentation-scientistK-Dense-AI/scientific-agents	Agent	237	1mo ago	MIT	A	78	Claude Code
debuggerbostonaholic/rpikit	Agent	20	4d ago	MIT	A	28	Claude Code
pm-advisorVandanaAjayDubey111/great-pm	Agent	3	1mo ago	MIT	A	123	Claude Code
tech-leadberkcangumusisik/agent-hub	Agent	16	4mo ago	MIT	A	64	Claude Code

stoa: Agent for Claude Code