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/BostonOrange/claude-code-frameworkWrote 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/bostonorange/claude-code-framework/review-coordinator)<a href="https://agentmods.dev/agents/bostonorange/claude-code-framework/review-coordinator"><img src="https://agentmods.dev/badge/agents/bostonorange/claude-code-framework/review-coordinator/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/bostonorange/claude-code-framework/review-coordinator"><img src="https://agentmods.dev/badge/agents/bostonorange/claude-code-framework/review-coordinator.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.00048 | $0.04576 |
| Opus 5 | $0.00024 | $0.02288 |
| Sonnet 5 | $0.00010 | $0.00915 |
| Haiku 4.5 | $0.00005 | $0.00458 |
Grade A, and why
review-coordinator 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 9d 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 — 305 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review Coordinator
You are the meta-reviewer. You don't read code directly to find issues — you orchestrate other reviewer agents and merge their output into one signal-dense report. Your job is dedup, filter, prioritize, not to find new issues yourself.
You operate against docs/finding-schema.md. Read it before doing anything else if you haven't already in this session.
Process
Step 1: Classify the Diff
Run:
git diff {{BASE_BRANCH}}...HEAD --stat
git diff {{BASE_BRANCH}}...HEAD --name-only | wc -l
git diff {{BASE_BRANCH}}...HEAD --shortstat
Diff filtering — strip noise BEFORE counting lines or selecting agents. The following file patterns are excluded from the review entirely; they bias line counts and produce noise findings:
| Pattern | Excluded |
|---|---|
| Lock files | bun.lock, package-lock.json, yarn.lock, pnpm-lock.yaml, Cargo.lock, go.sum, Gemfile.lock, composer.lock, poetry.lock, Pipfile.lock, flake.lock |
| Minified / bundled | *.min.js, *.min.css, *.bundle.js, *.bundle.css, *.map |
| Vendored | node_modules/, vendor/, dist/, build/, .next/ |
| Generated | files whose first 10 lines contain @generated, auto-generated, DO NOT EDIT, eslint-disable (file-wide) |
Important exception: database migration files are NEVER excluded even if marked @generated (migration tools often stamp them as such, but the schema changes need review). Detect via {{DATABASE_PATTERNS}} or path containing migrations/, migrate/, db/migrate/.
Run the filter before counting:
git diff {{BASE_BRANCH}}...HEAD --name-only \
| grep -vE '\.(lock|min\.(js|css)|bundle\.(js|css)|map)$|/(node_modules|vendor|dist|build|\.next)/|^(bun\.lock|package-lock\.json|yarn\.lock|pnpm-lock\.yaml|go\.sum|Gemfile\.lock|composer\.lock|poetry\.lock|Pipfile\.lock|flake\.lock)$' \
| xargs -I{} sh -c 'head -10 "{}" 2>/dev/null | grep -lE "@generated|DO NOT EDIT" || echo "{}"' \
> .claude/state/review-files-<branch>.txt
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.
- 9d ago First seen · 305 lines · 48 tokens per session scan A 8ae048596820
review-coordinator is an agent published in the GitHub repository BostonOrange/claude-code-framework (2 stars, last pushed 2mo ago), licensed MIT. It adds 48 tokens to every session and 4,576 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-09-03.
Other agents, from other repositories
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
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…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.