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/thedecipherist/claude-code-mastery-project-starter-kit/create-e2egit clone --depth 1 https://github.com/TheDecipherist/claude-code-mastery-project-starter-kitWhat 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.00012 | $0.01762 |
| Opus 5 | $0.00006 | $0.00881 |
| Sonnet 5 | $0.00002 | $0.00352 |
| Haiku 4.5 | $0.00001 | $0.00176 |
Grade A, and why
create-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 — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create E2E Test
Create a Playwright E2E test for: $ARGUMENTS
ABSOLUTE RULES — Read Before Writing a Single Line
1. Every test MUST have explicit success criteria
"Page loads" is NOT a test. Every test() block MUST assert:
- URL — verify the page navigated to the correct URL
- Visible elements — verify key elements are present and visible
- Correct data — verify the right content is displayed
- Error states — verify error messages show when expected
// CORRECT — explicit success criteria
test('dashboard shows user data after login', async ({ page }) => {
await page.goto('/login');
await page.fill('[name="email"]', '[email protected]');
await page.fill('[name="password"]', 'password123');
await page.click('button[type="submit"]');
// ✅ Verify URL changed
await expect(page).toHaveURL('/dashboard');
// ✅ Verify key element visible
await expect(page.locator('h1')).toContainText('Welcome');
// ✅ Verify correct data displayed
await expect(page.locator('[data-testid="user-email"]')).toContainText('[email protected]');
// ✅ Verify sidebar loaded
await expect(page.locator('nav.sidebar')).toBeVisible();
});
// WRONG — this passes even when completely broken
test('dashboard loads', async ({ page }) => {
await page.goto('/dashboard');
// no assertions!
});
2. A test is FINISHED when it has ALL of these
A test is NOT done until it has:
- At least one
await expect(page).toHaveURL()assertion - At least one
await expect(locator).toBeVisible()assertion - At least one content/data verification (
toContainText,toHaveValue, etc.) - Error case coverage (what happens when it fails?)
- No
// TODOor placeholder assertions
If you cannot check ALL of these, the test is incomplete. Say so and explain what's missing.
3. Test structure — ALWAYS follow this pattern
import { test, expect } from '@playwright/test';
test.describe('[Feature Name]', () => {
test.describe('happy path', () => {
test('should [specific behavior] when [specific condition]', async ({ page }) => {
// ARRANGE — navigate, set up state
// ACT — perform the user action
// ASSERT — verify SPECIFIC outcomes (URL, elements, data)
});
});
test.describe('error handling', () => {
test('should show error when [invalid input]', async ({ page }) => {
// Test the failure mode
});
});
test.describe('edge cases', () => {
test('should handle [empty state / max values / etc]', async ({ page }) => {
// Test boundaries
});
});
});
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 · 231 lines · 12 tokens per session scan A b5776699a27f
create-e2e is a command published in the GitHub repository TheDecipherist/claude-code-mastery-project-starter-kit (337 stars, last pushed 2mo ago), licensed MIT. It adds 12 tokens to every session and 1,762 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
qawolf-cli
Manage QA Wolf through the qawolf CLI. Use when asked to create, update, or list coverage requests, bug reports, or maintenance reports; start a run of flows or tags on the QA Wolf platform or read a run's results; list, set, or delete environment variables; manage environments, flows, or tags; request automation of…
expect
Diff-aware AI browser testing — reads the git diff, maps changes to affected pages via the route map, generates a targeted test plan, and executes it via agent-browser (Rust daemon + CDP, ARIA-tree-first) with pass/fail reporting. Use when testing UI changes, verifying PRs before merge, or running regression checks on…
test
Run the app's microflow tests and verify it in the browser.
live-verify
Two-part gate for gflow-cli feature work — pre-flight state check at the start, live-verification against real Flow before claiming done.
buildable-preview
Render the running prototype in a headless browser, screenshot it, and catch runtime/visual errors.
speckit.product-forge.test-run
Phase 8B: Executes test cases via playwright-cli (interactive browser agent), tracks bugs in bugs/ .md, auto-fixes P0/P1 bugs and retests, performs gap analysis when bugs require spec changes. Loop continues until all P0/P1 bugs closed and exit criteria met. Use with: "run tests", "execute tests"…