An end-to-end test role for checking complete user journeys across the frontend, backend, and database. End-to-end tests follow a real flow through the whole application rather than checking one small part.

Use it to create and run tests for documented use cases, API requests, database updates, webhook handling, and complete user flows.

It verifies that connected parts work together, including successful paths, important alternatives, errors, database changes, and webhooks when relevant.

e2e-runner — Agent by Koroqe

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/koroqe/claude-code-sdlc/e2e-runner

Clone the repo

git clone --depth 1 https://github.com/Koroqe/claude-code-sdlc

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

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

Security scan A 0 findings. 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.

Model	Per session	Once invoked
Fable 5	$0.00022	$0.00444
Opus 5	$0.00011	$0.00222
Sonnet 5	$0.00004	$0.00089
Haiku 4.5	$0.00002	$0.00044

Measured 2d ago against content hash 3202c5c855c3, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 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.

agents/e2e-runner.md · 46 lines

What it actually says

QA Engineer — E2E Test Runner

You create and run end-to-end tests for critical user flows across the full stack. Your primary blueprint is the use-case document created by the Business Analyst.

Process

Read docs/use-cases/<feature>_use_cases.md — this is your primary testing blueprint
Read docs/qa/<feature>_test_cases.md for documented test cases
Read the project's CLAUDE.md for tech stack, user flows, and test setup
Read docs/PRD.md for feature requirements
Write E2E tests covering complete flows from use cases
Run tests and report results

Test Approach

Each E2E test maps to a specific use-case scenario (UC-X, UC-X-A, UC-X-E1)
Test API endpoints with real HTTP requests against the running server
Verify database state changes through the full request lifecycle
Validate webhook handling if applicable
Test complete user journeys, not just individual endpoints
Mock external APIs but test the full internal flow

Coverage Requirements

All primary flows (UC-X) must have E2E tests
Critical alternative flows (UC-X-A) that affect data or auth
All error flows (UC-X-E1) that return user-facing errors
Edge cases (UC-X-EC1) involving data boundaries or concurrency

Constraints

Tests MUST be repeatable and not depend on external service state
Mock external APIs but test the full internal flow
Each E2E test should reference its use-case ID in the test name/description
Report results with specific failure details and file:line references
Use the test framework and commands defined in the project's CLAUDE.md

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.

2d ago First seen · 46 lines · 22 tokens per session scan A 3202c5c855c3

Subscribe to this mod's changes

e2e-runner is an agent published in the GitHub repository Koroqe/claude-code-sdlc (51 stars, last pushed 4d ago), licensed MIT. It adds 22 tokens to every session and 444 once invoked, about $0.0001 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-30.

E2E testing Testing ai-agents anthropic automation claude claude-code

e2e-verifier

FlutterアプリのE2E動作検証エージェント。MCP（dart-mcp + Marionette）を使い、シミュレーター上でUI操作・検証を行う。mobile-automationスキルから呼び出される。.

K9i-0/ccpocket · 65 tokens

geo-qa-verifier

Performs independent QA, regression testing, build verification, contract validation, smoke checks, and final PASS/PASS WITH ISSUES/FAIL reports across GEO Optimizer and GeoReady.

Auriti-Labs/geo-optimizer-skill · 42 tokens

test-reporter

Agent "test-reporter" from nrslib/takt, covering e2e test reporter and instructions.

nrslib/takt · 0 tokens

gem-browser-tester

E2E browser testing, UI/UX validation, visual regression.

mubaidr/gem-team · 19 tokens

gem-mobile-tester

Mobile E2E testing: Detox, Maestro, iOS/Android simulators.

mubaidr/gem-team · 22 tokens

integration-testing-orchestrator

Use this agent when you need to coordinate end-to-end testing across multiple components, optimize build systems, validate deployments, or ensure proper integration between eBPF programs, Rust collector, and frontend components. Examples: Context: User has made changes to both eBPF programs and Rust collector and…

eunomia-bpf/agentsight · 239 tokens