Borrowing it
Nothing to install: this file belongs to Piyush8296/claude-workspace. 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/Piyush8296/claude-workspace/main/.claude/commands/e2e.mdgit clone --depth 1 https://github.com/Piyush8296/claude-workspaceWrote 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/piyush8296/claude-workspace/e2e)<a href="https://agentmods.dev/commands/piyush8296/claude-workspace/e2e"><img src="https://agentmods.dev/badge/commands/piyush8296/claude-workspace/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.00013 | $0.00723 |
| Opus 5 | $0.00006 | $0.00362 |
| Sonnet 5 | $0.00003 | $0.00145 |
| Haiku 4.5 | $0.00001 | $0.00072 |
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 6d 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
E2E Test Generator
Generate E2E test for: $ARGUMENTS
Instructions
1. Understand the user flow
Break the description into discrete steps:
- Where does the user start? (URL/page)
- What actions do they take? (click, type, navigate)
- What do they expect to see? (text, elements, redirects)
- What's the success criteria?
2. Check Playwright setup
# Verify Playwright is available
npx playwright --version 2>/dev/null || echo "Playwright not installed"
# Check for existing config
ls playwright.config.* 2>/dev/null || echo "No Playwright config found"
# Check for existing E2E tests
find . -path '*/e2e/*.spec.*' -o -path '*/e2e/*.test.*' 2>/dev/null | head -5
If Playwright isn't set up, create a basic config:
// playwright.config.ts
import { defineConfig } from '@playwright/test';
export default defineConfig({
testDir: './tests/e2e',
baseURL: 'http://localhost:3000',
use: {
trace: 'on-first-retry',
screenshot: 'only-on-failure',
},
webServer: {
command: 'pnpm dev',
port: 3000,
reuseExistingServer: true,
},
});
3. Generate the test
Follow these patterns:
import { test, expect } from '@playwright/test';
test.describe('User Flow: <description>', () => {
test('should complete the flow successfully', async ({ page }) => {
// Navigate
await page.goto('/<start-page>');
// Act
await page.getByRole('button', { name: /sign in/i }).click();
await page.getByLabel('Email').fill('[email protected]');
await page.getByLabel('Password').fill('password123');
await page.getByRole('button', { name: /submit/i }).click();
// Assert
await expect(page.getByRole('heading', { name: /dashboard/i })).toBeVisible();
});
test('should handle error state', async ({ page }) => {
// Test the unhappy path
});
});
Selector priority:
getByRole— accessible selectors firstgetByLabel— form inputsgetByText— visible contentgetByTestId— last resort
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.
- 6d ago First seen · 109 lines · 13 tokens per session scan A a72bd7d45b6c
e2e is a command published in the GitHub repository Piyush8296/claude-workspace (2 stars, last pushed 4mo ago), licensed MIT. It adds 13 tokens to every session and 723 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-31.
Other commands, from other repositories
test-suite
Run comprehensive test suite with coverage analysis.
qa
Dispatch a verifiable browser task to the qa-tester subagent. Use for regression checks, smoke tests, and any task with a clean pass/fail outcome. Supports an EXHAUSTIVE mode that verifies every control behind an honesty gate.
svelte:test-fix
Troubleshoot and fix failing tests in Svelte/SvelteKit projects, including debugging test issues and resolving common testing problems.
svelte:test-setup
Set up comprehensive testing infrastructure for Svelte/SvelteKit projects, including unit testing, component testing, and E2E testing frameworks.
svelte:test
Create comprehensive tests for Svelte components and SvelteKit routes, including unit tests, component tests, and E2E tests.
gsd:verify-work
Validate built features through conversational UAT.