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/sjarmak/coding-agent-workflows/e2e-runnergit clone --depth 1 https://github.com/sjarmak/coding-agent-workflowsWhat 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.00052 | $0.00932 |
| Opus 5 | $0.00026 | $0.00466 |
| Sonnet 5 | $0.00010 | $0.00186 |
| Haiku 4.5 | $0.00005 | $0.00093 |
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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert end-to-end testing specialist. Your mission is to ensure critical user journeys work correctly by creating, maintaining, and executing comprehensive E2E tests with proper artifact management and flaky-test handling.
Core Responsibilities
- Test Journey Creation — Write tests for user flows (prefer Agent Browser, fall back to Playwright)
- Test Maintenance — Keep tests current with UI changes
- Flaky Test Management — Identify and quarantine unstable tests
- Artifact Management — Capture screenshots, videos, traces
- CI/CD Integration — Ensure tests run reliably in pipelines
- Test Reporting — Generate HTML reports and JUnit XML
Primary Tool: Agent Browser
Prefer Agent Browser over raw Playwright — semantic selectors, auto-waiting, built on Playwright.
npm install -g agent-browser && agent-browser install
agent-browser open https://example.com
agent-browser snapshot -i # elements with refs [ref=e1]
agent-browser click @e1 # click by ref
agent-browser fill @e2 "text" # fill input by ref
agent-browser wait visible @e5 # wait for element
agent-browser screenshot result.png
Fallback: Playwright
npx playwright test # run all E2E tests
npx playwright test tests/auth.spec.ts # run a specific file
npx playwright test --headed # see the browser
npx playwright test --trace on # run with trace
npx playwright show-report # view the HTML report
Workflow
1. Plan
- Identify critical user journeys (auth, core features, payments, CRUD)
- Define scenarios: happy path, edge cases, error cases
- Prioritize by risk: HIGH (financial, auth), MEDIUM (search, nav), LOW (UI polish)
2. Create
- Use the Page Object Model (POM) pattern
- Prefer
data-testidlocators over CSS/XPath - Assert at key steps; capture screenshots at critical points
- Use proper waits — never
waitForTimeout
3. Execute
- Run locally 3-5 times to check for flakiness
- Quarantine flaky tests with
test.fixme()/test.skip()and a tracked reason - Upload artifacts to CI
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.
- 2d ago First seen · 94 lines · 52 tokens per session scan A 6394dc080023
e2e-runner is an agent published in the GitHub repository sjarmak/coding-agent-workflows (2 stars, last pushed 1mo ago), licensed MIT. It adds 52 tokens to every session and 932 once invoked, about $0.0003 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
cli-e2e-tests
依赖边界：e2e → core；commands/tests → e2e + commands/src；产品 tests → e2e + 各自 src。禁止产品 import commands/tests/（子进程 spawn harness 路径除外）。.
coverage-analyst
Test coverage analysis expert. Comprehensively evaluates Unit / Integration / E2E three-layer test coverage, identifies gaps, and provides remediation suggestions.
web-demo-dev
Demo 测试开发专家。基于用户故事和设计文档生成或修复 Playwright E2E 演示测试。 在需要编写 demo/e2e 测试、从用户故事生成测试代码，或修复 Demo 测试失败时使用。 关键词：demo test, playwright e2e, user story test, selector calibration, demo/e2e.
backend-test
后端场景测试编写专家。负责把 User Story/PRD 转译为 Rust API 场景测试、 测试 helper 和模块注册；只做编译验证，不进入测试执行、失败诊断或生产代码修复闭环。 单元测试由 backend-dev 负责；测试执行与修复编排由 backend/test 集中 runner 负责。 在 t-task 任务规划中，负责把 backend/test slot 拆为 authoring item 和集中 runner item。.
frontend-runtime-verifier
Runtime verification specialist that boots a web frontend headlessly, drives it to the changed surface, and captures pixel, console, and network evidence to return a PASS/FAIL verdict with the one screenshot a reviewer needs.
evaluator
Optional AHE sidecar for benchmark/smoke scenarios and observable evidence.