LegendaryTeam_For_Claude: Command for Claude Code

.claude/commands/e2e.md

e2e is a command for Claude Code from RegardV/LegendaryTeam_For_Claude. It costs 0 tokens per session (2,201 once invoked), scanned A, original, MIT.

A command that creates and runs Playwright end-to-end tests. End-to-end tests check a complete user journey through an application, such as logging in or completing a purchase.

In plain words
What is it for?
Use it to generate tests for user flows and pages, run all existing tests or one test file, and verify interactions such as login, dashboards, profiles, and checkout.
Why use it?
It turns a described workflow into test steps, runs those steps, and reports failures with screenshots or videos.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is RegardV/LegendaryTeam_For_Claude's own configuration. It tells Claude Code how to work on LegendaryTeam_For_Claude itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything LegendaryTeam_For_Claude configures →

Reuse

Borrowing it

Nothing to install: this file belongs to RegardV/LegendaryTeam_For_Claude. 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/RegardV/LegendaryTeam_For_Claude/main/.claude/commands/e2e.md
Clone the repo
git clone --depth 1 https://github.com/RegardV/LegendaryTeam_For_Claude

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/regardv/legendaryteam_for_claude/e2e.svg)](https://agentmods.dev/commands/regardv/legendaryteam_for_claude/e2e)
Your own site
<a href="https://agentmods.dev/commands/regardv/legendaryteam_for_claude/e2e"><img src="https://agentmods.dev/badge/commands/regardv/legendaryteam_for_claude/e2e.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,201 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.02201
Opus 5 $0.00000 $0.01100
Sonnet 5 $0.00000 $0.00440
Haiku 4.5 $0.00000 $0.00220

Measured 8d ago against content hash 7ac211a053c7, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, 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 8d 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/e2e.md · 358 lines

How it starts

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

/e2e - E2E Test Generation & Execution

Generate and execute end-to-end tests for user workflows using Playwright.


Usage

# Generate E2E test for a user flow
/e2e "user can login and view dashboard"

# Generate E2E test with specific steps
/e2e "checkout flow: add item to cart, proceed to checkout, complete payment"

# Run existing E2E tests
/e2e run

# Run specific E2E test file
/e2e run auth/login.spec.ts

# Generate test for specific page/component
/e2e "test profile page with all user interactions"

What This Command Does

  1. Analyzes the requested user flow or feature
  2. Generates Playwright E2E test with proper selectors
  3. Creates test file in e2e/ directory
  4. Runs the test to verify it works
  5. Reports results with screenshots on failure

Command Flow

Step 1: Parse user request
  → Identify user flow/journey
  → Break down into testable steps

Step 2: Generate test
  → Create Playwright test file
  → Use proper selectors (data-testid preferred)
  → Add proper waits and assertions

Step 3: Execute test
  → Run Playwright test
  → Capture screenshots/videos on failure
  → Report results

Step 4: Integrate
  → Add test to test suite
  → Update CI/CD if needed

Invokes Agent

@E2ERunner will handle this command with the following context:

Task: Generate E2E test for user workflow
Description: ${user_input}

Requirements:
1. Create Playwright test file
2. Use proper selectors (prefer data-testid)
3. Include proper waits and assertions
4. Handle errors and edge cases
5. Run test to verify it works
6. Provide test report with results

Output:
- Test file path
- Test execution results
- Screenshots on failure
- Recommendations for improvement

Example: Login Flow

Input:

/e2e "user can login with email and password"

Generated Test (e2e/auth/login.spec.ts):

import { test, expect } from '@playwright/test';

test.describe('User Login', () => {
  test('should login with valid credentials', async ({ page }) => {
    // Navigate to login page
    await page.goto('/login');

    // Fill login form
    await page.fill('[data-testid="email-input"]', '[email protected]');
    await page.fill('[data-testid="password-input"]', 'password123');

    // Submit form
    await page.click('[data-testid="login-button"]');

    // Verify redirect to dashboard
    await expect(page).toHaveURL(/\/dashboard/);
    await expect(page.locator('[data-testid="user-menu"]')).toBeVisible();
  });

  test('should show error for invalid credentials', async ({ page }) => {
    await page.goto('/login');

    await page.fill('[data-testid="email-input"]', '[email protected]');
    await page.fill('[data-testid="password-input"]', 'wrongpassword');

    await page.click('[data-testid="login-button"]');

    // Verify error message
    await expect(page.locator('[data-testid="error-message"]')).toContainText('Invalid credentials');
  });
});

Read the full file on GitHub · 358 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. 8d ago First seen · 358 lines · 0 tokens per session scan A 7ac211a053c7

Subscribe to this mod's changes

e2e is a command published in the GitHub repository RegardV/LegendaryTeam_For_Claude (19 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,201 tokens. 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.