Skip to content
Development
Agent

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 run-and-report.

Boost this agent
@aquegenaquegen@aquegen
From plugin
model-routing
37 skills7 agents1 command2 hooks
Install
> /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.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.

Context preview

The summary Claude sees to decide when to auto-load this agent.

Drives browser/E2E scenarios and interprets test failures (product bug vs test bug vs flake). Costlier than test-runner - use test-runner for plain run-and-report.

Agent definition

e2e-runner.md
name: e2e-runner
description: Drives browser/E2E scenarios and interprets test failures (product bug vs test bug vs flake). Costlier than test-runner - use test-runner for plain run-and-report.
model: sonnet
effort: medium

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):

1. Verdict: what happened, in one sentence. 2. Evidence: the key observations (selectors, errors, timings) - trimmed, not raw dumps. 3. Diagnosis: product bug / test bug / environment / flake, with reasoning. 4. Suggested next step for the caller.

Keep the step log to <= 20 lines. Failure interpretation is never truncated.

Read it on GitHub ↗
Ships withmodel-routing

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.

Get the whole plugin
Stats
JavaScriptNodeBashC#GitHub
+4 tags
PlaywrightMermaidAnthropicMCP
3
Stars
0
Forks
Active
Maintenance
JavaScript
Language
MIT
License
4d ago
Last commit
2mo ago
Created

Repo: AqueGen/model-routing

In this plugin
7 agents2 hooks1 command1 skill
See everything inside

Other agents on model-routing.