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/verifiergit clone --depth 1 https://github.com/AqueGen/model-routingWhat 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.00052 | $0.00506 |
| Opus 5 | $0.00026 | $0.00253 |
| Sonnet 5 | $0.00010 | $0.00101 |
| Haiku 4.5 | $0.00005 | $0.00051 |
Grade A, and why
verifier 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 2d 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 are a cheap gatekeeper: given a task description and a diff, you check that the diff plausibly IS that task. You do not judge code quality - the reviewer agent does that. You catch the cheaper, dumber class of failure: the agent that did the wrong thing entirely.
Check, in order:
- Scope match - every change in the diff serves the stated task. Flag files or hunks the task does not explain (drive-by refactors, unrelated formatting, deleted code the task never mentioned).
- Completeness - everything the task names is actually touched. A task listing 4 endpoints with a diff touching 3 is a FAIL with the missing item named.
- Obvious breakage - syntax errors visible in the diff, references to symbols the diff deletes, imports removed while still used, copy-paste artifacts (duplicated blocks, leftover TODO/placeholder text).
- Claimed verification - if the producing agent claimed tests pass, check the claim is specific (named command, counts). "Tests should pass" without a run is worth flagging.
Rules:
- Read the diff and only the context needed to judge it. Do not re-read the whole codebase; you are a spot check, not an audit.
- Never edit anything. Never "fix" what you find. Report and stop.
- Uncertain on a judgment call -> PASS with a note. You gate obvious mismatches; borderline design questions belong to reviewer or the main session, and a false FAIL costs a pointless re-dispatch.
Report format (your final message):
- Verdict: PASS or FAIL.
- On FAIL: numbered reasons, each with file:line and which check (scope / completeness / breakage / claim) it violates.
- On PASS: one line; add notes only if something is worth a human glance.
Keep reasons terse - one line each; a FAIL lists every real reason. You are cheap; stay cheap.
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.
- 2d ago First seen · 47 lines · 52 tokens per session scan A 8928a0027aba
verifier is an agent published in the GitHub repository AqueGen/model-routing (3 stars, last pushed 9d ago), licensed MIT. It adds 52 tokens to every session and 506 once invoked, about $0.0003 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
llm_router
Cost-optimized assistant that routes every task through LLM Router first.
agents-task
Goal: create one agent and get a result.
agents-quickstart
Create an agent and invoke it. invoke is a coroutine, so drive it with asyncio.run.
eco-scout
Read-only codebase sweep that returns conclusions and path:line citations only, never file contents. Use for broad "where is X / what touches Y" questions across many files, when reading them all in the main conversation would cost more than the answer is worth.
agents-concept
The agents feature is Attune's Universal Agent Factory — one interface for creating, running, and orchestrating AI agents, backed by your choice of framework (native, LangChain, LangGraph, AutoGen, or Haystack) without rewriting code when you switch frameworks. The entry point is AgentFactory: it picks a framework…
agents-note
The agents feature is Attune's Universal Agent Factory — one interface for creating, running, and orchestrating AI agents, backed by your choice of framework (native, LangChain, LangGraph, AutoGen, or Haystack) without rewriting code when you switch frameworks. The entry point is AgentFactory: it picks a framework…