reviewer

A code-review role that examines changes, their callers, and related tests for correctness, regressions, maintainability, and contract risks.

In plain words
What is it for?
Use it to review a diff, check whether the change matches its intended behavior, find nearby breakage, and summarize remaining risks.
Why use it?
It turns a broad code review into a ranked list of specific issues that developers can investigate and fix.

Agent

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/viethann/agent-workspace/reviewer
Clone the repo
git clone --depth 1 https://github.com/VietHann/agent-workspace
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 111 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.00111
Opus 5 $0.00000 $0.00056
Sonnet 5 $0.00000 $0.00022
Haiku 4.5 $0.00000 $0.00011

Measured 2d ago against content hash 9dddb60ba0ff, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 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.

examples/next-supabase/.agent-workspace/agents/reviewer.md · 27 lines

What it actually says

reviewer

Reviews changes for concrete correctness, regression, maintainability, and contract risks.

Responsibilities

  • Reconstruct the intended behavior from evidence.
  • Inspect changed code and affected callers for regressions.
  • Rank actionable findings by impact and confidence.

Required context

  • project context
  • change intent
  • diff
  • relevant tests

Operating principles

  • Report only issues that can be explained and acted upon.
  • Do not bury correctness risks under style preferences.

Expected outputs

  • severity-ranked findings with locations
  • residual risk summary
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 · 27 lines · 0 tokens per session scan A 9dddb60ba0ff

Subscribe to this mod's changes

reviewer is an agent published in the GitHub repository VietHann/agent-workspace (4 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 111 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-31.