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/.claude/skills/branding-report/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/branding-report)<a href="https://agentmods.dev/skills/bloombooks/bloomdesktop/branding-report"><img src="https://agentmods.dev/badge/skills/bloombooks/bloomdesktop/branding-report/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/bloombooks/bloomdesktop/branding-report"><img src="https://agentmods.dev/badge/skills/bloombooks/bloomdesktop/branding-report.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00069 | $0.01686 |
| Opus 5.5 | $0.00028 | $0.00674 |
| Sonnet 5.5 | $0.00014 | $0.00337 |
| Haiku 4.5 | $0.00007 | $0.00169 |
Grade A, and why
branding-report 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
branding-report
Render a Bloom book's pages across a matrix of branding × page × layout × xmatter by driving the running Bloom, screenshot each page into a folder, and explore the results in a filterable viewer (or bake a self-contained HTML report to share).
Use this when asked to "survey the brandings", "show every branding's back cover / title page", "compare a branding across layouts", or otherwise audit how branding/appearance renders across Bloom's real xmatter — at full fidelity (real cover color, appearance CSS, generated QR, etc.).
The heavy loop is pure Node driving Bloom's HTTP API + headless-Chrome CDP — no AI tokens.
Prerequisites
- Bloom running from source via
./go.sh(a Debug build). The survey relies on the DEBUG-only multi-axis set-state handler onPOST /bloom/api/settings/branding(accepts{branding,layout,xmatter}JSON; seeCollectionSettingsApi.cs). If a static field in the branding code was added or changed while Bloom was running, fully restart it; hot-reload leaves a new static field null and every capture NREs (seeREADME-gotchas.md). - A collection open with at least one book (any book works; branding shows mainly on cover/title/credits/back-cover pages).
- Google Chrome installed (path in
survey.mjsCHROME).
Confirm Bloom is up and get its port from launcherControl.mjs --status --json (run-bloom
skill); 8089 is first-come across worktrees, so pass the reported port via --base.
Axes / parameters (survey.mjs)
| Flag | Values | Default |
|---|---|---|
--brandings |
comma list, or all (every folder under src/content/branding) |
Default |
--pages |
front,title,credits,insideFront,insideBack,back or all |
front,title,credits,back |
--layouts |
e.g. A5Portrait,Device16x9Landscape |
current (unchanged) |
--xmatters |
e.g. Factory,Device,Kyrgyzstan2020 |
current (unchanged) |
--book |
path to the book folder | currently-selected / first non-factory book |
--out |
output dir | ./branding-report-out |
--base |
Bloom base URL | http://localhost:8089/bloom |
--settle-ms, --load-ms |
tuning | 400 / 1500 |
What ships with it
9 files 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.
- 1mo ago Changed 3957c29053db
- 1mo ago Changed · +4 lines · +69 tokens per session db1574edb7a0
- 2mo ago First seen · 116 lines · 0 tokens per session scan A dab07d9d2bcc
branding-report is a skill published in the GitHub repository BloomBooks/BloomDesktop (43 stars, last pushed today), licensed MIT. It adds 69 tokens to every session and 1,686 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…