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 connect-nextgit 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/connect-next)<a href="https://agentmods.dev/skills/get-bb/bb/connect-next"><img src="https://agentmods.dev/badge/skills/get-bb/bb/connect-next/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/connect-next"><img src="https://agentmods.dev/badge/skills/get-bb/bb/connect-next.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.00029 | $0.00635 |
| Opus 5.5 | $0.00012 | $0.00254 |
| Sonnet 5.5 | $0.00006 | $0.00127 |
| Haiku 4.5 | $0.00003 | $0.00064 |
Grade A, and why
connect-next 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 3d 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
bb connect next (beta)
The connect-next plugin makes this bb reachable at
https://<label>.next.getbb.app through bb's Fly gate, in addition to its
bb connect address https://<label>.getbb.app. The domain follows the bb
account it is signed in to (next.<account domain>); status prints the
exact address. It is on as soon as the
plugin is enabled and needs this bb signed in to its bb account
(bb account status).
bb connect-next status [--json]prints the label, the address, and the state:off,signed-out,connecting,connected,refused(the gate refused the server credential),offline(the gate can't be reached), orerror(the plugin couldn't start the tunnel;lastErrorsays why).bb connect-next on [--json]turns it on;bb connect-next off [--json]turns it off. Neither touches bb connect or the account sign-in.- The switch is the plugin setting
enabled, sobb plugin config bb--connect-next set enabled trueworks too.
Only turn it on or off when the user asks.
Port shares: every port shared from the bb server's machine with
bb connect expose <port> also answers at
https://<label>--<port>.next.<account domain> while connect next is on
(owner session only, like the bb connect share). bb connect expose prints
that URL on a second line, and bb connect-next status lists each share as
share <port> <url> <state> (--json: shares[] with port, url,
state pending | active | refused, and error).
Shares from other enrolled machines (bb connect expose <port> --host <machine>) answer at https://<machine-label>--<port>.next.<account domain>
while connect next is on; the machine's own daemon runs the tunnel while the
machine shares a port. bb connect-next status prints a
machine <name> (<host id>) <label> <state> line per machine with its
share lines (--json: machines[] with hostId, hostName, label,
state idle | connecting | connected | refused | offline | error,
lastError, and shares[]). A machine missing from the list shares nothing
or runs a bb too old for connect next machine tunnels.
The plugin itself is disabled by default: bb plugin enable bb--connect-next
first if bb connect-next is not found.
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.
- 3d ago First seen · 47 lines · 29 tokens per session scan A a23e76502067
connect-next is a skill published in the GitHub repository get-bb/bb (4,600 stars, last pushed today), licensed MIT. It adds 29 tokens to every session and 635 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-10-22.
Other skills, from other repositories
mirrord-db-branching
Helps users configure mirrord.json for database branching, enabling isolated database copies for safe development and testing. Use when the user wants to set up MySQL, MariaDB, PostgreSQL, MSSQL, MongoDB, Redis, DynamoDB, ClickHouse, Google Spanner, Amazon S3, turbopuffer, or generic branches, configure copy modes…
mirrord-prev-env
Help users create and manage mirrord preview environments — running a modified service as an isolated pod in a shared Kubernetes cluster, scoped by an environment key and HTTP/queue traffic filtering, so teams can validate and review changes against real traffic without affecting live services. Use when a developer…
mirrord-kafka
Helps DevOps engineers configure mirrord Operator's Kafka queue splitting feature end-to-end. Generates the MirrordSplitConfig and MirrordPropertyList Kubernetes CRD YAMLs (the current resources; MirrordKafkaTopicsConsumer + MirrordKafkaClientConfig are deprecated but still supported), the matching mirrord.json…
mirrord-operator
Help users install and configure the mirrord Operator for team/enterprise environments. Use when users ask about operator setup, Helm installation, cloud API key or license configuration, air-gapped/offline licensing, enabling features (queue splitting, DB branching, preview environments, multi-cluster), internal…
mirrord-header-propagation
Makes a codebase propagate W3C baggage (the baggage header carrying mirrord-session= ) end to end, so mirrord HTTP filters, preview environments, and queue splitting can route a whole request chain to one developer's session. Detects existing OpenTelemetry, Datadog, or other tracing that can already propagate baggage…
mirrord-temporal
Helps DevOps engineers configure mirrord Operator's Temporal task queue splitting feature end-to-end. Generates the MirrordSplitConfig and MirrordPropertyList Kubernetes CRD YAMLs, the matching mirrord.json splitqueues section with messagefilter and jqfilter, and Helm value guidance. Use this skill whenever the user…