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/component-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/component-test)<a href="https://agentmods.dev/skills/bloombooks/bloomdesktop/component-test"><img src="https://agentmods.dev/badge/skills/bloombooks/bloomdesktop/component-test/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/component-test"><img src="https://agentmods.dev/badge/skills/bloombooks/bloomdesktop/component-test.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.00064 | $0.00627 |
| Opus 5.5 | $0.00026 | $0.00251 |
| Sonnet 5.5 | $0.00013 | $0.00125 |
| Haiku 4.5 | $0.00006 | $0.00063 |
Grade A, and why
component-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 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Component UI tests
The test system is explained in src/BloomBrowserUI/react_components/component-tester/README.md;
read it first. Then decide whether you are in the setup or the implementation stage.
Setup stage
If the component has no component-tests/ directory, it is not set up yet. Use
src/BloomBrowserUI/react_components/registration and its component-tests/ folder as the
example. You will need to intercept some API calls with
src/BloomBrowserUI/react_components/component-tester/apiInterceptors.ts.
- In the component's own directory (not in
component-tests/), createtest.shandshow.shscripts that run the tests and open the component in a browser for manual testing (registration/show.shis the model; the README documents./show.sh). - If there is no
<componentname>-ui-test-plan.mdyet, make one. Keep it small: during setup the goal is proving the component shows in a browser and does one minimal thing, not complete coverage. The developer will direct you to add more later. - Work through the plan, checking items off as you go and running the tests along the way.
- If you are unclear how to organize tests across files, make a proposal and ask.
Implementation stage
Troubleshooting. To see what the browser sees (console, DOM, screenshots), use a CDP client;
the run-bloom skill describes attaching Playwright over CDP. If you have no browser
tooling available, stop and ask the developer to enable some.
Refactoring to make testing easier. Sometimes the top-level component is not readily testable and a core should be extracted. Do not do that without discussing it first: stop and make a proposal. Do not refactor any non-test code without prior approval.
Guidelines for the tests.
- If you want to make a mock, stop and ask.
- Avoid timed waits like
page.waitForTimeout(1000). If there is no other way, discuss it first and, once approved, document why in a comment. - Feel free to add
data-test-idattributes to elements in the component under test. Avoid finding things by CSS. - Keep the tests well factored, with common code in a
test-helpers.tsfile. - Do not check styles as a way to know the status of something; that is fragile. Have the component expose a class or attribute instead.
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 065ba86fe073
- 1mo ago First seen · 48 lines · 64 tokens per session scan A 87928d036f09
component-test is a skill published in the GitHub repository BloomBooks/BloomDesktop (43 stars, last pushed today), licensed MIT. It adds 64 tokens to every session and 627 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-09-19.
Other skills, from other repositories
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…
next-partial-prefetching-optimizer
Optimize what selected Next.js client navigations include before the click under Partial Prefetching. Use after Cache Components and Partial Prefetching are adopted when the user wants selected URL-specific UI to be instant, wants reusable content to wait for navigation, or needs to choose between default, viewport…
verify
Build/launch/drive recipe for verifying apps/docs changes at runtime (demos, docs pages, llms.txt).
verify-bug
Post-merge UAT verification workflow. Walks JIRA reproduce steps, performs comparative audits (Before/After), attaches evidence to JIRA, and transitions status on PASS.
verify-work
Verify feature, bug, UI, API, mobile, security, or deployment work against acceptance criteria.
uat-signoff
Walk a business/UAT approver through a plain-language demo of a verified feature and capture business acceptance signoff.