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/nerds-odd-e/doughnut/e2e-authoringgit clone --depth 1 https://github.com/nerds-odd-e/doughnutWhat 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.02726 |
| Opus 5 | $0.00000 | $0.01363 |
| Sonnet 5 | $0.00000 | $0.00545 |
| Haiku 4.5 | $0.00000 | $0.00273 |
Grade A, and why
e2e-authoring 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 — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.
E2E Authoring Rules
Use this rule when writing or modifying E2E tests, Cypress/Cucumber feature files, step definitions, page objects, or E2E assertions. For OCR-specific canvas assertions, use e2e-ocr.mdc.
Environment Assumption
Assume the developer has already started services with pnpm sut, including backend auto-reload, frontend HMR, and Mountebank. Services automatically restart when code changes are made.
If services are not running, suggest starting pnpm sut in a separate terminal.
Cypress Origin
http://localhost:5173 is always the Cypress app origin through the local load balancer. CI vs pnpm sut, wait-on, NO_PROXY, and env vars are documented in docs/gcp/prod_env.md, Local dev / Cypress under section 6.
Run E2E Tests
Agents should default to pnpm cypress run --spec with one or more .feature paths tied to the changed capability. Add adjacent specs only when regression risk warrants it. Do not run bare pnpm cypress run, pnpm verify, or the whole suite unless the user explicitly asks for a full E2E run or the instructions require reproducing CI.
CURSOR_DEV=true nix develop -c pnpm cypress run --spec e2e_test/features/ai_generated_recall_questions/question_contest.feature
Important notes:
- Do not use
cypress run -- --spec; the empty--causes the--specparameter to be ignored. - The default tag filter is
expose.tagsine2e_test/config/ci.ts, for examplenot @ignore. Override per run with--expose tags='...'(-x), not--env tags=...(ignored by@badeball/cypress-cucumber-preprocessorv27 on Cypress >= 15.17). @skipOptimizationDueToKnownNecessarySlownesson a Scenario or Feature marks known-necessary slowness. Test-optimization profiles exclude it with--expose tags='not @ignore and not @skipOptimizationDueToKnownNecessarySlowness'. Normal CI/dev runs still execute these scenarios. Do not add this tag without developer review.@focusand@onlyare local debugging aids only. Do not commit them; CI runs./scripts/check_focus_tags.shon.featurefiles to block@focus, and@onlyshould be treated the same.- If any node in a feature file is tagged
@focusor@only,@badeball/cypress-cucumber-preprocessorfilters scenarios in that file to@focus or @onlyonly.
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 · 228 lines · 0 tokens per session scan A d55f5058345a
e2e-authoring is a cursor rule published in the GitHub repository nerds-odd-e/doughnut (49 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,726 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
e2e_playwright
We use playwright with pytest to e2e test Streamlit library. E2E tests verify the complete Streamlit system (frontend, backend, communication, state, visual appearance) from a user's perspective (black-box). They complement Python/JS unit tests, which are faster and focus on internal logic, input/output validation…
playwright-e2e
Playwright E2E testing configuration for AI agents.
playwright
在制定规范前，需明确 Playwright 测试失败的三大核心根因。编写"高成功率"测试的本质，就是通过规范消除这三个变量：.
dev-browser
Fallback browser automation with persistent Chrome state. Use only when Browser Use is unavailable or blocked.
security-standards
Cursor rule "security-standards" from wjgogogo/cursor-rules, covering 安全规范, 核心原则 [p0], 输入验证, xss 防护 and csrf 防护.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.