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 rules/systemowiec/ai-agents-workspace-starter/role-e2egit clone --depth 1 https://github.com/systemowiec/ai-agents-workspace-starterWrote 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/systemowiec/ai-agents-workspace-starter/role-e2e)<a href="https://agentmods.dev/rules/systemowiec/ai-agents-workspace-starter/role-e2e"><img src="https://agentmods.dev/badge/rules/systemowiec/ai-agents-workspace-starter/role-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 | $0.00000 | $0.00245 |
| Opus 5 | $0.00000 | $0.00122 |
| Sonnet 5 | $0.00000 | $0.00049 |
| Haiku 4.5 | $0.00000 | $0.00024 |
Grade A, and why
role-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 4d 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
Role: E2E Test Engineer
Read and apply strictly:
- Project rules: @AGENTS.md
- Role definition: @.agents/roles/e2e-engineer.md
- Skill: @.agents/skills/write-e2e-tests/SKILL.md
- Workflow: @.agents/workflows/as-e2e-engineer.md
Key Principles
- Page Object Model - every page has a POM
- Selectors:
data-testid, never CSS classes - Data seeding: via API, never via UI
- Auth: storageState, login once
- No
waitForTimeout- use smart waits - Docker First:
make e2e, never locally - Determinism: test must pass 3 times in a row
DO NOT TOUCH: backend/app/, frontend/src/, infra/backend/
When done: report in docs/specs/{layer}/{PREFIX}-NNN/impl-e2e-engineer.md
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.
- 4d ago First seen · 27 lines · 0 tokens per session scan A 8cd3858c57cd
role-e2e is a cursor rule published in the GitHub repository systemowiec/ai-agents-workspace-starter (2 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 245 tokens. 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 cursor rules, from other repositories
maestro-device-selection
Maestro tests can run on either iPhone or iPad simulators based on tags in the test YAML files. This allows you to test iPad-specific UI layouts and features while maintaining a single test suite.
tester
Tester role - Unit, E2E, and visual regression testing.
xiigen-user-journey-testing
Validate work through a realistic user path. Use for UX, tool workflows, onboarding, and generated instructions.
vasu-playwright-utils
../../templates/cursor-rules/vasu-playwright-utils.mdc.
qa-script-executor
QA Script Executor - Executes natural language test scripts using Chrome DevTools MCP and enhances them with technical hints.
puppeteer
This guide provides opinionated, actionable best practices for writing robust, performant, and maintainable Puppeteer scripts for web scraping, automation, and testing. It emphasizes modern patterns like page.locator() and efficient resource management.