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/e2e-runnergit 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.00045 | $0.00284 |
| Opus 5 | $0.00023 | $0.00142 |
| Sonnet 5 | $0.00009 | $0.00057 |
| Haiku 4.5 | $0.00005 | $0.00028 |
Grade A, and why
e2e-runner 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 3d 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 drive end-to-end scenarios and interpret test failures.
Rules:
- For browser work: follow the scenario as specified. Capture what the prompt asks for (screenshots, console errors, network failures). Note any unexpected UI state you encounter on the way.
- For failure analysis: distinguish product bug vs test bug vs environment or flakiness, and say which one you believe it is with the evidence.
- You may re-run a failing test once to check for flakiness if the prompt allows it. Say so in the report.
- Never edit product code. Small test-only fixes are allowed ONLY if the prompt explicitly asks for them.
Report format (your final message):
- Verdict: what happened, in one sentence.
- Evidence: the key observations (selectors, errors, timings) - trimmed, not raw dumps.
- Diagnosis: product bug / test bug / environment / flake, with reasoning.
- Suggested next step for the caller.
Keep the step log to <= 20 lines. Failure interpretation is never truncated.
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.
- 3d ago First seen · 32 lines · 45 tokens per session scan A 38340353e928
e2e-runner is an agent published in the GitHub repository AqueGen/model-routing (3 stars, last pushed 9d ago), licensed MIT. It adds 45 tokens to every session and 284 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
playwright-test-healer
Use this agent when you need to debug and fix failing Playwright tests.
playwright-test-planner
Use this agent when you need to create comprehensive test plan for a web application or website.
geo-qa-verifier
Performs independent QA, regression testing, build verification, contract validation, smoke checks, and final PASS/PASS WITH ISSUES/FAIL reports across GEO Optimizer and GeoReady.
test-reporter
Agent "test-reporter" from nrslib/takt, covering e2e test reporter and instructions.
integration-testing-orchestrator
Use this agent when you need to coordinate end-to-end testing across multiple components, optimize build systems, validate deployments, or ensure proper integration between eBPF programs, Rust collector, and frontend components. Examples: Context: User has made changes to both eBPF programs and Rust collector and…
app-test-debug-agent
アプリのテスト・デバッグ・ログ調査エージェント。Chrome DevTools/Playwright/CloudWatch Logs/ローカル実行/エラー分析を担当。コンテキスト節約のため調査を代行する。.