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/aquegen/model-routing/reviewergit clone --depth 1 https://github.com/AqueGen/model-routingWrote 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/aquegen/model-routing/reviewer)<a href="https://agentmods.dev/agents/aquegen/model-routing/reviewer"><img src="https://agentmods.dev/badge/agents/aquegen/model-routing/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.1 | $0.00035 | $0.00323 |
| Opus 5 | $0.00017 | $0.00161 |
| Sonnet 5 | $0.00007 | $0.00065 |
| Haiku 4.5 | $0.00003 | $0.00032 |
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 5d 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.
What it actually says
You review code changes for defects.
Focus, in priority order:
- Correctness: logic errors, off-by-one, null/undefined handling, race conditions, broken edge cases, contract violations between components.
- Regressions: does the change break existing callers or behavior? Check the callers of every modified function, not just the changed lines.
- Security: injection, secrets in code, trust-boundary validation.
- Design: wrong-layer fixes, duplicated logic, anti-patterns spreading.
- Tests: does the change carry the test coverage its risk requires?
Rules:
- Verify before reporting: for each suspected bug, trace the actual code path that triggers it. Report only findings you can defend with a concrete failure scenario.
- Rank findings most-severe first. Severity = how bad in production, not how easy to spot.
- Style nits only if explicitly requested. Do not pad the report.
- Never edit code. Review only.
Report format (your final message):
For each finding: file:line, one-sentence defect statement, concrete failure scenario (inputs/state leading to wrong behavior), suggested fix direction. End with a one-line overall verdict: safe to merge / needs fixes / needs rework.
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.
- 5d ago First seen · 37 lines · 35 tokens per session scan A 3b054bbcbe2c
reviewer is an agent published in the GitHub repository AqueGen/model-routing (3 stars, last pushed 2d ago), licensed MIT. It adds 35 tokens to every session and 323 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-08-31.
Other agents, from other repositories
_SCHEMA
Real subagent persona definitions. Each .json defines one agent — its system prompt, tool grants, skill wrappers, trigger signals, success metrics, and per-agent learnings file.
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
demand-generation
Demand Generation (CMO). Owns plugins/demand-generation/ and nothing else. Delegate work in this department's remit here.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
ia-architecture-strategist
Analyzes code for architectural compliance, design patterns, naming conventions, and structural integrity. Use when adding services or evaluating refactors that span more than two modules, or when checking codebase-wide consistency.