What is generate-e2e-test-plan?

A command that creates an end-to-end test plan from a completed feature specification. End-to-end testing checks a user flow through the whole application, often in a real browser.

It is for writing user-story-based test scenarios with directions to navigate, click, type, and verify results.

It turns acceptance criteria into repeatable browser checks and helps confirm that a user-facing feature works as specified.

How jnarowski/agentcmd configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to jnarowski/agentcmd. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/jnarowski/agentcmd/main/.claude/commands/generate-e2e-test-plan.md

Clone the repo

git clone --depth 1 https://github.com/jnarowski/agentcmd

Made for: Claude Code.

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/commands/jnarowski/agentcmd/generate-e2e-test-plan/github.svg)](https://agentmods.dev/commands/jnarowski/agentcmd/generate-e2e-test-plan)

Your own site

<a href="https://agentmods.dev/commands/jnarowski/agentcmd/generate-e2e-test-plan"><img src="https://agentmods.dev/badge/commands/jnarowski/agentcmd/generate-e2e-test-plan/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/commands/jnarowski/agentcmd/generate-e2e-test-plan"><img src="https://agentmods.dev/badge/commands/jnarowski/agentcmd/generate-e2e-test-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 3,718 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.00013	$0.03718
Opus 5.5	$0.00005	$0.01487
Sonnet 5.5	$0.00003	$0.00744
Haiku 4.5	$0.00001	$0.00372

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

Security

Grade A, and why

generate-e2e-test-plan 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 2mo 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.

.claude/commands/generate-e2e-test-plan.md · 473 lines

How it starts

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

Generate E2E Test Plan

Analyze completed spec implementation and generate comprehensive end-to-end test plan document with user stories and step-by-step browser automation directions for Playwright MCP.

When to use: After implementing a frontend feature with user-facing UI, when you need structured test scenarios for browser automation testing.

Variables

$specIdOrNameOrPath: $1 (required) - Either a timestamp ID (e.g., 2511191130), feature name (e.g., webhook-frontend), or full path to spec file

Instructions

Critical Rules:

Generate test plan as USER STORIES with conversational directions, not code
Focus on browser interactions: click, type, navigate, verify
Map test scenarios to spec's acceptance criteria (primary) or phases (fallback)
Detect feature type: full test plan for frontend, smoke test for backend
Always include all template sections (strict structure for consistency)
Use aggressive fallbacks for missing spec sections - always generate something
Output test plan as e2e-test-plan.md in spec folder root (overwrite if exists)
Output ONLY raw JSON at the end (no markdown fences, no text)

Test Plan Requirements:

3-7 user stories covering critical paths (frontend) or 2-3 smoke tests (backend)
Each story has: pre-conditions, step-by-step actions, expected outcomes
Include all 8 template sections: Prerequisites, Scenarios, Verification, Success Criteria, Troubleshooting, Seed Script, MCP Notes
Database seeding: always include section with template/examples (not working code)
No spec status validation - works for any status (draft, in-progress, review, completed)

Spec File Resolution

Parse and resolve $specIdOrNameOrPath:

If it's a full path (contains /): use as-is
Otherwise, look up in .agent/specs/index.json:
- For timestamp ID: Match by id field (object key)
- For feature name: Fuzzy match path (e.g., webhook-frontend matches todo/2511191130-webhook-frontend/spec.md)
- Use path from index: .agent/specs/{path}
If not found in index.json, fallback to directory search:
- Search in order: todo/, backlog/, done/
- For ID: Pattern {id}-*/spec.md
- For feature name: Pattern *{feature-name}*/spec.md (fuzzy match)
If still not found: Report error and exit

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

2mo ago First seen · 473 lines · 13 tokens per session scan A f8fad050ff78

Subscribe to this mod's changes

generate-e2e-test-plan is a command published in the GitHub repository jnarowski/agentcmd (18 stars, last pushed 10mo ago), licensed MIT. It adds 13 tokens to every session and 3,718 once invoked, about $0.0001 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-09-01.

E2E testing Frontend Testing

generate-e2e-test-plan next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
generate-e2e-test-planjnarowski/agentcmd	Command	18	10mo ago	MIT	A	13	Claude Code
playwright-test-healmicrosoft/playwright	Command	99k	yesterday	Apache-2.0	A	2	GitHub Copilot
webapp-testinghamr0/agentic-toolkit	Command	23	6d ago	Apache-2.0	A	35	Claude Code
verify-prdesplega-ai/qa-use	Command	29	1mo ago	MIT	A	0	Claude Code
ui-snapshot.templateevan043/claude-cli-advanced-starter-pack	Command	61	3mo ago	MIT	A	0	Claude Code
test-rundesplega-ai/qa-use	Command	29	1mo ago	MIT	A	0	Claude Code
laravel-playwrightjpcaparas/superpowers-laravel	Command	157	4mo ago	MIT	A	20	Claude Code

agentcmd: Command for Claude Code