e2e-test-runner

e2e-test-runner is an agent for coding agents from iamcxa/kc-claude-plugins. It costs 38 tokens per session (15,599 once invoked), scanned A, original, MIT.

An agent that runs browser-based end-to-end flows described in YAML using the agent-browser command-line tool. It checks complete web journeys, records pass or fail results, and gathers screenshots and traces.

In plain words
What is it for?
Use it to run mapped flows against a live web app, verify expected page behavior, and collect failure screenshots or traces.
Why use it?
It provides repeatable execution and debugging evidence instead of requiring someone to perform each browser test manually.

Agent

Installs and runs on its own, but its text points at files inside its plugin — anything it tells you to read at a ${CLAUDE_PLUGIN_ROOT} path is only there once the plugin is installed. Installing the plugin gets both.

Part of the e2e-pipeline plugin — 11 skills, 8 agents, 2 hooks shipped together

Install

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.

agentmods
npx agentmods add agents/iamcxa/kc-claude-plugins/e2e-test-runner
Clone the repo
git clone --depth 1 https://github.com/iamcxa/kc-claude-plugins

Or install e2e-pipeline, the plugin that ships this one along with the rest of its 11 skills, 8 agents, 2 hooks.

Wrote 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.

agentmods badge for e2e-test-runner

README.md
[![agentmods](https://agentmods.dev/badge/agents/iamcxa/kc-claude-plugins/e2e-test-runner.svg)](https://agentmods.dev/agents/iamcxa/kc-claude-plugins/e2e-test-runner)
Your own site
<a href="https://agentmods.dev/agents/iamcxa/kc-claude-plugins/e2e-test-runner"><img src="https://agentmods.dev/badge/agents/iamcxa/kc-claude-plugins/e2e-test-runner.svg" alt="Measured on agentmods" height="20"></a>
Per session 38 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 15,599 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00038 $0.15599
Opus 5 $0.00019 $0.07799
Sonnet 5 $0.00008 $0.03120
Haiku 4.5 $0.00004 $0.01560

Measured 4d ago against content hash d141a05d7404, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

e2e-test-runner scanned grade A with 1 finding 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 4d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -s -o /dev/null -w "%{http_code}" {{base_url}} # Server reachable? 2xx/3xx = OK
e2e-pipeline/agents/e2e-test-runner.md · 1,263 lines

How it starts

The opening of the file, as written. The whole thing — 1,263 lines — stays where its author put it; the contents beside it link to each section on GitHub.

E2E Test Runner Agent

You are an autonomous E2E test executor. You run browser test flows defined in YAML against live web apps using the agent-browser CLI. You operate in a subagent context (or as a persistent teammate in Teams mode) — your job is to execute the flow, collect evidence, and return a structured summary.

Core Responsibilities

  1. Execute browser-based E2E test flows using agent-browser CLI commands
  2. Validate pre-flight conditions (CLI installed, server reachable, auth profile exists)
  3. Follow flow steps sequentially: snapshot, interact via @ref, wait for stability, validate expectations
  4. Capture screenshots on failure and on-demand, plus traces for debugging
  5. Continue through all steps even after failures — collect maximum evidence
  6. Return a structured pass/fail summary that the orchestrator can parse

Input Contract

The orchestrator skill dispatches this agent with the following fields. Parse them from the dispatch message before starting.

Field Required Description
flow_path Yes Absolute path to the flow YAML file
mapping_path Yes Absolute path to the mapping YAML file
auth_mode Required persistent or flow-managed; reject any other value
canonical_auth_profile Required Canonical app profile path (~/.agent-browser/<app>/)
ephemeral_auth_profile Flow-managed only Must equal auth_profile; omitted in persistent mode
auth_profile Yes Canonical profile in persistent mode; runtime-prepared ephemeral profile in flow-managed mode
auth_profile_freshness Required persistent-existing or verified-absent
base_url Yes Base URL of the app under test (e.g., http://localhost:3000)
app Yes App identifier matching the mapping's app field (e.g., my-app)
report_dir Yes Absolute path to the directory for report output (create with mkdir -p if missing)
browser_runtime Required Absolute path to the plugin's bin/e2e-browser-runtime.js
browser_run_id Required Run identity shared by every browser runner in this orchestrator invocation
browser_receipt Required Absolute receipt path under this runner's report_dir
diagnostic_init_scripts Optional Ordered list of absolute recorder paths; defaults to an empty list
service_runtime Conditional Absolute shared supervisor path when local services are orchestrator-owned
service_run_id Conditional Service ownership identity
service_state_dir Conditional Absolute service state/receipt directory
headed No Run browser in headed mode (default: true — always headed in current workflow)
suite_context No Marks a multi-site/suite run; the runtime always isolates the app session (default: false)
video No When true, orchestrator will dispatch media-processor for screenshot-based MP4 after this agent completes (default: false). This agent always captures step screenshots regardless.

Read the full file on GitHub · 1,263 lines

Changes

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.

  1. 4d ago First seen · 1,263 lines · 38 tokens per session scan A d141a05d7404

Subscribe to this mod's changes

e2e-test-runner is an agent published in the GitHub repository iamcxa/kc-claude-plugins (3 stars, last pushed today), licensed MIT. It adds 38 tokens to every session and 15,599 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other agents, from other repositories

alchemist

Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…

drobins25/craft · 355 tokens

praman-sap-planner-cli

SAP UI5 test planner via Playwright CLI. Token-efficient alternative to MCP planner. Generates test plan + gold-standard spec using CLI commands.

mrkanitkar/playwright-praman · 36 tokens

FAI Browser Agent

Browser automation agent — navigates websites, extracts data, and executes web workflows using Playwright MCP and vision analysis. Domain-restricted, no credential entry, human approval for transactions.

frootai/frootai · 41 tokens

dogfood-persona

Drives the running whiteboard app as a realistic end-user persona via the Playwright MCP browser tools, to surface friction (bugs, missing affordances, confusing/slow/dead-end flows). Spawned by the dogfood-triage workflow and by the review workflow's optional Dogfood phase. Pass the persona, goal, app URL, and (for…

kamiazya/whiteboard · 86 tokens

e2e-tester

Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.

mnzralee/claude-multi-agent-architecture · 41 tokens

judge-x-claude-code

Independent Gauntlet judge for Claude Code, invoked by the harness through the evaluator adapter (dispatch.ts --judge-x). Reads the evaluation brief, the success contract and the candidate — reading it and, to observe behavior, running its tests or a browser, never editing it — writes exactly one scorecard.json into…

gutomec/nirvana-os-engine · 106 tokens