pi-agents-config: Agent for Claude Code

.pi/agent/agents/code-reviewer.md

code-reviewer is an agent for Claude Code from niclejeune/pi-agents-config. It costs 33 tokens per session (256 once invoked), scanned A, original, MIT.

An agent that reviews code for correctness, security, readability, maintainability, error handling, input checks, tests, and performance. It is intended to be used after code is written or changed.

In plain words
What is it for?
Use it to review recent code changes, check for exposed secrets or missing validation, assess test coverage, and report issues by priority with specific fixes.
Why use it?
It can catch defects, security risks, and maintenance problems before modified code is accepted or released.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: model in frontmatter.

This is niclejeune/pi-agents-config's own configuration. It tells Claude Code how to work on pi-agents-config 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 pi-agents-config configures →

Reuse

Borrowing it

Nothing to install: this file belongs to niclejeune/pi-agents-config. 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/niclejeune/pi-agents-config/main/.pi/agent/agents/code-reviewer.md
Clone the repo
git clone --depth 1 https://github.com/niclejeune/pi-agents-config

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 code-reviewer

README.md
[![agentmods](https://agentmods.dev/badge/agents/niclejeune/pi-agents-config/code-reviewer/github.svg)](https://agentmods.dev/agents/niclejeune/pi-agents-config/code-reviewer)
Your own site
<a href="https://agentmods.dev/agents/niclejeune/pi-agents-config/code-reviewer"><img src="https://agentmods.dev/badge/agents/niclejeune/pi-agents-config/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.

agentmods 80×15 button for code-reviewer

Your own site · 80×15
<a href="https://agentmods.dev/agents/niclejeune/pi-agents-config/code-reviewer"><img src="https://agentmods.dev/badge/agents/niclejeune/pi-agents-config/code-reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 33 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 256 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.00033 $0.00256
Opus 5.5 $0.00013 $0.00102
Sonnet 5.5 $0.00007 $0.00051
Haiku 4.5 $0.00003 $0.00026

Measured 1mo ago against content hash db024e33e333, 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 1mo 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.

.pi/agent/agents/code-reviewer.md · 35 lines

What it actually says

Original Claude model hint: sonnet. Pi model mapped to gpt-5.5 / thinking medium.

You are running as a pi-teams teammate. Work independently, keep outputs concise, update task status when applicable, and send clear progress/final messages back to the team lead. You are a senior code reviewer ensuring high standards of code quality and security.

When invoked:

  1. Run git diff to see recent changes
  2. Focus on modified files
  3. Begin review immediately

Review checklist:

  • Code is simple and readable
  • Functions and variables are well-named
  • No duplicated code
  • Proper error handling
  • No exposed secrets or API keys
  • Input validation implemented
  • Good test coverage
  • Performance considerations addressed

Provide feedback organized by priority:

  • Critical issues (must fix)
  • Warnings (should fix)
  • Suggestions (consider improving)

Include specific examples of how to fix issues.

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. 1mo ago First seen · 35 lines · 33 tokens per session scan A db024e33e333

Subscribe to this mod's changes

code-reviewer is an agent published in the GitHub repository niclejeune/pi-agents-config (1 stars, last pushed 6mo ago), licensed MIT. It adds 33 tokens to every session and 256 once invoked, about $0.0001 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.

Related

Other agents, from other repositories

architect

Architecture sparring partner for Trellis. Pre-design boundary, contract, migration, release, and blast-radius review. Demands concrete file paths, command shapes, compatibility analysis, and rejected alternatives. NOT an implementer.

mindfold-ai/Trellis · 46 tokens

reviewer

Reviews code, plans, architecture risk, and test gaps without editing files.

heggria/taskflow · 17 tokens

risk-reviewer

Engineering risk review for backend, data, and infrastructure changes.

heggria/taskflow · 15 tokens

observer

PROVE Observe stage. Use to verify and review the runner's output — run tests, gather evidence, read the diff — with no Edit/Write authority over product code, so it cannot directly patch code to pass its own evidence. Do not use to build, plan, or decide ship/block.

FlyFission/nuclear-grade-context-engineering · 62 tokens

ccf-spec-checker

Use when /ccf:check reviews a finished implementation. Fresh-context reviewer that checks an implementation against the CCF spec — conformance, conventions, SOLID/OOP, spec drift, BE↔FE consistency. Read-only, returns findings with file:line, does NOT fix code. Invoked by /ccf:check, never for coding.

naniiluja/ccf · 78 tokens

adversarial-planner

Independent adversary for an implementation PLAN, before any code is written. Attacks the written plan's scope, non-goals, and decisions against the committed constraints it must honor, and surfaces only grounded objections for the human to decide. Never rewrites the plan and never sees the author's reasoning …

jakubsuplicki/codument · 82 tokens