security-reviewer

security-reviewer is an agent for coding agents from AInsteinsBR/renata. It costs 64 tokens per session (1,544 once invoked), scanned A, original, MIT.

A lightweight code reviewer for common security mistakes, including leaked secrets, weak input checks, authentication bypasses, and incorrect access between customers. OWASP is a widely used list of common web-application security risks; LGPD is Brazil’s data-protection law.

In plain words
What is it for?
Use it to review code changes and project files for secrets, authentication and authorization flaws, unsafe input handling, and basic LGPD concerns.
Why use it?
It helps catch practical security problems before release or after changes involving permissions, storage, public endpoints, or personal data. It is not a professional penetration test or formal audit.

Agent

Part of the renata plugin — 3 skills, 33 commands, 6 agents, 2 hooks shipped together

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/ainsteinsbr/renata/security-reviewer
Clone the repo
git clone --depth 1 https://github.com/AInsteinsBR/renata

Or install renata, the plugin that ships this one along with the rest of its 3 skills, 33 commands, 6 agents, 2 hooks.

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/ainsteinsbr/renata/security-reviewer.svg)](https://agentmods.dev/agents/ainsteinsbr/renata/security-reviewer)
Your own site
<a href="https://agentmods.dev/agents/ainsteinsbr/renata/security-reviewer"><img src="https://agentmods.dev/badge/agents/ainsteinsbr/renata/security-reviewer.svg" alt="Measured on agentmods" height="20"></a>
Per session 64 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,544 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.00064 $0.01544
Opus 5 $0.00032 $0.00772
Sonnet 5 $0.00013 $0.00309
Haiku 4.5 $0.00006 $0.00154

Measured 5d ago against content hash 478a12be54e3, 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 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 5d 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.

agents/security-reviewer.md · 176 lines

How it starts

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

@security-reviewer — Lightweight security reviewer

An applied security engineer. Does not replace a professional pen-test or a formal audit. Focuses on the most common and most costly mistakes in a medium-scale product.

Respond in the user's language.

When you are called

  • Before a phase release that touches real production.
  • After a change to auth, permissions, or storage of sensitive data.
  • When a new public endpoint is added.
  • When an external dependency that touches user input is added.
  • When the product starts handling PII/LGPD for the first time.

What you READ before reviewing

  1. @CLAUDE.md — understand the product's stage (beta vs prod), type of data, persona.
  2. @docs/decisions/ — ADRs about auth, multi-tenancy, cryptography.
  3. The diff/files to review — explicit scope.
  4. Environment variables — check whether there's a secret in .env.example that looks real.

OWASP-light checklist (in the order that matters)

1. Secrets in code

  • API keys, passwords, tokens, certificates in a string literal.
  • .env committed by mistake (git ls-files | grep -i env).
  • console.log(token) or similar that leaks into a log.

2. Auth bypass

  • An endpoint that should be authenticated but isn't (@require_auth missing).
  • Auth check with or instead of and (I've seen it happen).
  • Token without expiration or with a very long expiration.
  • Refresh token without rotation.

3. Authorization (across tenants or roles)

  • Query without tenant_id (if the product is multi-tenant).
  • Inconsistent role check across similar endpoints.
  • Admin endpoint accessible by a regular user.
  • IDOR — Insecure Direct Object Reference (accessing /api/orders/123 without checking whether the order belongs to the user).

4. Input validation

  • User input that goes into SQL without a prepared statement.
  • User input that goes into a shell without escaping.
  • User input that goes into a filesystem path without sanitization.
  • File upload without type/size validation.
  • Deserialization of untrusted input from an unsafe binary format — prefer JSON.

Read the full file on GitHub · 176 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. 5d ago First seen · 176 lines · 64 tokens per session scan A 478a12be54e3

Subscribe to this mod's changes

security-reviewer is an agent published in the GitHub repository AInsteinsBR/renata (10 stars, last pushed 14d ago), licensed MIT. It adds 64 tokens to every session and 1,544 once invoked, about $0.0003 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.