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.
curl -O https://raw.githubusercontent.com/RegardV/LegendaryTeam_For_Claude/main/.claude/commands/e2e.mdgit clone --depth 1 https://github.com/RegardV/LegendaryTeam_For_ClaudeWrote 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/commands/regardv/legendaryteam_for_claude/e2e)<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>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.00000 | $0.02201 |
| Opus 5 | $0.00000 | $0.01100 |
| Sonnet 5 | $0.00000 | $0.00440 |
| Haiku 4.5 | $0.00000 | $0.00220 |
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.
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
- Analyzes the requested user flow or feature
- Generates Playwright E2E test with proper selectors
- Creates test file in
e2e/directory - Runs the test to verify it works
- 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');
});
});
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.
- 8d ago First seen · 358 lines · 0 tokens per session scan A 7ac211a053c7
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.
Other commands, from other repositories
rooms-test
Self-test DorkOS rooms in a live browser — two agents in one channel, driven through bursts, mid-turn steering, halt, reactions, threads, and the three-way DM rule, cross-checked against the API and SQLite. Logs an evidence-based findings report.
self-test
Self-test the DorkOS chat UI in a live browser session — drives real interactions, monitors JSONL transcript, compares API vs UI, researches issues, and produces an evidence-based findings report.
session-switch-test
Self-test switching between two concurrently-working DorkOS chat sessions in a live browser — drives real interactions, watches both JSONL transcripts, and asserts that streaming, subagents, queued messages, todos, and permission prompts survive session switches. Logs an evidence-based findings report.
browsertest
Run, create, debug, and maintain browser tests.
maintain
Audit browser test suite health and fix stale tests.
dark-factory-behavioral-e2e
Holdout-pattern E2E validator. Drives agent-browser against the running DynaChat app to verify that the PR's user-facing behavior actually matches what the linked issue asked for.