Borrowing it
Nothing to install: this file belongs to nerds-odd-e/doughnut. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/nerds-odd-e/doughnut/main/.agents/skills/e2e-authoring/SKILL.mdgit clone --depth 1 https://github.com/nerds-odd-e/doughnutWrote 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/skills/nerds-odd-e/doughnut/e2e-authoring)<a href="https://agentmods.dev/skills/nerds-odd-e/doughnut/e2e-authoring"><img src="https://agentmods.dev/badge/skills/nerds-odd-e/doughnut/e2e-authoring/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/skills/nerds-odd-e/doughnut/e2e-authoring"><img src="https://agentmods.dev/badge/skills/nerds-odd-e/doughnut/e2e-authoring.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.00057 | $0.03343 |
| Opus 5.5 | $0.00023 | $0.01337 |
| Sonnet 5.5 | $0.00011 | $0.00669 |
| Haiku 4.5 | $0.00006 | $0.00334 |
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 10d 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 — 260 lines — stays where its author put it; the contents beside it link to each section on GitHub.
E2E Authoring Rules
Use this skill when writing or modifying E2E tests, Cypress/Cucumber feature files, step definitions, page objects, or E2E assertions. For OCR-specific canvas assertions, use the e2e-ocr skill.
Environment Assumption
The pnpm cy:run wrapper owns its stack and compiles current backend source once per batch, without a continuous backend compiler. Local batches retain frontend HMR; backend edits need a new invocation. Use pnpm cy:open for an interactive session with backend reload and frontend HMR. Required mocks are owned by the selected invocation.
If services are not running, suggest running pnpm cy:run --spec <feature> in a separate terminal.
Cypress Origin
Primary unconfigured checkouts and CI use http://localhost:5173 as the Cypress
app origin through the local load balancer. A linked worktree (or a primary
with .worktree.local.json) uses that checkout's isolated origin
http://127.0.0.1:<lbListenPort> — see docs/worktree-browser-tests.md. Isolated
Cypress accepts one or more selections from the assessed active feature set
declared in scripts/isolated-cypress-spec-selection.mjs (application-only
active specs plus the active CLI, MCP, OpenAI-mock, and Wikidata-mock focused
specs) per run; a new feature file must be added to that set (e.g.
APPLICATION_ONLY_ACTIVE_SPECS in scripts/isolated-cypress-active-specs.mjs) before an
isolated run accepts it. The CLI command is scoped to the assessed active CLI workflows.
The MCP command is scoped to that one search/graph feature. OpenAI-mock specs
start a runner-owned private OpenAI Mountebank; Wikidata-mock specs start a
runner-owned private Wikidata Mountebank; application-only, CLI, and MCP specs
do not require Mountebank. Each isolated checkout needs its own healthy E2E
allocation. Paired CLI-vs-browser reset proof:
CURSOR_DEV=true nix develop -c node scripts/worktree-reset-isolation-harness.mjs --mode cli --peer <cli-checkout> --resetter <browser-checkout>
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago Changed bd3775431981
- 29d ago Changed · +2 lines a3a2a1f0b8e4
- 1mo ago Changed · +5 lines 6cd1bfd66d44
- 1mo ago Changed · +7 lines abc8b1535e6d
- 1mo ago Changed · -24 lines 1d706a57923f
- 1mo ago First seen · 270 lines · 57 tokens per session scan A 701a94e6352b
e2e-authoring is a skill published in the GitHub repository nerds-odd-e/doughnut (50 stars, last pushed today), licensed MIT. It adds 57 tokens to every session and 3,343 once invoked, about $0.0002 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-09-17.
Other skills, from other repositories
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…
eval-dataset-design
A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
test-warp-ui
Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.