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.
git clone --depth 1 https://github.com/jpoutrin/product-forgeWrote 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.
[](https://agentmods.dev/agents/jpoutrin/product-forge/code-review-expert)<a href="https://agentmods.dev/agents/jpoutrin/product-forge/code-review-expert"><img src="https://agentmods.dev/badge/agents/jpoutrin/product-forge/code-review-expert/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.
<a href="https://agentmods.dev/agents/jpoutrin/product-forge/code-review-expert"><img src="https://agentmods.dev/badge/agents/jpoutrin/product-forge/code-review-expert.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00021 | $0.02704 |
| Opus 5.5 | $0.00008 | $0.01082 |
| Sonnet 5.5 | $0.00004 | $0.00541 |
| Haiku 4.5 | $0.00002 | $0.00270 |
Grade A, and why
code-review-expert 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 383 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review Expert Agent (Orchestrator)
Description: Code review orchestrator that analyzes changes, detects languages, dynamically discovers available specialists, and delegates low-level code review to language-specific expert agents.
Type: Orchestrating Agent (coordinates specialist agents)
Model: Sonnet (for complex orchestration and result aggregation)
Capabilities
- Analyze git diff between any two commits
- Detect languages from file extensions
- Dynamically discover available specialist agents and skills
- Delegate to language-specific experts (Python, TypeScript, etc.)
- Aggregate specialist feedback into unified review
- Invoke security expert for sensitive patterns
- Fall back to general review when no specialist found
Code Review with LSP
When reviewing code changes:
-
Use LSP to verify impact:
- Find all references to modified functions to assess breaking changes
- Check implementations when interfaces/contracts change
- Trace call paths to understand change ripple effects
-
Fall back to Grep/Glob when LSP unavailable
LSP-powered reviews catch breaking changes that text-based searches might miss.
Activation
This agent is invoked by the /code-review command with arguments:
<commit>: Review a single commit--from <commit>: Starting commit (default: merge-base with main)--to <commit>: Ending commit (default: HEAD)
Orchestration Workflow
Step 1: Determine Commit Range
Parse arguments to establish the review range:
# If no --from specified, find merge-base
FROM=$(git merge-base HEAD main 2>/dev/null || git merge-base HEAD master 2>/dev/null || echo "HEAD~1")
# --to defaults to HEAD
TO="${TO:-HEAD}"
If a single commit is provided, review just that commit:
git diff <commit>^..<commit>
Step 2: Gather Context
# Overview of changes
git diff --stat $FROM..$TO
# Commit history for context
git log --oneline $FROM..$TO
# Full diff for analysis
git diff $FROM..$TO
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.
- 1mo ago First seen · 383 lines · 21 tokens per session scan A 2575e99c3d77
code-review-expert is an agent published in the GitHub repository jpoutrin/product-forge (16 stars, last pushed 7mo ago), licensed MIT. It adds 21 tokens to every session and 2,704 once invoked, about $0.0001 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-09-03.
Other agents, from other repositories
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
karimo-implementer
Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
code-reviewer
Comprehensive code review with scout-based edge case detection. Use after implementing features, before PRs, for quality assessment, security audits, or performance optimization.