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 claude-code-providergit 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/claude-code-provider)<a href="https://agentmods.dev/skills/get-bb/bb/claude-code-provider"><img src="https://agentmods.dev/badge/skills/get-bb/bb/claude-code-provider/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/get-bb/bb/claude-code-provider"><img src="https://agentmods.dev/badge/skills/get-bb/bb/claude-code-provider.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.00018 | $0.00495 |
| Opus 5.5 | $0.00007 | $0.00198 |
| Sonnet 5.5 | $0.00004 | $0.00099 |
| Haiku 4.5 | $0.00002 | $0.00049 |
Grade A, and why
claude-code-provider 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 14d 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.
What it actually says
Claude Code provider
Read settings with bb plugin config provider-claude-code; change a declared key
with bb plugin config provider-claude-code set <key> <value>.
disable1MContextdefaults tofalse. Enable withbb plugin config provider-claude-code set disable1MContext trueto setCLAUDE_CODE_DISABLE_1M_CONTEXT=1(0when off). Changes restart the thread's Claude process before its next turn, preserving context.chromeEnableddefaults tofalse. It starts Claude Code with--chromefor Claude in Chrome tools. The host needs the extension and a claude.ai login. A change restarts the thread's Claude process before its next turn, preserving context.- Select the Fast service tier in the model picker or pass
--service-tier fasttobb thread spawnfor supported Opus models. Usebb thread tell --service-tier fastto change a thread on its next turn;defaultturns it off. Fast mode requires eligible Claude access; subscription accounts need usage credits. It is billed at premium rates. The provider passes the selection as a session-scoped SDK setting, so it does not change the user's Claude defaults. sandboxEnableddefaults totrue. In Accept Edits and Approve for me modes bb runs Claude Code's Bash commands in its sandbox. Set it tofalseto use Claude Code's own command approvals and sandbox settings instead. A change restarts the thread's Claude process before its next turn, preserving context.- bb passes only
BB_CLAUDE_CODE_EXECUTABLEandCLAUDE_CODE_OAUTH_TOKENto the CLI. Mint the token withclaude setup-tokenfor machines with no interactive login. - Structured plan, message editing, and compaction are supported through the
corresponding
bb threadcommands. Unlisted model IDs are accepted by the provider; verify actual availability on the target host.
Inspect the thread and provider state after a change; do not restart unrelated threads or change settings merely to answer a question.
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.
- 14d ago Changed · +4 lines 4b4c8ce3f1b9
- 16d ago Changed · +4 lines 6933d0481beb
- 20d ago Changed · +7 lines 1c83c04df8c4
- 23d ago Changed · +3 lines d4db7c167c02
- 1mo ago Changed · -3 lines 006fcc4bb5d8
- 1mo ago First seen · 24 lines · 18 tokens per session scan A 9b25a5b84964
claude-code-provider is a skill published in the GitHub repository get-bb/bb (4,324 stars, last pushed today), licensed MIT. It adds 18 tokens to every session and 495 once invoked, about $0.0001 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-07.
Other skills, from other repositories
using-grove
Use when orchestrating Grove workspaces from outside, including creating or supervising host or container agents, steering a fleet, using Grove CLI or MCP tools, or having agents write to each other through the mailbox. Also use when splitting work across workspaces, reviewing a diff from several angles, managing…
working-in-grove
Use when working inside a Grove workspace, including reporting task phase, updating a workspace or its ticket links, using GROVEPHASEFILE, writing to another Grove agent through the mailbox, or waiting on slow work like CI by registering a watch instead of sleeping. Also use when a worktree has a phase file, when…
collaborating-on-diagrams
Use when working with an existing .drawio diagram through Grove collaboration. Triggers on opening, reading, editing, updating, stopping, or recovering a diagram in a Grove workspace. Covers revisioned managed writes, XML-preserving edits, collaboration state, conflicts, read-only stop, and container/editor limits.
mocking-up-in-grove
Use when a visual or frontend task in a Grove workspace needs a mockup approved before code — a new control, a redesigned surface, a layout change. Covers drawing a draw.io mockup through Grove's diagram tools, previewing it in the browser, getting sign-off, filing the approved image on the tracker issue, and handing…
leading-in-grove
Use when you lead a fleet of Grove teammates toward one deliverable, including deciding how many to spawn and how to split the work, writing their onboarding prompt, getting acknowledgment, running scheduled check-ins, answering their mailbox questions, keeping tickets and your own status compaction-proof, reviewing…
configuring-grove
Use when configuring Grove for a user or project, including agent rosters, init scripts, containers, private credentials, daemon or MCP setup, or the native-versus-terminal launch of a Claude Code or Codex agent. Also use when resolving config layers, validating a config schema, or explaining why a workspace starts…