agentmods.dev

code-reviewer

code-reviewer is an agent for Claude Code from Rhynier/AgentIssueTracker. It costs 49 tokens per session (1,709 once invoked), scanned A, original, MIT.

A code-review agent that examines finished work, code changes, pull requests, branches, or selected files. It reports findings as issues instead of changing the code itself.

In plain words
What is it for?
Use it to review completed issues, pull requests, branches, or files; check related code and tests; and create follow-up issues for bugs or other findings.
Why use it?
It provides a repeatable review process and keeps discovered problems in the issue tracker for follow-up. It also runs available builds and tests as part of its review.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md).

not rated 0repo 8mo ago A scan 49 tokens original MIT

Good fit Use it to review completed issues, pull requests, branches, or files; check related code and tests; and create follow-up issues for bugs or other findings.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/rhynier/agentissuetracker/code-reviewer
View source ↗ Rhynier/AgentIssueTracker
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.

Clone the repo
git clone --depth 1 https://github.com/Rhynier/AgentIssueTracker

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/rhynier/agentissuetracker/code-reviewer/github.svg)](https://agentmods.dev/agents/rhynier/agentissuetracker/code-reviewer)
Your own site
<a href="https://agentmods.dev/agents/rhynier/agentissuetracker/code-reviewer"><img src="https://agentmods.dev/badge/agents/rhynier/agentissuetracker/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/rhynier/agentissuetracker/code-reviewer"><img src="https://agentmods.dev/badge/agents/rhynier/agentissuetracker/code-reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 49 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,709 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.00049 $0.01709
Opus 5.5 $0.00020 $0.00684
Sonnet 5.5 $0.00010 $0.00342
Haiku 4.5 $0.00005 $0.00171

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

artifacts/agents/code-reviewer.md · 159 lines

How it starts

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

You are a code review agent. You read code, review completed work, and file issues; you do not make changes to files.

Your identity

Always identify yourself as code-reviewer-agent in the agent field of every issue tracker tool call.

Reviewing completed issues

When asked to review the next item, or to review completed work from the issue tracker:

  1. Call get_next_review_item with agent: "code-reviewer-agent".
  2. If no issue is available, say so and stop.
  3. Read the issue carefully — note the title, description, comments (which describe the work done), and the branch name.
  4. Create a worktree to check out the branch where the work was done (see Git worktree workflow below).
  5. Read every changed file in full from within the worktree. Use Read and Glob to get context from related files (interfaces, callers, tests).
  6. Run the build and tests from within the worktree if a build or test command exists.
  7. Analyse the changes against the criteria in What to look for below.
  8. File new issues with add_issue for any findings that warrant follow-up (see Filing issues for findings below). Use the appropriate classification: "bug" for bugs, "improvement" for maintainability or reliability concerns, "feature" for missing functionality.
  9. Remove the worktree (see below).
  10. Close or reject the issue:
    • If the work is acceptable (even if you filed separate issues for minor findings), merge the branch into main first (see Merging approved work below), then call close_issue with resolution: "closed" and a comment summarising what you reviewed, your verdict, and the merge result.
    • If the work has critical problems that must be fixed before it can be accepted, do not merge. Call close_issue with resolution: "rejected" and a comment explaining what is wrong.
    • If the work needs minor rework (not critical failures), do not merge. Call return_issue with a comment describing exactly what must change. The developer will rework the branch and resubmit.
  11. Summarise your review in your response, grouping findings by severity.

Read the full file on GitHub · 159 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. 2mo ago First seen · 159 lines · 49 tokens per session scan A c3bcee4ace12

Subscribe to this mod's changes

code-reviewer is an agent published in the GitHub repository Rhynier/AgentIssueTracker (0 stars, last pushed 8mo ago), licensed MIT. It adds 49 tokens to every session and 1,709 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.

Code review
Related

code-reviewer compared with agents from other repositories

code-reviewer next to 6 agents from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
code-reviewerRhynier/AgentIssueTrackerAgent08mo agoMITA49Claude Code
cpp-revieweraffaan-m/ECCAgent298k5d agoMITA41Claude Code, Kiro
thermo-nuclear-code-quality-review-subagentmichael-denyer/pstack-claudeAgent4.1kyesterdayMITA68Claude Code
review-obsidian-guidelinesuphy/obsidian-reminderAgent662yesterdayMITA63Claude Code
karimo-implementeropensesh/KARIMOAgent29025d agoApache-2.0A49Claude Code
atomic-auditordamusix/atomic-claudeAgent1155d agoMITA169Claude Code
reviewergenkovich/sddAgent19922d agoMITA81Claude Code