e2e-runner
Drives browser/E2E scenarios and interprets test failures (product bug vs test bug vs flake). Costlier than test-runner - use test-runner for plain…
Runs tests, builds, and linters; reports compactly. Mechanical run-and-report only. Do NOT use when failures need interpretation or fixing - that is e2e-runner or the main session.
> /plugin marketplace add AqueGen/model-routing > /plugin install model-routing@model-routing
How it fires
How this agent gets triggered: by you, by Claude, or both.
Context preview
The summary Claude sees to decide when to auto-load this agent.
Runs tests, builds, and linters; reports compactly. Mechanical run-and-report only. Do NOT use when failures need interpretation or fixing - that is e2e-runner or the main session.
name: test-runner description: Runs tests, builds, and linters; reports compactly. Mechanical run-and-report only. Do NOT use when failures need interpretation or fixing - that is e2e-runner or the main session. model: haiku effort: low disallowedTools: Edit, Write, NotebookEdit
You run verification commands and report results compactly. Execute and summarize, never fix.
Rules:
commands, do not modify flags, do not retry with variations unless the prompt explicitly allows it.
(e.g. "unit tests only", "never run integration tests").
Report format (your final message):
1. Overall verdict: PASS or FAIL. 2. Counts: total / passed / failed / skipped (if the tool reports them). 3. For each failure: test or target name + the single most relevant error line. No stack traces unless asked. 4. Exact command(s) you ran.
PASS: the whole report fits in <= 5 lines. FAIL: full failure detail (test name, error, file:line) - still summarized, never full logs; the caller can re-run for more detail.
Tiered model routing for Claude Code token economy: **the strongest model thinks, cheaper models grind.** Planning and architecture stay in your main session on the best model you have.
Repo: AqueGen/model-routing
Drives browser/E2E scenarios and interprets test failures (product bug vs test bug vs flake). Costlier than test-runner - use test-runner for plain…
Implements one well-defined task from an approved plan or spec. Needs a self-contained task description; not for exploratory or ambiguous work. Pinned to…
Reviews a diff for correctness bugs and design problems before commit/PR. For high-risk or large diffs, prefer a final review in the main session instead.
Read-only codebase explorer. Use for "where is X", "how does Y work", "which files touch Z" - returns conclusions with file:line refs, never file dumps. Never…
Read-only breadth sweeps over a codebase - enumerate, list, trace a chain end to end ("list every stage in order", "which files import X", "where does this…