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.
npx agentmods add commands/mckruz/claude-code-mastery/e2egit clone --depth 1 https://github.com/MCKRUZ/claude-code-masteryWhat 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 | $0.00029 | $0.00822 |
| Opus 5 | $0.00015 | $0.00411 |
| Sonnet 5 | $0.00006 | $0.00164 |
| Haiku 4.5 | $0.00003 | $0.00082 |
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 2d 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
E2E Command
Generate, maintain, and execute end-to-end tests using Playwright.
Workflow
- Generate Test Journeys - Create Playwright tests for user flows
- Run E2E Tests - Execute tests across browsers
- Capture Artifacts - Screenshots, videos, traces on failures
- Generate Report - HTML reports and JUnit XML
- Identify Flaky Tests - Quarantine unstable tests
When to Use
Use /e2e when:
- Testing critical user journeys (login, trading, payments)
- Verifying multi-step flows work end-to-end
- Testing UI interactions and navigation
- Validating integration between frontend and backend
- Preparing for production deployment
Process
- Analyze user flow and identify test scenarios
- Generate Playwright test using Page Object Model pattern
- Run tests across multiple browsers (Chrome, Firefox, Safari)
- Capture failures with screenshots, videos, and traces
- Generate report with results and artifacts
- Identify flaky tests and recommend fixes
Test Artifacts
On All Tests:
- HTML Report with timeline and results
- JUnit XML for CI integration
On Failure Only:
- Screenshot of the failing state
- Video recording of the test
- Trace file for debugging (step-by-step replay)
- Network logs
- Console logs
Flaky Test Detection
If a test fails intermittently:
- Report the pass rate (e.g., 7/10 runs)
- Identify common failure cause (timeout, race condition, animation)
- Recommend fix (explicit wait, increased timeout, race condition fix)
- Suggest quarantine with
test.fixme()until fixed
Browser Configuration
Tests run on multiple browsers by default:
- Chromium (Desktop Chrome)
- Firefox (Desktop)
- WebKit (Desktop Safari)
- Mobile Chrome (optional)
Configure in playwright.config.ts to adjust browsers.
Best Practices
DO:
- Use Page Object Model for maintainability
- Use
data-testidattributes for selectors - Wait for API responses, not arbitrary timeouts
- Test critical user journeys end-to-end
- Run tests before merging to main
- Review artifacts when tests fail
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.
- 2d ago First seen · 131 lines · 29 tokens per session scan A cace8a638f41
/e2e is a command published in the GitHub repository MCKRUZ/claude-code-mastery (11 stars, last pushed 4mo ago), licensed MIT. It adds 29 tokens to every session and 822 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-30.
Other commands, from other repositories
claude-md-migrate
Rewrite a bloated or stale CLAUDE.md into a lean, verified "map, not wishes" file — nothing invented, hard rules preserved verbatim.
claude-md-new
Scaffold a CLAUDE.md for this repo from battle-tested templates, filled in with the project's real commands.
claude-md-audit
Grade this repo's CLAUDE.md / AGENTS.md (0–100) and return a worst-first fix list.
review
请从风险、回归、测试遗漏和可读性四个角度 review 当前变更。.
explain
请解释当前文件或目录的核心结构，并指出我下一步应该看哪里。.
fix
请先定位根因，再给出最小修改方案，最后说明验证方式。.