bb is an agentic IDE that lets users control, customize, and automate a software-development environment through a desktop app, web app, command-line interface, or HTTP API. Developers use it to run work in observable threads that can be steered or handed off to other agents. Its catalogue add-ons provide skills and instructions for working with bb.
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 skills add get-bb/bb --skill maintain-verification-skillgit clone --depth 1 https://github.com/get-bb/bbWrote 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/get-bb/bb/maintain-verification-skill)<a href="https://agentmods.dev/skills/get-bb/bb/maintain-verification-skill"><img src="https://agentmods.dev/badge/skills/get-bb/bb/maintain-verification-skill.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.00053 | $0.00796 |
| Opus 5 | $0.00026 | $0.00398 |
| Sonnet 5 | $0.00011 | $0.00159 |
| Haiku 4.5 | $0.00005 | $0.00080 |
Grade A, and why
maintain-verification-skill 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Maintain a verification skill
Keep a repository's .bb/skills/verify-<app>/ usable by the next agent.
Locate and scope
Read repository instructions and the target verification skill. If several
apps are plausible and the request does not identify one, ask which. If none
exists, report that and point to create-verification-skill; do not invent an
audit target. A request to explain maintenance does not authorize running it.
Edit only the verification skill directory, its feature map, and its owned helpers. Report product regressions separately. Do not rewrite the expected behavior to match a broken app. Preserve only explicitly requested feature subsets and real product boundaries.
Read source
Check the index against its feature files. Read each feature's source entry points and compare its recipe with current routes, labels, CLI flags, defaults, and persistence behavior. Record a concrete source citation for each suspected drift and one concise live recipe per feature. Reconcile the feature inventory against current routes, commands, settings, plugins, platform clients, and action menus. Document omitted features even when their live prerequisites are unavailable. Preserve an explicitly requested subset, but do not infer a scope limit from gaps left by an earlier generator.
Work directly unless delegation is authorized. When source review is delegated, keep browser driving with one owner and reconcile findings before editing. Concurrent reviewers must not manipulate a shared app session.
Drive the app
Follow the skill's launch and isolation rules. Run doctor before driving and after unexpected behavior. Reset a stuck UI to a known state; do not repeatedly click into a broken session. Exercise every mapped feature through its actual user entry point, even when source review finds no drift.
Record the initial state, action, observable outcome, and relevant side effect. Use fresh isolated sessions when the launch model requires them. Preserve evidence outside disposable runtime state, including failed-attempt evidence. Clean up residue from failed attempts before proceeding.
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.
- yesterday First seen · 82 lines · 53 tokens per session scan A d37532eab20e
maintain-verification-skill is a skill published in the GitHub repository get-bb/bb (3,416 stars, last pushed today), licensed MIT. It adds 53 tokens to every session and 796 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-09-07.
Other skills, from other repositories
browser-qa
Use when you need lightweight browser QA for a web page, local HTML file, or app: inspect console errors, broken assets, keyboard/focus behavior, viewport readability, and publish evidence-backed findings JSON through a local HTML report viewer.
playwright-explore-website
A browser-testing workflow that explores a website through Playwright, a tool for controlling a web browser with code. It records important user flows, page elements, expected results, and possible test cases.
vite-browser-release-smoke
Pre-release smoke verification workflow for Vite apps with vite-browser. Use this whenever users ask for final checks before merge/release, including core path validation, runtime sanity, HMR diagnosis, and evidence-based sign-off.
playwright-best-practices
A set of guidelines for writing and maintaining Playwright tests for websites and applications. It covers browser-based end-to-end tests, API tests, component tests, and specialised cases such as authentication or file uploads.
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.
playwright-cli
Automate browser interactions, test web pages and work with Playwright tests.