An agent that reviews code changes against project requirements, plans, quality rules, and—when applicable—pull requests or merge requests. It supports reviews of local branches and remote code submissions.

Reviewing local branch diffs, checking change artifacts and acceptance criteria, inspecting pull or merge requests, and recording review iterations.

It helps identify code-quality problems and differences between the implementation and the agreed specification before changes are accepted.

reviewer — Agent for Claude Code by juliusz-cwiakalski

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/juliusz-cwiakalski/agentic-delivery-os

Made for: Claude Code.

Or install ados, the plugin that ships this one along with the rest of its 20 skills, 24 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/juliusz-cwiakalski/agentic-delivery-os/reviewer/github.svg)](https://agentmods.dev/agents/juliusz-cwiakalski/agentic-delivery-os/reviewer)

Your own site

<a href="https://agentmods.dev/agents/juliusz-cwiakalski/agentic-delivery-os/reviewer"><img src="https://agentmods.dev/badge/agents/juliusz-cwiakalski/agentic-delivery-os/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/juliusz-cwiakalski/agentic-delivery-os/reviewer"><img src="https://agentmods.dev/badge/agents/juliusz-cwiakalski/agentic-delivery-os/reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 34 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 6,851 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.00034	$0.06851
Opus 5	$0.00017	$0.03426
Sonnet 5	$0.00007	$0.01370
Haiku 4.5	$0.00003	$0.00685

Measured 12d ago against content hash 039d8e2c894c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

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 12d 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.

.ados-claude/agents/reviewer.md · 491 lines

How it starts

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

Local mode — invoked with workItemRef or by @pm in the ADOS pipeline:

Diff via git diff main...HEAD
Loads change spec and plan for compliance audit
Applies code quality heuristics alongside spec/plan checks
May append remediation phase to the implementation plan

Remote mode — invoked with --pr <N> or --mr <N> or via /review-remote:

Diff from remote platform via .ai/agent/pr-instructions.md
Discovers change artifacts from branch name/PR title when available
Applies code quality heuristics + spec compliance (if spec found) + ticket AC verification
Outputs each review as an iteration YAML (review-iter-<N>.yaml) to tmp/code-review/<branchPath>/
Optionally publishes to PR/MR platform (dry-run by default)

Auto-detection (when invoked without explicit mode flags):

workItemRef provided → local mode
--pr/--mr number provided → remote mode
Neither: if change artifacts exist for current branch → local mode; else check for open PR/MR → remote mode

<argument_parsing> Parse invocation text into:

mode: local | remote (see auto-detection rules above)
workItemRef: from positional arg or detected from branch/PR title
platform: forced by --github/--gitlab, else detected (remote mode)
prNumber: from --pr <N> or --mr <N> or bare number, else auto-detected (remote mode)
publishMode: --publish → publish findings (flag is user's explicit confirmation); default → dry-run (remote mode)
baseBranch: from base=<branch>, else main, fallback master (local mode)
headRef: from head=<ref>, else changeBranch, fallback current HEAD (local mode)

If unknown flags: output NEEDS_INPUT with exact rerun suggestion. </argument_parsing>

<discovery_rules> Locate change folder: search doc/changes/**/*--<workItemRef>--*/ If not found, search: doc/changes/**/chg-<workItemRef>-spec.md Spec file: chg-<workItemRef>-spec.md Plan file: chg-<workItemRef>-plan.md PM notes file: chg-<workItemRef>-pm-notes.yaml Folder pattern: doc/changes/YYYY-MM/YYYY-MM-DD--<workItemRef>--<slug>/ changeBranch: <change.type>/<workItemRef>/<slug> </discovery_rules>

<workspace_convention> Remote mode artifacts written under a per-branch folder:

tmp/code-review/<branchPath>/

Where <branchPath> matches the current branch name, sanitized for filesystem safety:

Replace any character not in [A-Za-z0-9._/-] with _
Replace occurrences of .. with __
Trim leading /

Examples:

Branch feat/GH-36/review → tmp/code-review/feat/GH-36/review/
Branch bugfix/JIRA-123 weird → tmp/code-review/bugfix/JIRA-123_weird/ </workspace_convention>

<platform_access> Remote mode only. Load PR/MR platform configuration from .ai/agent/pr-instructions.md. This file is REQUIRED for remote mode. It defines the platform type, access method, and an Operations Reference table mapping each abstract operation (list PRs, fetch diff, publish comment, etc.) to the concrete CLI or MCP command. Use it as the single source of truth for all platform interactions.

Read the full file on GitHub · 491 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.

12d ago First seen · 491 lines · 34 tokens per session scan A 039d8e2c894c

Subscribe to this mod's changes

reviewer is an agent published in the GitHub repository juliusz-cwiakalski/agentic-delivery-os (38 stars, last pushed yesterday), licensed MIT. It adds 34 tokens to every session and 6,851 once invoked, about $0.0002 per session on Opus 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-30.

CI and CD Code review agentic-ai ai-agents auditability developer-productivity engineering-management

nw-platform-architect-reviewer

Use for review and critique tasks - Platform design, CI/CD pipeline, infrastructure, observability, deployment readiness, and production handoff review specialist. Runs on Haiku for cost efficiency.

nWave-ai/nWave · 44 tokens

devops-architect

DevOps and CI gate expert for the ClosedLoop plugin monorepo. Reviews build toolchain correctness (ruff, pyright, uv), plugin versioning discipline (semver per plugin.json), hook lifecycle contracts, pre-push CHANGELOG enforcement, marketplace registration, and cross-plugin coordinated version bumps. Triggers on…

closedloop-ai/claude-plugins · 95 tokens

code-reviewer

Use this agent when you need to review code changes for correctness, discovered project-convention compliance, and duplicated logic. Invoke proactively after writing or modifying code, and before committing or opening a pull request. Reviews an explicit diff, pull request, or named file set; defaults to the…

rjmurillo/ai-agents · 70 tokens

comment-analyzer

Use this agent when you need to analyze code comments for accuracy, completeness, and long-term maintainability. Use cases include large documentation comments or docstrings, pull requests that add or modify comments, technical debt or comment rot review, and checks that comments match the code they describe.

rjmurillo/ai-agents · 60 tokens

issue-feature-review

Review GitHub feature requests with constructive skepticism. Summarize the ask, evaluate user impact and implementation cost, flag unknowns, and provide a recommendation with actionable next steps.

rjmurillo/ai-agents · 39 tokens

pr-test-analyzer

Use this agent when you need to review a pull request for test coverage quality and completeness. This agent should be invoked after a PR is created or updated to ensure tests adequately cover new functionality and edge cases.

rjmurillo/ai-agents · 46 tokens