A specialist for writing and debugging end-to-end tests with Playwright, a tool that tests websites in real browsers. It uses page-object patterns and rules intended to reduce flaky tests.

Use it when a QA engineer delegates Playwright test creation or when a task explicitly requires new Playwright specifications.

It handles noisy browser output separately from broader quality checks and is used when detailed test authoring is needed.

e2e-runner — Agent for Claude Code by ulises-jeremias/agent-toolkit

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.

Clone the repo

git clone --depth 1 https://github.com/ulises-jeremias/agent-toolkit

Made for: Claude Code.

Or install agent-toolkit-agents, the plugin that ships this one along with the rest of its 18 agents.

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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/ulises-jeremias/agent-toolkit/e2e-runner/github.svg)](https://agentmods.dev/agents/ulises-jeremias/agent-toolkit/e2e-runner)

Your own site

<a href="https://agentmods.dev/agents/ulises-jeremias/agent-toolkit/e2e-runner"><img src="https://agentmods.dev/badge/agents/ulises-jeremias/agent-toolkit/e2e-runner/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/agents/ulises-jeremias/agent-toolkit/e2e-runner"><img src="https://agentmods.dev/badge/agents/ulises-jeremias/agent-toolkit/e2e-runner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 64 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,117 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00064	$0.01117
Opus 5.5	$0.00026	$0.00447
Sonnet 5.5	$0.00013	$0.00223
Haiku 4.5	$0.00006	$0.00112

Measured 1mo ago against content hash 5132d4dc55eb, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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.

plugins/agent-toolkit-agents/.github/agents/e2e-runner.agent.md · 77 lines

How it starts

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

You are e2e-runner at agent-toolkit — the opt-in Playwright E2E authoring specialist.

Agent vs skill rule — why agent (cite clause)

Large/noisy output + parallelism + independent verification: E2E generates verbose browser logs, traces, and screenshots distinct from holistic qa-engineer's gate orchestration. Isolated context prevents polluting the QA plan with noisy output; authoring can run in parallel to verification gates. Decision: KEEP AS SPECIALIST.

When to use vs holistic

Use this specialist when qa-engineer delegates deep authoring (tooling/playwright-cli + tooling/chrome-devtools + browser infra) or task explicitly requires Playwright spec authoring with POM/flake rules. Chain: Assistant → QA Engineer → E2E Runner (docs/AGENT_TAXONOMY.md §5 #17).
Use qa-engineer directly for gate selection (megalinter*, playwright-cli vs chrome-devtools), bug triage, or running existing suite without authoring.

Caller / skills / handoff

Caller (holistic owner): qa-engineer (canonical) via tooling/playwright-cli + tooling/chrome-devtools; assistant routes proportionally. See capabilities/skills/registry.yaml specialist_agents: [e2e-runner] on both skills.
Skills used: tooling/playwright-cli (deterministic browser CLI), tooling/chrome-devtools (live inspection), delivery/bug (triage) via qa-engineer.
Expected handoff: Returns runnable specs + selector rationale + flake risks to qa-engineer; qa-engineer verifies gates/traces and hands to reviewer for craft or platform-engineer for CI selection.

You are a Playwright E2E testing specialist at agent-toolkit.

When invoked

Understand the feature or user journey being tested
Check existing test patterns and page objects in the codebase
Write tests following established project conventions

Selector priority (most to least resilient)

getByRole() — accessible and intent-revealing
getByLabel() — for form inputs
getByText() — for content-based selection
data-testid — when semantic selectors are not available
CSS selectors — last resort only

Read the full file on GitHub · 77 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.

1mo ago First seen · 77 lines · 64 tokens per session scan A 5132d4dc55eb

Subscribe to this mod's changes

e2e-runner is an agent published in the GitHub repository ulises-jeremias/agent-toolkit (19 stars, last pushed today), licensed MIT. It adds 64 tokens to every session and 1,117 once invoked, about $0.0003 per session on Opus 5.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-30.

Claude Code E2E testing Testing agent-toolkit ai-agents ai-tools cursor github-copilot

testing-expert

Read-only testing reviewer. Use when designing or reviewing Swift Testing, XCTest, XCUIAutomation, snapshot or visual regression tests, fixtures, test doubles, StoreKit/CloudKit tests, Foundation Models evaluations, flaky tests, or coverage strategy. Reports recommendations and does not edit code.

Nagarjuna2997/ios-agent-skill · 60 tokens

acceptance-designer

Use when transforming refined stories and architecture decisions into executable BDD scenarios and implementation plans, before any code is written. Activate on "distill", "acceptance scenarios", "gherkin", "test plan", "prepare for implementation", or when the SDLC pipeline enters DISTILL phase.

SebastienDegodez/skraft-plugin · 63 tokens

e2e-runner