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/get-bb/bb/plugin-guide-maintenancenpx skills add get-bb/bb --skill plugin-guide-maintenancegit clone --depth 1 https://github.com/get-bb/bbWhat 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 | $0.00085 | $0.00708 |
| Opus 5 | $0.00043 | $0.00354 |
| Sonnet 5 | $0.00017 | $0.00142 |
| Haiku 4.5 | $0.00009 | $0.00071 |
Grade A, and why
plugin-guide-maintenance 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 yesterday.
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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Maintain the Plugin Guide for a public API change
The Plugin Guide is bb's public Plugin SDK reference. Use this workflow only when a public API change affects its documented contract.
Confirm the trigger
Build the declarations and inspect the SDK change:
pnpm exec turbo run build:types --filter=@get-bb/plugin-sdk
git diff -- packages/plugin-sdk/package.json packages/plugin-sdk/src
Continue only when the API change affects a Guide card, API symbol list, fixture, or SDK inventory. If the Guide remains accurate, do not change it.
New public members also require:
- an
experimental_name, or anExperimentaltype name; - an entry in
docs/api_to_audit.md; - compatibility with released SDK users unless the user approves the break.
Find the product source
For a visible method, inspect these sources:
- The app component that shows the surface.
- The slot, collector, or adapter that inserts the plugin content.
- The closest app test that defines the real states.
Record stable source paths and anchors in
packages/plugin-api-map/src/anatomy-manifest.json. Use labels, roles, data
attributes, class constants, and state names as anchors.
For a method without a visible surface, use the Plugin backend group. Do not invent interface elements.
Add the Guide entry
For a new Guide entry, run the scaffold command with its sources and symbols:
pnpm exec turbo run scaffold:surface-entry --filter=@bb/plugin-api-map -- \
--id <stable-id> \
--title "<visible-product-object>" \
--group <group> \
--source <source-path> \
--api-symbol <exported-name>
Complete the applicable changes:
- Update
packages/plugin-api-map/src/surfaces.ts. - Prefer an existing card unless the API creates a new product surface.
- Keep existing surface IDs stable and list each exact exported symbol.
- For a visible method, update
wireframes.tsxand its marker. - Match the real ownership, labels, roles, order, states, actions, and outcome.
- Keep Guide annotations separate from the product interface.
- Add focused tests for the entry, source anchors, trigger, and outcome.
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.
- yesterday First seen · 90 lines · 85 tokens per session scan A 16b5017c03a3
plugin-guide-maintenance is a skill published in the GitHub repository get-bb/bb (2,762 stars, last pushed 2d ago), licensed MIT. It adds 85 tokens to every session and 708 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-08-30.
Other skills, from other repositories
emil-design-eng
This skill encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great.
cradle-cli
Use whenever you need to read, inspect, wait on, or mutate Cradle-owned state or workflows, including issues, delegation, sessions, awaits, CI/review waits, timed waits, Work inspection, workspaces and git inspection, Chronicle, automations, usage, observability, skills, agents, profiles, providers, preferences…
elysiajs
Create backend with ElysiaJS, a type-safe, high-performance framework.
transitions-dev
Production-ready CSS transitions for web apps. Use when implementing notification badges, dropdowns, modals, panel reveals, page transitions, card resizes, number pop-ins, text swaps, icon swaps, success checks, avatar group hovers, or error state shakes. Triggers on "add a transition", "animate the dropdown", "make…
userinterface-wiki
UI/UX best practices for web interfaces. Use when reviewing animations, CSS, audio, typography, UX patterns, prefetching, or icon implementations. Covers 11 categories from animation principles to typography. Outputs file:line findings.
cradle-observability-debugger
Debug Cradle local observability data by querying SQLite events/incidents/timeline, runtime snapshots, metrics, and server logs.