agentmods.dev

code-reviewer

A pull-request review checklist for checking changed code for security, correctness, performance, and maintainability problems.

In plain words
What is it for?
It helps review pull requests, group findings by severity, and approve changes when no issues are found.
Why use it?
It gives reviews a consistent focus and keeps comments limited to issues in the modified files.

Agent for Claude Code

98 5d ago A scan 0 tokens original MIT
View the source file sirsjg/flux
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/sirsjg/flux/code-reviewer
Clone the repo
git clone --depth 1 https://github.com/sirsjg/flux

Made for: Claude Code.

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 299 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.00000 $0.00299
Opus 5 $0.00000 $0.00150
Sonnet 5 $0.00000 $0.00060
Haiku 4.5 $0.00000 $0.00030

Measured 2d ago against content hash ff6118b72d68, 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.

.claude/agents/code-reviewer.md · 51 lines

What it actually says

Code Review Checklist

Review PRs against this checklist. Be concise - only comment on actual issues.

Critical (must fix)

  • Security vulnerabilities (injection, XSS, secrets in code)
  • Data loss or corruption risks
  • Breaking changes to public APIs
  • Crashes or unhandled errors in critical paths

Warning (should fix)

  • Missing error handling for external calls
  • Race conditions or concurrency issues
  • Performance problems (N+1 queries, unbounded loops)
  • Missing input validation at system boundaries
  • Inconsistent behavior with existing patterns

Suggestion (nice to have)

  • Code style inconsistencies
  • Missing tests for new functionality
  • Unclear naming or documentation gaps
  • Minor code duplication

Review Process

  1. Run git diff origin/<base>...HEAD to see changes
  2. Focus on modified files only - don't review unchanged code
  3. Check each file against the checklist above
  4. Post a single comment summarizing findings by severity
  5. If no issues found, approve with a brief summary of what was reviewed

Output Format

## Review: <PR Title>

### Critical
- [file:line] Issue description

### Warning
- [file:line] Issue description

### Suggestion
- [file:line] Issue description

### Summary
Brief assessment and recommendation (approve/request changes)

If a section has no items, omit it entirely.

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. 2d ago First seen · 51 lines · 0 tokens per session scan A ff6118b72d68

Subscribe to this mod's changes

code-reviewer is an agent published in the GitHub repository sirsjg/flux (98 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 299 tokens. 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-30.

Code reviewProject managementSecurityaiai-agentskanbantask-managementworkflow
Related

Other agents, from other repositories

chorus-code-reviewer

Final ship-time review of an Idea's aggregate code change — the whole feature across all its tasks, not one task. Read-only; posts a VERDICT comment on the Idea. Spawn via the blocking subagent tool after the last task of an idea-rooted proposal is verified.

Chorus-AIDLC/Chorus · 62 tokens

code-reviewer

Final ship-time review of an Idea's aggregate code change — the whole feature across all its tasks, not one task. Read-only; posts a VERDICT comment on the Idea. Spawn after the last task of an idea-rooted proposal is verified.

Chorus-AIDLC/Chorus · 50 tokens

chorus-proposal-reviewer

Review submitted Chorus proposals for quality — check document completeness, task granularity, AC alignment, and cross-task dependencies. Spawn via the blocking subagent tool after choruspmsubmitproposal.

Chorus-AIDLC/Chorus · 44 tokens

chorus-task-reviewer

Review submitted Chorus tasks — verify implementation against AC and proposal documents. Spawn via the blocking subagent tool after chorussubmitforverify.

Chorus-AIDLC/Chorus · 32 tokens

proposal-reviewer

Review submitted Chorus proposals for quality — check document completeness, task granularity, AC alignment, and cross-task dependencies. Spawn after choruspmsubmitproposal.

Chorus-AIDLC/Chorus · 31 tokens

task-reviewer

Review submitted Chorus tasks — verify implementation against AC and proposal documents. Spawn after chorussubmitforverify.

Chorus-AIDLC/Chorus · 20 tokens