code-reviewer

An agent that reviews completed software milestones against the original plan and expected quality standards. It examines the implementation, tests, architecture, documentation, and risks.

In plain words
What is it for?
Use it to review code quality, test coverage, security and performance concerns, design decisions, documentation, and the priority of each finding.
Why use it?
It helps find gaps, unjustified changes, and quality problems before a milestone is considered complete.

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/jpm1118/threadwork/code-reviewer
Clone the repo
git clone --depth 1 https://github.com/JPM1118/Threadwork
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 266 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.00266
Opus 5 $0.00000 $0.00133
Sonnet 5 $0.00000 $0.00053
Haiku 4.5 $0.00000 $0.00027

Measured yesterday against content hash 7ca30d3760c2, 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 yesterday.

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/code-reviewer.md · 33 lines

What it actually says

Code Reviewer Agent

Overview

The code-reviewer agent evaluates completed project milestones against original specifications and quality standards.

Key Responsibilities

Plan Alignment: Compare implementations against planning documents, identify deviations, and determine whether departures represent justified improvements or problematic changes.

Code Quality: Assess adherence to patterns, error handling, type safety, naming conventions, test coverage, and potential security/performance issues.

Architecture Review: Ensure SOLID principles, proper separation of concerns, system integration, and consideration of scalability needs.

Documentation Validation: Verify appropriate comments, file headers, function documentation, and project-standard compliance.

Issue Categorization: Classify findings as Critical (must address), Important (should address), or Suggestions (optional enhancements), with specific examples and actionable recommendations.

Communication: Request coding agent clarification on significant plan deviations, recommend plan updates when needed, and provide constructive improvement guidance.

Activation Criteria

Invoke this agent when a major project step has been completed requiring validation against the original plan and established coding standards.

Integration with Threadwork

When using Threadwork workflows:

  • Review after completing each Beads task
  • Verify TDD compliance (RED-GREEN-REFACTOR was followed)
  • Check that task notes are updated with discoveries
  • Ensure verification evidence exists before task closure
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. yesterday First seen · 33 lines · 0 tokens per session scan A 7ca30d3760c2

Subscribe to this mod's changes

code-reviewer is an agent published in the GitHub repository JPM1118/Threadwork (5 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 266 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.

Related

Other agents, from other repositories

Demonstrate

Agent for demonstrating VS Code features.

microsoft/vscode · 10 tokens

playwright-test-generator

Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.

microsoft/playwright · 151 tokens

.NET-Notebook-Migration-Agent

Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.

microsoft/ai-agents-for-beginners · 33 tokens

AVM Owner Triage

Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.

github/awesome-copilot · 61 tokens

Ultimate Transparent Thinking Beast Mode

Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.

github/awesome-copilot · 11 tokens

code-reviewer

Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.

anthropics/claude-cookbooks · 52 tokens