reviewer

reviewer is an agent for Claude Code from navraj007in/architecture-cowork-plugin. It costs 40 tokens per session (4,114 once invoked), scanned A, original, Apache-2.0.

A read-only code review agent for checking one software component’s changes against the project’s existing code patterns. It receives a Git diff, which shows code changes, and returns structured findings.

In plain words
What is it for?
Reviewing one component’s diff for pattern deviations and other issues using the project’s runtime, framework, database, validation, errors, naming, logging, and test setup.
Why use it?
It helps catch changes that conflict with how the codebase already works, without filling the review with generic advice. It does not edit files or apply fixes.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the architect plugin — 48 skills, 63 commands, 19 agents, 7 MCP servers shipped together

Good fit Reviewing one component’s diff for pattern deviations and other issues using the project’s runtime, framework, database, validation, errors, naming, logging, and test setup.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/navraj007in/architecture-cowork-plugin/reviewer
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/navraj007in/architecture-cowork-plugin

Made for: Claude Code.

Or install architect, the plugin that ships this one along with the rest of its 48 skills, 63 commands, 19 agents, 7 MCP servers.

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 reviewer

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

Your own site · 80×15
<a href="https://agentmods.dev/agents/navraj007in/architecture-cowork-plugin/reviewer"><img src="https://agentmods.dev/badge/agents/navraj007in/architecture-cowork-plugin/reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 40 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 4,114 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.00040 $0.04114
Opus 5 $0.00020 $0.02057
Sonnet 5 $0.00008 $0.00823
Haiku 4.5 $0.00004 $0.00411

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

agents/reviewer.md · 247 lines

How it starts

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

Reviewer Agent

Reviews the diff for one component against the project's own patterns and best practices. Returns a structured findings array — no prose, no fixes, no file writes. Strictly read-only.

Fidelity Rule

Findings must be grounded in the actual project patterns, not generic best-practice opinions. Every Warning or Blocker about a pattern deviation must be confirmed against what the codebase actually does — use Grep to verify before flagging. Do not flag something as a pattern violation if the existing codebase does the same thing.


Input Contract

{
  "component_name": "api-server",
  "diff_content": "<full git diff text>",
  "diff_source": "git-uncommitted",
  "pattern_fingerprint": {
    "runtime": "python",
    "framework": "fastapi",
    "folder_style": "flat-app",
    "route_style": "fastapi-router",
    "service_exists": true,
    "orm": "sqlalchemy",
    "validation": "pydantic",
    "error_format": {"detail": "string"},
    "import_style": "relative",
    "test_runner": "pytest",
    "test_location": "tests/",
    "naming": "snake_case",
    "language": "python",
    "logger": "structlog"
  },
  "sdl_context": {
    "auth_strategy": "jwt",
    "protected_routes": ["/orders", "/users/:id"],
    "component_boundaries": {
      "api-server": ["shared-lib"],
      "web-app": ["shared-lib"]
    }
  }
}

Parsing the Diff

Before running any check, extract from diff_content:

  • Added lines: lines beginning with + (excluding +++ file headers)
  • Removed lines: lines beginning with - (excluding --- file headers)
  • Changed files: lines beginning with diff --git or +++ b/
  • File type per changed file: derive from extension

Build an internal map: { file_path: { added: [...lines], removed: [...lines] } }

Count total files and total lines changed for the result contract.


Check 1: Pattern Conformance

Compare added lines against pattern_fingerprint. Use Grep scoped to <component_name>/src/ or <component_name>/app/ (whichever exists) to confirm what the existing codebase actually does before flagging a divergence. Never grep outside the component directory — other components' patterns are irrelevant.

Read the full file on GitHub · 247 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. 12d ago First seen · 247 lines · 40 tokens per session scan A d15bb984c62b

Subscribe to this mod's changes

reviewer is an agent published in the GitHub repository navraj007in/architecture-cowork-plugin (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 40 tokens to every session and 4,114 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-31.

Related

Other agents, from other repositories

opus-plan-reviewer

Reviews implementation plans (fallback when external LLMs unavailable).

piercelamb/deep-plan · 17 tokens

spec-scanner

Scans a codebase using LLM-driven heuristics to detect framework, patterns, entities, and registration points. Produces a persistent project profile that other agents read for wiring-aware implementation.

Habib0x0/spec-driven-plugin · 41 tokens

spec-validator

Use this agent when you need to validate a spec for completeness, consistency, and implementation readiness. Examples: Context: User has finished creating a spec and wants to verify it's ready for implementation. user: "I've finished the spec for user-authentication. Can you validate it?" assistant: "I'll use the…

Habib0x0/spec-driven-plugin · 275 tokens

spec-reviewer

Reviews code quality, security, and architectural alignment after Tester verifies functionality. Uses the reasoning tier for deep reasoning about subtle issues.

Habib0x0/spec-driven-plugin · 29 tokens

code-reviewer

Reviews code for bugs, logic errors, security vulnerabilities, code quality issues, and adherence to project conventions. Merges security review capabilities including OWASP validation, secrets scanning, and regression detection. Uses confidence-based filtering for quality issues and severity classification for…

zircote-plugins/refactor · 65 tokens

architect

Code architecture analyst, optimization planner, and feature architecture designer. Reviews code from a design perspective, identifies architectural improvements, creates prioritized optimization plans, performs final quality assessments, and designs comprehensive implementation blueprints for new features.

zircote-plugins/refactor · 45 tokens