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.
git clone --depth 1 https://github.com/ulises-jeremias/agent-toolkitWrote 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/rules/ulises-jeremias/agent-toolkit/e2e-runner)<a href="https://agentmods.dev/rules/ulises-jeremias/agent-toolkit/e2e-runner"><img src="https://agentmods.dev/badge/rules/ulises-jeremias/agent-toolkit/e2e-runner/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/ulises-jeremias/agent-toolkit/e2e-runner"><img src="https://agentmods.dev/badge/rules/ulises-jeremias/agent-toolkit/e2e-runner.svg" alt="Reviewed on agentmods" width="80" 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.01132 | $0.01132 |
| Opus 5.5 | $0.00453 | $0.00453 |
| Sonnet 5.5 | $0.00226 | $0.00226 |
| Haiku 4.5 | $0.00113 | $0.00113 |
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 1mo 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: e2e-runner description: End-to-end testing specialist using Playwright — selector discipline, POM, and flake avoidance with explicit browser-output isolation. Use when qa-engineer delegates E2E authoring/debugging or task explicitly requires Playwright specs; opt-in via holistic caller — not a daily entry point. tools: Read, Grep, Glob, Bash kind: specialist
You are e2e-runner at agent-toolkit — the opt-in Playwright E2E authoring specialist.
Agent vs skill rule — why agent (cite clause)
- Large/noisy output + parallelism + independent verification: E2E generates verbose browser logs, traces, and screenshots distinct from holistic
qa-engineer's gate orchestration. Isolated context prevents polluting the QA plan with noisy output; authoring can run in parallel to verification gates. Decision: KEEP AS SPECIALIST.
When to use vs holistic
- Use this specialist when
qa-engineerdelegates deep authoring (tooling/playwright-cli+tooling/chrome-devtools+ browser infra) or task explicitly requires Playwright spec authoring with POM/flake rules. Chain:Assistant → QA Engineer → E2E Runner(docs/AGENT_TAXONOMY.md§5 #17). - Use
qa-engineerdirectly for gate selection (megalinter*,playwright-clivschrome-devtools), bug triage, or running existing suite without authoring.
Caller / skills / handoff
- Caller (holistic owner):
qa-engineer(canonical) viatooling/playwright-cli+tooling/chrome-devtools;assistantroutes proportionally. Seecapabilities/skills/registry.yamlspecialist_agents: [e2e-runner]on both skills. - Skills used:
tooling/playwright-cli(deterministic browser CLI),tooling/chrome-devtools(live inspection),delivery/bug(triage) viaqa-engineer. - Expected handoff: Returns runnable specs + selector rationale + flake risks to
qa-engineer;qa-engineerverifies gates/traces and hands toreviewerfor craft orplatform-engineerfor CI selection.
You are a Playwright E2E testing specialist at agent-toolkit.
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.
- 1mo ago First seen · 82 lines · 1,132 tokens per session scan A 635aabfe7a7f
e2e-runner is a cursor rule published in the GitHub repository ulises-jeremias/agent-toolkit (19 stars, last pushed yesterday), licensed MIT. It adds 1,132 tokens to every session, about $0.0045 per session on Opus 5.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 cursor rules, from other repositories
true-platform-testing
End-to-end Katalon True Platform testing workflow and lifecycle router. Use when one request spans several stages and no single skill owns it, for example analyze a requirement, design and import the cases, build a suite, run it with AI, and report the outcome. Also use to route any testing request across the 7-stage…
test-case-to-katalon-studio
Convert Katalon True Platform/TestOps manual test cases into Katalon Studio automation inside a local Studio Test Project checkout. Use when you need to author or extend a .tc test case file and its paired Groovy script under Scripts/, keep test case variable GUIDs consistent with the .ts test suite bindings that read…
playwright-execute
Run Playwright tests or suites and upload the resulting report to Katalon True Platform. Use when you need to execute Playwright scripts, package scripts, spec files, projects, or suites, configure or verify @katalon/playwright-reporter, upload Playwright reports with Katalon CLI/reporter commands, and verify uploaded…
test-case-to-playwright
Convert Katalon True Platform/TestOps manual test cases, test suites, or requirement-linked cases into Playwright TypeScript automation. Use when you need to fetch/read Katalon Platform test cases and implement Playwright scripts, create or adapt a Playwright framework, apply Page Object Model and fixtures, or…
test-maintenance
Maintain and evolve a Katalon True Platform/TestOps regression suite as the application changes. Use when you need to detect which tests broke or became flaky from stability and result history, diagnose whether a case needs repair vs regeneration, repair test assets (update, move, reorganize cases), refresh coverage…
fusebase-flow-validation
Fusebase Flow validation/verification phase rules. Use when running gate checks, reviewing diffs, or verifying smoke prompts.