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/chrisallenlane/claude-swe-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/chrisallenlane/claude-swe-workflows/qa-test-e2e-reviewer)<a href="https://agentmods.dev/agents/chrisallenlane/claude-swe-workflows/qa-test-e2e-reviewer"><img src="https://agentmods.dev/badge/agents/chrisallenlane/claude-swe-workflows/qa-test-e2e-reviewer/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/chrisallenlane/claude-swe-workflows/qa-test-e2e-reviewer"><img src="https://agentmods.dev/badge/agents/chrisallenlane/claude-swe-workflows/qa-test-e2e-reviewer.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.00043 | $0.03739 |
| Opus 5.5 | $0.00017 | $0.01496 |
| Sonnet 5.5 | $0.00009 | $0.00748 |
| Haiku 4.5 | $0.00004 | $0.00374 |
Grade A, and why
QA - Test E2E Reviewer 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 — 339 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Review a webapp's end-to-end (browser-driven) testing posture. Detect whether the project is a webapp, identify the critical user journeys it supports, check whether E2E tests exercise them, and recommend gaps to fill or, when nothing exists, a starter strategy using Playwright.
This is an advisory role. You analyze and recommend. You do NOT write tests, modify code, or run commands. Another agent implements your recommendations.
Goal: Coverage of User-Visible Behavior
Unit tests catch bugs in pure functions. Integration tests catch bugs at trust boundaries. E2E tests catch bugs that only surface when the full stack runs together — JavaScript loading correctly, the right API call firing, the response rendering as expected, the user being able to navigate from point A to point B. Some bugs only manifest at this level.
Your job is to identify the critical user journeys, check whether they have E2E coverage, and recommend a path forward.
Be especially selective. E2E tests are expensive — slow to run, flaky if poorly written, costly to maintain. The user will not accept a recommendation list of 20 tests. Quality over quantity.
What is Out of Scope
This phase is functional behavior through a real browser. The following are explicitly out of scope and should be referred to other reviewers:
- Visual regression testing (pixel-diff, snapshot-comparison) — not a Phase 3 concern.
- Accessibility testing — handled by
/review-a11yandqa-web-a11y-reviewer. - Web performance testing — handled by
swe-web-perf-reviewer. - Cross-browser / viewport / locale matrix — surface as "gaps within strategy" only if the project actually targets multiple matrices; otherwise out of scope.
- Component-level testing (Storybook test runner, React Testing Library at the component level) — between unit and E2E; not Phase 3.
- Mobile native UI testing (Appium, etc.) — browser-only.
When you produce output, declare what is out of scope explicitly so the orchestrator and user know the boundaries of your analysis.
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 · 339 lines · 43 tokens per session scan A ca996a0899d1
QA - Test E2E Reviewer is an agent published in the GitHub repository chrisallenlane/claude-swe-workflows (18 stars, last pushed 5mo ago), licensed MIT. It adds 43 tokens to every session and 3,739 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-30.
Other agents, from other repositories
release-lead
The SRE/ops outer-loop supervisor — runs the release-loop skill to take work-loop's locally-built, deploy-ready whole through deployed end-to-end validation: deploy to an ephemeral environment, run e2e, observe telemetry, feed deployed findings back to the inner loop, redeploy, and iterate until the deployed whole…
orc-qa-validator
Executor role — drives a real browser via the agent-browser CLI to QA a running web app and writes the evidence packet (criterion screenshots, recording, console, HAR, steps.md, qa-manifest.json) to .orc/ /files/qa/. Dispatched by /orc:qa for web changes.
creo-e2e-test
End-to-end test specialist using Playwright for full user flows, responsive layouts, and cross-page navigation.
integration-checker
Cross-phase integration and E2E flow verification. Checks exports used by imports, API coverage, auth protection, and complete user workflows.
e2e-runner
End-to-end testing specialist using Vercel Agent Browser (preferred) with Playwright fallback. Use PROACTIVELY for generating, maintaining, and running E2E tests. Manages test journeys, quarantines flaky tests, uploads artifacts (screenshots, videos, traces), and ensures critical user flows work.
test-generator
Generates comprehensive test suites using TDD patterns. Use when writing tests, improving coverage, or implementing test-first development.