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 bb-accountgit 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/bb-account)<a href="https://agentmods.dev/skills/get-bb/bb/bb-account"><img src="https://agentmods.dev/badge/skills/get-bb/bb/bb-account/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/bb-account"><img src="https://agentmods.dev/badge/skills/get-bb/bb/bb-account.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.00031 | $0.00718 |
| Opus 5.5 | $0.00012 | $0.00287 |
| Sonnet 5.5 | $0.00006 | $0.00144 |
| Haiku 4.5 | $0.00003 | $0.00072 |
Grade A, and why
bb-account 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 16d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
bb account
The builtin bb account plugin links this bb server to a getbb.app account and
holds the server credential. Remote access (bb connect) and hosted services
reach getbb.app through it; they never see the credential.
Check the account
bb account status [--json] prints the signed-in name, GitHub login, handle,
and this server's label and URL, or Not signed in. A bb that holds a
pairing but couldn't load its account yet says so; it keeps retrying, and
remote access and hosted services start once it succeeds. With --json it
prints {state, revision, account, login}: state is signed-in,
signed-out, or profile-pending, and login is the pending browser
sign-in, if any.
Sign in
bb account login [--json]starts a browser sign-in. It prints ahttps://getbb.app/link?code=XXXX-XXXXlink and the code, then returns. Open the link on any device, sign in with GitHub, claim a handle if asked, and approve. bb finishes signing in on its own; the code expires after 10 minutes.bb account login --wait [--json]waits for that sign-in to be approved, denied, or expire, and exits non-zero unless it signed in.bb account login --code XXXX-XXXX [--json]pairs with a one-time code from the getbb.app dashboard.bb connect --code <code>is an alias.--base-url <url>points sign-in athttps://getbb.apporhttps://vibecodethis.site(staging); a development build also acceptshttp://bb.localhost:<port>. Any other origin is refused. In a source checkout,pnpm devsetsBB_DEV_CONNECT_BASE_URLso sign-in uses that worktree's local Cloud.
Signing in again replaces the account this bb is signed in to, and revokes the previous server on getbb.app when the new sign-in is for a different one. Starting a new sign-in cancels one that is still waiting for approval.
Sign out
bb account logout [--json] revokes this server's credential on getbb.app,
forgets it locally, and cancels a sign-in still waiting for approval. Remote
access and hosted services stop until you sign in again. If getbb.app can't be
reached, bb still signs out locally and says the server wasn't revoked; remove
it from the getbb.app dashboard. --json prints {revocation, status}. To
stop remote access but stay signed in, use bb connect off.
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.
- 16d ago First seen · 60 lines · 31 tokens per session scan A 7bd5557e20da
bb-account is a skill published in the GitHub repository get-bb/bb (4,324 stars, last pushed today), licensed MIT. It adds 31 tokens to every session and 718 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-30.
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…