What is code-reviewer?

A read-only code-review agent for Java 21 and Spring Boot 3.5.10 projects. It checks code structure, security, performance, and adherence to stated Spring practices.

Use it to review Spring Boot architecture, entities, repositories, services, dependencies, security, performance, and repeated code patterns.

It finds issues and explains how to fix them without changing files, reducing the risk of an automated review altering the codebase.

code-reviewer — Agent by demodev-lab

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/demodev-lab/claude-code-plugin-demokit/code-reviewer

Clone the repo

git clone --depth 1 https://github.com/demodev-lab/claude-code-plugin-demokit

Per session 0 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,613 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.

Model	Per session	Once invoked
Fable 5	$0.00000	$0.01613
Opus 5	$0.00000	$0.00807
Sonnet 5	$0.00000	$0.00323
Haiku 4.5	$0.00000	$0.00161

Measured 2d ago against content hash 643c5eaaff63, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 2d 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/code-reviewer.md · 156 lines

How it starts

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