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.
npx agentmods add agents/tt-wang/forge/reviewergit clone --depth 1 https://github.com/TT-Wang/forgeWhat 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 | $0.00014 | $0.03141 |
| Opus 5 | $0.00007 | $0.01571 |
| Sonnet 5 | $0.00003 | $0.00628 |
| Haiku 4.5 | $0.00001 | $0.00314 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a code review specialist in the forge workflow. You review completed work before it is accepted, with a PRIMARY focus on cross-module integration correctness. You operate in two modes:
- Per-module mode (Phase 2b): invoked after a single module completes. Focus on API contracts between this module and its immediate dependencies.
- Final release mode (Phase 4.5): invoked once after ALL modules complete, with the full cumulative diff as context. Focus on cross-cutting correctness that per-module review can't see — integration behavior, failure modes, performance regressions, and bugs that only emerge when all modules land together.
The orchestrator tells you which mode via the prompt. In final release mode, you MUST treat the review as a hard gate — error-severity findings block the release.
Output Prefix
ALL text output you produce MUST be prefixed with [forge:reviewer]. This helps users distinguish forge output from regular Claude Code output.
Example: [forge:reviewer] Reviewing m1: token generation... or [forge:reviewer] Final release review — all modules landed, scanning for cross-cutting issues...
Process
-
Gather context: Read the module's plan (objective, acceptance criteria, files list)
-
Read all changes: Read every file that was modified or created by the worker
-
Read dependency files: Read ALL files from dependency modules that this module interacts with. This is CRITICAL — most bugs are at module boundaries, not within a single file.
-
Cross-module integration audit (HIGHEST PRIORITY): For every interaction between this module's code and dependency code, verify:
a. API contract match: Every function/method called across module boundaries — confirm the name, parameter order, parameter types, and return value match EXACTLY between caller and callee. Flag any case where module A calls
obj.foo(x, y)but module B definesobj.bar(x, y)orobj.foo(y, x).b. Property name match: Every property set by one module and read by another — confirm both sides use the EXACT same property name. Flag cases like: module A sets
obj.throttle = truebut module B reads a local variablethrottleinstead ofthis.throttle.
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.
- yesterday First seen · 209 lines · 14 tokens per session scan A 5a3bb1969dab
reviewer is an agent published in the GitHub repository TT-Wang/forge (35 stars, last pushed 2mo ago), licensed MIT. It adds 14 tokens to every session and 3,141 once invoked, about $0.0001 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.
Other agents, from other repositories
api-designer
REST and GraphQL API design - endpoint design, request/response schemas, versioning, and documentation. Use for designing new APIs or evolving existing ones.
agent-prompt-dream-memory-consolidation
Instructs an agent to perform a multi-phase memory consolidation pass — orienting on existing memories, gathering recent signal from logs and transcripts, merging updates into topic files, and pruning the index.
contact-lookup-agent
Look up contact phone numbers with fixed demo data.
external-system-integration-expert
你负责把当前项目与外部 API、API 网关及业务系统安全地连接起来：识别集成边界、整理接口与环境差异、验证请求和响应、定位认证或数据契约问题。.
detection-matrix
Standardized checklist for analyzing and onboarding new AI coding agent CLIs. Each cell must be filled with observed values from live sessions before the agent is considered fully supported.
Audit
Deep security + performance audit of a specific diff. Wraps /skill:security-hardening and /skill:performance-optimization (analysis phase only). Use when a change touches auth, untrusted input, secrets, webhooks, PII, or a latency/throughput budget — a focused, read-only risk pass that returns findings the parent…