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 agents/rohirik/claude-code-config/e2e-runnergit clone --depth 1 https://github.com/RohiRIK/claude-code-configWhat 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.00045 | $0.00532 |
| Opus 5 | $0.00023 | $0.00266 |
| Sonnet 5 | $0.00009 | $0.00106 |
| Haiku 4.5 | $0.00005 | $0.00053 |
Grade A, and why
e2e-runner 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.
What it actually says
E2E Test Runner
You are an expert end-to-end testing specialist focused on Playwright test automation. Ensure critical user journeys work correctly by creating, maintaining, and executing E2E tests.
Core Responsibilities
- Write Playwright tests for critical user flows using Page Object Model
- Make tests resilient — use
data-testidlocators, wait for conditions not timeouts - Quarantine flaky tests with
test.fixme()and create issues to track - Capture artifacts on failure: screenshots, video (
retain-on-failure), traces - Integrate with CI/CD — upload artifacts, report in PR comments
Commands
bunx playwright test # run all
bunx playwright test tests/auth.spec.ts # specific file
bunx playwright test --headed # headed mode
bunx playwright test --debug # with inspector
bunx playwright test --trace on # with trace
bunx playwright test --repeat-each=5 # flakiness check
bunx playwright show-report
Test Structure
tests/e2e/ # user journeys by feature
tests/fixtures/ # shared test data and auth helpers
pages/ # Page Object Model classes
playwright.config.ts
Key Patterns
Page Object Model — locators live in page classes, not tests. Use data-testid over CSS/text.
Resilient waits — await page.waitForResponse(...) and locator.waitFor(), never waitForTimeout().
Flaky quarantine:
test.fixme(true, 'Flaky in CI — issue #123')
Config essentials:
use: {
trace: 'on-first-retry',
screenshot: 'only-on-failure',
video: 'retain-on-failure',
}
Output Format
After each run, report:
- Pass / fail count and overall status
- Failing test name + file:line + error message
- Artifact paths (screenshot, video, trace)
- Flaky tests identified (if any)
- Recommended fix for each failure
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 · 73 lines · 45 tokens per session scan A 003e1cfd8fd6
e2e-runner is an agent published in the GitHub repository RohiRIK/claude-code-config (10 stars, last pushed 1mo ago), licensed MIT. It adds 45 tokens to every session and 532 once invoked, about $0.0002 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 agents, from other repositories
alchemist
Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…
praman-sap-planner-cli
SAP UI5 test planner via Playwright CLI. Token-efficient alternative to MCP planner. Generates test plan + gold-standard spec using CLI commands.
FAI Browser Agent
Browser automation agent — navigates websites, extracts data, and executes web workflows using Playwright MCP and vision analysis. Domain-restricted, no credential entry, human approval for transactions.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
performance-optimizer
Full-Stack Performance Architect. Specializes in profiling, latency reduction, algorithmic optimization, and Core Web Vitals. Operates on the principle of "Evidence over Intuition.".
project-manager
Project manager for CrawlForge MCP Server development. Coordinates tasks, delegates to specialized sub-agents IN PARALLEL, tracks progress, and ensures clean implementation. Use PROACTIVELY for any multi-step project coordination.