Borrowing it
Nothing to install: this file belongs to BloomBooks/BloomDesktop. 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/BloomBooks/BloomDesktop/master/.github/skills/add-e2e-test/SKILL.mdgit clone --depth 1 https://github.com/BloomBooks/BloomDesktopWrote 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/bloombooks/bloomdesktop/add-e2e-test)<a href="https://agentmods.dev/skills/bloombooks/bloomdesktop/add-e2e-test"><img src="https://agentmods.dev/badge/skills/bloombooks/bloomdesktop/add-e2e-test.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.1 | $0.00089 | $0.08310 |
| Opus 5 | $0.00044 | $0.04155 |
| Sonnet 5 | $0.00018 | $0.01662 |
| Haiku 4.5 | $0.00009 | $0.00831 |
Grade A, and why
add-e2e-test 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 today.
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 — 521 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add an edge-to-edge test
What an e2e test is here
An e2e test launches its own Bloom.exe on a known collection, drives the real UI in
the embedded WebView2, asserts, and tears the instance down. You can run a single test
locally; wiring the suite into the nightly workflow (.github/workflows/nightly.yml)
is planned but not done yet — the Running section below tells the current truth.
Test code lives in BloomDesktop (src/BloomE2E/), versioned with the product code.
Test input collections live in https://github.com/BloomBooks/bloom-testing-inputs,
pinned by build/testing-inputs.pin and fetched to output/testing-inputs/ by
node build/get-testing-inputs.mjs.
Build Bloom whenever it helps; the usual rules are suspended here
The repo's guidance for agents says not to build Bloom: use the agent-dotnet wrapper, never
run pnpm build, let the dev server push front-end edits into the developer's running Bloom.
Those rules protect a Bloom the developer is running from this worktree. They do not apply
while you follow this skill. The suite launches its own Bloom.exe from output/Debug/ (or
output/Release/), with --e2e --automation, on a temp copy of a collection, and that instance
runs alongside whatever Bloom the developer has open. Developing a test does not disturb them.
The Bloom you launch is also not the one the dev server feeds: it reads the front end from
output/browser and the C# from the built exe. So a test sees a change to Bloom only after a
build, and you build whenever it helps, without asking.
- A fresh worktree:
./init.sh(dependencies,pnpm install, and the full front-end build), thenpnpm installinsrc/BloomE2E,node build/get-testing-inputs.mjs, and the C# build below. - C# changed (an
E2eTestingApihook, anything undersrc/BloomExe/), or noBloom.exeis built yet:dotnet build src/BloomExe/BloomExe.csproj. Plaindotnet, not thebuild/agent-dotnetwrapper: the wrapper builds into a private tree and builds noBloom.exeapphost, so the suite would never find its output. - Front end changed (a
data-testidin a.tsxfile):pnpm build:uiinsrc/BloomBrowserUIrebuilds the bundles inoutput/browser, manifest included. Run the fullpnpm buildthere when the change also touches pug, LESS, markdown, or content. - Before you trust a failure, ask whether the build is current. A
data-testidthat is in the source but not inoutput/browser, or a hook that is inE2eTestingApi.csbut not in the exe, fails exactly like a bug in the test.
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.
- today Changed · +21 lines 871477533063
- 2d ago First seen · 500 lines · 89 tokens per session scan A a106bba824f0
add-e2e-test is a skill published in the GitHub repository BloomBooks/BloomDesktop (44 stars, last pushed today), licensed MIT. It adds 89 tokens to every session and 8,310 once invoked, about $0.0004 per session on Opus 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-04.
Other skills, from other repositories
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.
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.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…
pyats-dynamic-test
Generate and execute deterministic pyATS aetest validation scripts - interface state, OSPF neighbors, BGP paths, ping matrices, and custom compliance tests. Use when writing a network test, validating post-change state, running pass/fail checks, or building automated regression tests.
trailblaze
Use when working with Trailblaze — natural-language device control for coding agents across iOS, Android, and web, with replayable .trail.yaml files as the artifact. Trigger on mentions of Trailblaze, the trailblaze CLI, .trail.yaml files, trailmaps, waypoints, or requests to drive / author / debug / run UI tests on…
Detox Mobile Testing
Gray-box end-to-end testing for React Native apps with Detox. Covers .detoxrc.js configuration, build and test commands, matchers, device.launchApp control, automatic synchronization, and macOS CI pipelines.