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.
git clone --depth 1 https://github.com/sjarmak/coding-agent-workflowsWrote 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.
[](https://agentmods.dev/agents/sjarmak/coding-agent-workflows/e2e-runner)<a href="https://agentmods.dev/agents/sjarmak/coding-agent-workflows/e2e-runner"><img src="https://agentmods.dev/badge/agents/sjarmak/coding-agent-workflows/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.
<a href="https://agentmods.dev/agents/sjarmak/coding-agent-workflows/e2e-runner"><img src="https://agentmods.dev/badge/agents/sjarmak/coding-agent-workflows/e2e-runner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00052 | $0.00932 |
| Opus 5.5 | $0.00021 | $0.00373 |
| Sonnet 5.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 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.
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.
- 1mo 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 (6 stars, last pushed 17d ago), licensed MIT. It adds 52 tokens to every session and 932 once invoked, about $0.0002 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-31.
Other agents, from other repositories
agent-tester
Senior QA Automation Engineer specializing in unit, integration, and E2E test suite creation.
vios-sqa
VIOS SQA agent. Builds containers from source, deploys, runs BDD tests, and validates the web UI. Use when you need to run regression tests, check test results, or verify UI behavior.
senior-qa
Senior QA engineer for acceptance tests. Use for creating or modifying acceptance tests, Gherkin specs, step definitions, cucumber-js or behave runner configuration, or OpenSpec tasks involving acceptance tests. Follows the acceptance-test-authoring skill.
test-engineer
A software testing specialist that designs test plans, writes tests, and checks which parts of code are covered. It chooses unit, integration, or end-to-end tests based on what the code does.
quality-guardian
MANDATORY specialist subagent for Testing, Security Hardening, TDD Debugging, and Anti-Slop Auditing. Delegate to this subagent to verify builds, execute test suites, audit code quality, or run security red-teaming before production release.
testing-specialist
Swift testing expert. Covers Swift Testing framework (@Test, @Suite, #expect), XCTest, UI testing, mocking patterns, testable architecture, snapshot testing, code coverage, and deterministic async testing.