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
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/get-bb/bbnpx agentmods add skills/get-bb/bb/verify-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/verify-bb)<a href="https://agentmods.dev/skills/get-bb/bb/verify-bb"><img src="https://agentmods.dev/badge/skills/get-bb/bb/verify-bb.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.00070 | $0.02639 |
| Opus 5 | $0.00035 | $0.01319 |
| Sonnet 5 | $0.00014 | $0.00528 |
| Haiku 4.5 | $0.00007 | $0.00264 |
Grade A, and why
verify-bb scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -fsS "$BB_SERVER_URL/health" How it starts
The opening of the file, as written. The whole thing — 234 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify BB
Run from the repository root. Start with the feature map
and select the affected journeys. Read docs/debugging-and-qa.md for the
existing launcher's contract. The launch below targets the source web app and
local host daemon. Desktop, native mobile, and hosted services have additional
setup in their feature files. A pass on one platform does not verify another.
Coverage and selection
The feature map aims to inventory every feature discoverable in this checkout,
including disabled plugins, compatibility paths, and developer surfaces. Group
files contain individual capability recipes. Read only the relevant files for
a focused verification request; for an exhaustive audit, track every recipe.
Mark each selected recipe passed, failed, not run, or blocked with its
specific prerequisite and evidence. Group-level source coverage never upgrades
an unexecuted recipe to a pass.
Run the read-only inventory check before selecting coverage:
.bb/skills/verify-bb/scripts/inventory.py
Python 3 and Git are required. The check compares source declarations and
fingerprints with INVENTORY.md and inventory.json, and requires
all recipe owners to exist. On drift, inspect the changed source, add/update
recipes and their prerequisites, then run scripts/inventory.py --write via
its full path above and review the diff. Never accept a new baseline merely to
silence the check. It watches CLI families, app routes/actions/settings, public
contracts/SDK, plugin sources, platform clients and server/daemon implementation.
The broad fingerprints deliberately flag implementation changes too: some
require only a recorded review, others reveal behavior missing from the map.
Literal extraction cannot resolve every dynamic registration, and source
fingerprints cannot judge recipe completeness; reconcile menus, help, schemas
and actual behavior during maintenance.
The latest maintenance audit assessed all 348 recipes: 166 passed, 177 partial/blocked and 5 failed. The per-recipe ledger records evidence and remaining subchecks. VALIDATION.md preserves the initial smoke history. An exhaustive map is the test inventory, not a whole-product pass.
What ships with it
57 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.
- features/appearance.md 2.2 KB
- features/cloud-gateway.md 2.9 KB
- features/compact-menu.md 2.8 KB
- features/compatibility-api.md 4.3 KB
- features/composer.md 5.9 KB
- features/desktop.md 5.1 KB
- features/developer-fixtures.md 2.8 KB
- features/execution-controls.md 5.2 KB
- features/extensions.md 6.3 KB
- features/hosted-web.md 4.8 KB
- features/hosts-updates.md 3.4 KB
- features/interactions.md 3.0 KB
- features/local-project.md 2.6 KB
- features/mobile.md 4.2 KB
- features/navigation.md 6.1 KB
- features/plugin-account-pool.md 3.4 KB
- features/plugin-ask-user-question.md 2.5 KB
- features/plugin-automations.md 3.7 KB
- features/plugin-concurrency-limit.md 2.6 KB
- features/plugin-connect.md 3.2 KB
- features/plugin-custom-instructions.md 2.2 KB
- features/plugin-docs.md 4.5 KB
- features/plugin-github.md 3.9 KB
- features/plugin-inline-vis.md 2.6 KB
- features/plugin-keep-awake.md 2.6 KB
- features/plugin-memory.md 2.9 KB
- features/plugin-monaco-editor.md 2.8 KB
- features/plugin-pdf-preview.md 1.9 KB
- features/plugin-plugin-api-docs.md 3.0 KB
- features/plugin-plugin-api-tester.md 1.6 KB
- features/plugin-provider-acp.md 2.9 KB
- features/plugin-provider-claude-code.md 2.7 KB
- features/plugin-provider-codex.md 2.8 KB
- features/plugin-provider-pi.md 2.2 KB
- features/plugin-provider-retry.md 2.3 KB
- features/plugin-provider-usage.md 2.2 KB
- features/plugin-push-notifications.md 2.6 KB
- features/plugin-scheduled-send.md 2.7 KB
- features/plugin-secrets.md 2.7 KB
- features/plugin-side-chat.md 2.7 KB
- features/plugin-tasks.md 4.8 KB
- features/plugin-theme-preview.md 2.8 KB
- features/plugin-workflows.md 3.4 KB
- features/projects-environments.md 7.4 KB
- features/README.md 7.2 KB
- features/responsive-accessibility.md 3.6 KB
- features/settings.md 4.6 KB
- features/thread-lifecycle.md 3.5 KB
- features/timeline.md 4.4 KB
- features/workspace-panels.md 7.2 KB
- inventory.json 67 KB
- INVENTORY.md 55 KB
- MAINTENANCE.md 8.5 KB
- scripts/inventory.py 9.4 KB runs code
- scripts/test_inventory.py 4.8 KB runs code
- validation-2026-09-05.json 498 KB
- VALIDATION.md 6.5 KB
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 · 234 lines · 70 tokens per session scan A 75da64132d4f
verify-bb is a skill published in the GitHub repository get-bb/bb (3,416 stars, last pushed today), licensed MIT. It adds 70 tokens to every session and 2,639 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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.