e2e

e2e is a command for Claude Code from fmflurry/settings-opencode. It costs 10 tokens per session (595 once invoked), scanned A, a copy of e2e, MIT.

A command that creates and runs end-to-end tests with Playwright. End-to-end tests check a complete user journey in the application, from actions such as filling a form to seeing the expected result.

In plain words
What is it for?
Use it to turn a described user flow into Playwright tests, run the tests, check results, and capture failure evidence.
Why use it?
It helps verify real user flows and provides screenshots or videos when tests fail, making browser problems easier to investigate.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: mentions CLAUDE.md; mentions subagents.

Good fit Use it to turn a described user flow into Playwright tests, run the tests, check results, and capture failure evidence.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/fmflurry/settings-opencode/e2e
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.

Clone the repo
git clone --depth 1 https://github.com/fmflurry/settings-opencode

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.

agentmods badge for e2e

README.md
[![agentmods](https://agentmods.dev/badge/commands/fmflurry/settings-opencode/e2e/github.svg)](https://agentmods.dev/commands/fmflurry/settings-opencode/e2e)
Your own site
<a href="https://agentmods.dev/commands/fmflurry/settings-opencode/e2e"><img src="https://agentmods.dev/badge/commands/fmflurry/settings-opencode/e2e/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.

agentmods 80×15 button for e2e

Your own site · 80×15
<a href="https://agentmods.dev/commands/fmflurry/settings-opencode/e2e"><img src="https://agentmods.dev/badge/commands/fmflurry/settings-opencode/e2e.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 595 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 100% copy Near-identical to another mod 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00010 $0.00595
Opus 5.5 $0.00004 $0.00238
Sonnet 5.5 $0.00002 $0.00119
Haiku 4.5 $0.00001 $0.00060

Measured 26d ago against content hash 1eaecc190110, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

e2e 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 26d 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.

Origin

This is a copy

100% identical to e2e — 114 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/commands/e2e.md · 54 lines

How it starts

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

E2E Command

CC: delegate this to the e2e-runner subagent via the Agent tool (subagent_type: e2e-runner). The subagent inspects the repo and runs the steps below.

Generate and run end-to-end tests using Playwright: $ARGUMENTS

How This Command Works

  • The e2e-runner agent loads the playwright-e2e-authoring skill to write tests, then the playwright-e2e-review skill to self-audit your work.
  • The four hard rules—no mocks, Page Object Model, work by fixture, per-application-module—are canonical in tests/playwright/CLAUDE.md and enforced by the skills.
  • Tests drive the real gc.platform stack: Angular frontend on http://localhost:4200 + .NET backend on http://localhost:5100, orchestrated by docker-compose. No mocks, no stubs, no simulations.
  • The suite runs against system Chrome only (browser CDN is firewall-blocked); do not expect Firefox/WebKit.

Prerequisites

  1. Docker Compose stack running: docker-compose up from the repo root. Both frontend and backend must be healthy.
  2. Chrome installed on the host (system browser, not downloaded).
  3. Module name matches frontend structure: frontend/src/app/modules/<module> → tests/<module>/.

Run Commands

After the agent creates/updates your tests, use these commands (from tests/playwright/):

# Strict TypeScript check (must be clean before running)
npx tsc --noEmit --pretty false

# Run tests for your module
npm run test:e2e -- tests/<module>

# Run with visible browser (headed mode)
npm run test:e2e:headed -- tests/<module>

# Interactive UI mode for debugging
npm run test:e2e:ui -- tests/<module>

# View HTML report + traces after run
npm run test:e2e:report

Output

You receive:

  • Files created/modified: POMs under tests/<module>/pages/, fixture at tests/<module>/fixtures/<module>.fixture.ts, spec(s) at tests/<module>/<feature>.spec.ts.
  • TypeScript verification: Last ~15 lines of tsc --noEmit --pretty false output (must be clean).
  • Test run result: Passed/Failed/Skipped counts.
  • Artifacts: HTML report and trace files in test-results/ and playwright-report/ (open via npm run test:e2e:report).
  • Rule compliance: Any deviations from the four rules noted explicitly.

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

  1. 26d ago Changed · -52 lines 1eaecc190110
  2. 1mo ago First seen · 106 lines · 10 tokens per session scan A 3fec3c1189d3

Subscribe to this mod's changes

e2e is a command published in the GitHub repository fmflurry/settings-opencode (171 stars, last pushed yesterday), licensed MIT. It adds 10 tokens to every session and 595 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to e2e, differing in 114 lines, and is treated as a copy.