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 skills/bloombooks/bloomdesktop/run-bloomnpx skills add BloomBooks/BloomDesktop --skill run-bloomgit 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/run-bloom)<a href="https://agentmods.dev/skills/bloombooks/bloomdesktop/run-bloom"><img src="https://agentmods.dev/badge/skills/bloombooks/bloomdesktop/run-bloom.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.00066 | $0.01043 |
| Opus 5 | $0.00033 | $0.00522 |
| Sonnet 5 | $0.00013 | $0.00209 |
| Haiku 4.5 | $0.00007 | $0.00104 |
Grade A, and why
run-bloom 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 5d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run Bloom (desktop app) — quick path
Bloom is a C#/WinForms shell hosting a React UI in WebView2. You drive it
programmatically through the dev launcher's control API and CDP. This skill is
the task-oriented quick path; the authoritative reference for every
mechanism, fallback, rule, and field-verified gotcha is
.github/skills/bloom-automation/SKILL.md (shared with Copilot agents; the
driver scripts live in that directory). All paths are repo-root-relative;
commands are bash.
1. Make sure Bloom is running
node .github/skills/bloom-automation/launcherControl.mjs --status --json
# exit 0 → launcher live; status has state, httpPort, cdpPort, vitePort, bloomProcessId
# exit 2 → nobody home (or starting:true = a launch is underway; never start another)
node .github/skills/bloom-automation/launcherControl.mjs --ensure-running --wait-ready --json
--ensure-running handles everything: stale discovery files, a launcher
mid-startup (waits instead of double-launching), an uninitialized worktree
(go.mjs runs ./init.sh itself, phase:"init"), and starting the stack
decoupled from your session (Orca terminal tab when available, else detached
to output/bloom-launcher.log). Never launch ./go.sh tied to your own
shell except when debugging the launcher itself, and never run an
already-built Bloom.exe directly (stale).
2. Get a .NET change into Bloom
node .github/skills/bloom-automation/launcherControl.mjs --restart --wait-ready --json
THE way — never ask the human to quit/restart, never kill-and-relaunch by hand. Returns the fresh ports. Front-end (.ts/.tsx/.less) edits need no restart at all: the Vite dev server pushes them into the running Bloom.
3. Drive it
node .github/skills/bloom-automation/switchWorkspaceTab.mjs --http-port <httpPort> --tab edit --json # collection | edit | publish
node .claude/skills/run-bloom/screenshotBloom.mjs --http-port <httpPort> --out output/screenshots/bloom.png --json
For arbitrary DOM/console/network work, attach Playwright (loaded from
src/BloomBrowserUI/react_components/component-tester) to
http://localhost:<cdpPort> with chromium.connectOverCDP — the two scripts
above are templates. On the Edit tab the page content is inside the iframe
named page. If a "Bloom had a problem" dialog appears, use
dismissProblemDialog.mjs (see bloom-automation SKILL.md).
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.
- 5d ago First seen · 85 lines · 66 tokens per session scan A 0a640b32929c
run-bloom is a skill published in the GitHub repository BloomBooks/BloomDesktop (44 stars, last pushed today), licensed MIT. It adds 66 tokens to every session and 1,043 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
v8-jit
V8 JIT optimization patterns for writing high-performance JavaScript in Next.js server internals. Use when writing or reviewing hot-path code in app-render, stream-utils, routing, caching, or any per-request code path. Covers hidden classes / shapes, monomorphic call sites, inline caches, megamorphic deopt, closure…
use-agent-browser-for-airi
Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
interactive-login
How to complete browser/interactive logins (aws / gh / glab / gcloud). The platform backgrounds the login poller so it survives the human's browser round-trip — and when that does NOT work.