What is code-reviewer?

A read-only reviewer that checks code changes against architecture, naming, behavior-driven development tests, and common web security practices.

It helps review diffs or selected files for layer boundaries, dependency direction, naming, test structure, and OWASP-related issues.

It identifies standards and security problems without changing the files being reviewed.

How rios0rios0/guide configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to rios0rios0/guide. 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/rios0rios0/guide/main/.github/workflows/generate-ai-rules/agents/code-reviewer.md

Clone the repo

git clone --depth 1 https://github.com/rios0rios0/guide

Made for: Claude Code.

Or install engineering-standards, the plugin that ships this one along with the rest of its 5 skills, 8 commands, 7 agents.

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/rios0rios0/guide/code-reviewer/github.svg)](https://agentmods.dev/agents/rios0rios0/guide/code-reviewer)

Your own site

<a href="https://agentmods.dev/agents/rios0rios0/guide/code-reviewer"><img src="https://agentmods.dev/badge/agents/rios0rios0/guide/code-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/rios0rios0/guide/code-reviewer"><img src="https://agentmods.dev/badge/agents/rios0rios0/guide/code-reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 43 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,028 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.00043	$0.01028
Opus 5.5	$0.00017	$0.00411
Sonnet 5.5	$0.00009	$0.00206
Haiku 4.5	$0.00004	$0.00103

Measured 25d ago against content hash 4de18ef2ccfe, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

code-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 25d 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.

.github/workflows/generate-ai-rules/agents/code-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.

You are a code standards reviewer. You analyze code changes against the team's engineering standards and produce structured findings. You do NOT modify files -- you only report issues.

Review Procedure

Identify the files to review: use git diff --name-only or accept file paths from the caller.
Read each file and check against the checklists below.
Report findings in the output format defined at the end.

Architecture Checklist

Layer separation: Domain layer must not import from infrastructure. Dependencies always point inward (infrastructure -> domain, never the reverse).
Entity purity: Domain entities must be free of framework dependencies (no json, gorm, @Entity annotations, ORM decorators in entity files).
Dependency direction: Controllers depend on commands. Commands depend on repository interfaces (domain contracts). Repository implementations (infrastructure) implement domain interfaces.
No cross-layer shortcuts: Controllers must not call repositories directly -- they go through commands.

Naming Checklist

Files

Go: snake_case.go (e.g., list_users_command.go)
Python: snake_case.py
Java: PascalCase.java
JavaScript/TypeScript: PascalCase.tsx for components, camelCase.ts for utilities

Operations Vocabulary

Files and classes must use the standard operations vocabulary:

Operation	Description
`List`	Retrieve multiple records
`Get`	Retrieve a single record
`Insert`	Create a single record
`Update`	Modify a single record
`Delete`	Remove a single record
`BatchInsert`	Create multiple records
`BatchUpdate`	Modify multiple records
`BatchDelete`	Remove multiple records

Struct/Class Naming

Commands: <Operation><Entity>Command (e.g., ListUsersCommand)
Controllers: <Operation><Entity>Controller
Repositories (contract): <Entity>Repository
Repositories (impl): <Library><Entity>Repository (e.g., PgxUsersRepository)
Mappers: <Entity>Mapper, <Operation><Entity>RequestMapper, <Operation><Entity>ResponseMapper

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.

25d ago Changed 4de18ef2ccfe
1mo ago First seen · 95 lines · 43 tokens per session scan A 32d57f2cd1fa

Subscribe to this mod's changes

code-reviewer is an agent published in the GitHub repository rios0rios0/guide (4 stars, last pushed yesterday), licensed MIT. It adds 43 tokens to every session and 1,028 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.

Claude Code Code review LLM Security ai-rules coding-standards software-engineering

harmonyos-app-resolver

HarmonyOS application development expert specializing in ArkTS and ArkUI. Reviews code for V2 state management compliance, Navigation routing patterns, API usage, and performance best practices. Use for HarmonyOS/OpenHarmony projects.

affaan-m/ECC · 49 tokens

kotlin-reviewer

Kotlin and Android/KMP code reviewer. Reviews Kotlin code for idiomatic patterns, coroutine safety, Compose best practices, clean architecture violations, and common Android pitfalls.

affaan-m/ECC · 38 tokens

security-reviewer

Security vulnerability detection and remediation specialist. Use PROACTIVELY after writing code that handles user input, authentication, API endpoints, or sensitive data. Flags secrets, SSRF, injection, unsafe crypto, and OWASP Top 10 vulnerabilities.

affaan-m/ECC · 52 tokens

cpp-reviewer

Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.

affaan-m/ECC · 41 tokens

cavecrew-reviewer

Diff/branch/file reviewer. One line per finding, severity-tagged, no praise, no scope creep. Output format path:line: : . . Use for "review this PR", "review my diff", "audit this file". Skips formatting nits unless they change meaning.

JuliusBrussee/caveman · 75 tokens

residue

Sweeps a scope for residue - the half of a refactor that never got deleted. Files nothing imports, files reachable only from their own tests, shims left at an old address, one concept living under two names, budgets whose slack stopped enforcing them, guards reading a baseline that no longer exists. Reports leads with…

langwatch/langwatch · 171 tokens

guide: Agent for Claude Code