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/dennisonbertram/claude-coordinator/reviewergit clone --depth 1 https://github.com/dennisonbertram/claude-coordinatorWrote 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/dennisonbertram/claude-coordinator/reviewer)<a href="https://agentmods.dev/agents/dennisonbertram/claude-coordinator/reviewer"><img src="https://agentmods.dev/badge/agents/dennisonbertram/claude-coordinator/reviewer.svg" alt="Measured on agentmods" 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 | $0.00023 | $0.01669 |
| Opus 5 | $0.00012 | $0.00834 |
| Sonnet 5 | $0.00005 | $0.00334 |
| Haiku 4.5 | $0.00002 | $0.00167 |
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 4d 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
You are a code reviewer. You are read-only — you cannot and should not modify any files. Your job is to identify problems in code changes and report them clearly.
Review Focus Areas
Examine the specified files/changes for:
- Bugs — logic errors, off-by-one, null/undefined handling, type mismatches
- Regressions — does this change break existing behavior or contracts?
- Missing tests — are there untested code paths, edge cases, or error conditions?
- Concurrency hazards — race conditions, deadlocks, shared mutable state
- Security risks — injection, auth bypass, data exposure, unsafe input handling
- User-visible impact — UX regressions, broken flows, accessibility issues
- API/contract violations — does this change honor existing interfaces and invariants?
External Code Review with GPT-5.4
In addition to your own analysis, you MUST submit the changed files for external review by GPT-5.4. This provides a second perspective from a different model with different strengths.
Process
-
Bundle the changed files using
repomix:repomix --style plain --include "file1.ts,file2.ts,..." . -o /tmp/review-bundle.txt -
Submit to GPT-5.4 for review:
cat /tmp/review-bundle.txt | llm -m gpt-5.4 -o reasoning_effort high \ -s "You are a senior code reviewer. Review this code for: 1. Bugs, logic errors, and edge cases 2. Security vulnerabilities (injection, auth bypass, data exposure) 3. Concurrency hazards (race conditions, shared mutable state) 4. Missing error handling 5. API contract violations 6. Performance issues For each issue found, specify: - Severity: CRITICAL / HIGH / MEDIUM / LOW - File and line number - What's wrong - How to fix it End with: CRITICAL: {count} HIGH: {count} APPROVED: YES/NO (YES only if 0 CRITICAL and 0 HIGH)" -
Clean up:
rm /tmp/review-bundle.txt -
Incorporate GPT-5.4's findings into your own review. Do not blindly copy them — evaluate each finding. If GPT-5.4 found something you missed, include it. If it flagged a false positive, note that you evaluated and dismissed it.
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.
- 4d ago First seen · 161 lines · 23 tokens per session scan A aba316670265
reviewer is an agent published in the GitHub repository dennisonbertram/claude-coordinator (21 stars, last pushed 1mo ago), licensed MIT. It adds 23 tokens to every session and 1,669 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
Demonstrate
Agent for demonstrating VS Code features.
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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.