Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/eliornl/rolemulenpx agentmods add rules/eliornl/rolemule/e2e-testingWrote 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/eliornl/rolemule/e2e-testing)<a href="https://agentmods.dev/rules/eliornl/rolemule/e2e-testing"><img src="https://agentmods.dev/badge/rules/eliornl/rolemule/e2e-testing/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/eliornl/rolemule/e2e-testing"><img src="https://agentmods.dev/badge/rules/eliornl/rolemule/e2e-testing.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.00000 | $0.03522 |
| Opus 5.5 | $0.00000 | $0.01409 |
| Sonnet 5.5 | $0.00000 | $0.00704 |
| Haiku 4.5 | $0.00000 | $0.00352 |
Grade A, and why
e2e-testing 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 — 352 lines — stays where its author put it; the contents beside it link to each section on GitHub.
E2E Testing Patterns (Playwright)
Test Suite Overview
Tests are split into two tiers based on whether they require a live server.
Tier 1 — Mocked, CI-safe (no server needed)
| File | Covers |
|---|---|
dashboard-pages.spec.ts |
All dashboard tabs, navbar, settings, career tools, sub-tabs |
landing.spec.ts |
All landing sections, navbar, CTAs, footer, a11y, cookie consent |
auth-pages.spec.ts |
Login/register/forgot/reset/verify form structure + validation |
interview-prep.spec.ts |
All states, 4 question sub-tabs, generate/complete/mobile |
profile-setup.spec.ts |
Profile setup (resume + 5 steps: basic → work → education → skills → prefs), field validation, navigation |
application-detail.spec.ts |
10 tabs (Optimize CV + Mock Session + Outreach), sub-tabs, cover letter, company, mobile layout |
onboarding.spec.ts |
Auto-show/suppress, step nav, skip, complete, window.Onboarding API, a11y |
complete-coverage.spec.ts |
Authenticated page coverage: dashboard, settings, career tools, history |
security.spec.ts |
XSS, JWT format, API headers, content security (all mocked) |
extension.spec.ts |
Manifest V3, content script, service worker, popup JS |
error-handling.spec.ts |
401/403/429/500 + mocked network errors, form validation |
smoke.spec.ts |
Critical path (~46 @smoke tests) — this is what CI runs (e2e-smoke in .github/workflows/ci.yml) |
workflow-mocked.spec.ts |
Workflow processing/complete/error states (mocked) |
api-validation.spec.ts |
API response shapes: full/partial/null fields, error bodies, auth tokens |
form-edge-cases.spec.ts |
Unicode, boundary values, special characters, XSS |
auth-complete.spec.ts |
Google OAuth (mocked), email verification, account lockout |
dashboard.spec.ts |
Dashboard nav, mocked settings, tools, history navigation |
journey.spec.ts |
Multi-step user journeys: new app → results, career tools flow, auth redirect |
keyboard-nav.spec.ts |
Tab/Enter/Space/Escape/Backspace/ArrowDown across all pages |
visual-regression.spec.ts |
Page structure verification at desktop/tablet/mobile viewports |
performance.spec.ts |
Page load assertions (mocked) |
accessibility.spec.ts |
ARIA, landmarks, heading hierarchy |
rate-limit.spec.ts |
429 + Retry-After handling: login, registration, career tools, workflow |
file-upload.spec.ts |
Resume/job upload, fixture files, API mock responses, error handling |
websocket.spec.ts |
Workflow processing/failed states, progress polling, network resilience |
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 · 352 lines · 0 tokens per session scan A d3f66e93e008
e2e-testing is a cursor rule published in the GitHub repository eliornl/rolemule (38 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,522 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-30.
Other cursor rules, from other repositories
ai-gateway-smoke-mandatory
AI Gateway / trafficevent changes require an ai-gateway smoke run before "done".
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.