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 provider-retrygit 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/provider-retry)<a href="https://agentmods.dev/skills/get-bb/bb/provider-retry"><img src="https://agentmods.dev/badge/skills/get-bb/bb/provider-retry/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/provider-retry"><img src="https://agentmods.dev/badge/skills/get-bb/bb/provider-retry.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.00026 | $0.00589 |
| Opus 5.5 | $0.00010 | $0.00236 |
| Sonnet 5.5 | $0.00005 | $0.00118 |
| Haiku 4.5 | $0.00003 | $0.00059 |
Grade A, and why
provider-retry 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 7d 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
Provider retry
The plugin is enabled on fresh installations. It reacts only to failed Codex and Claude Code turns and never blocks a send; prior output or tool activity does not prevent a retry. It queues a retry of the failed turn, which core runs by continuing accepted input or re-sending input the provider never accepted, for one of three failures:
- A structured provider overload: retried after a short delay that doubles on each attempt.
- An unavailable provider (HTTP 500, 502, 503, or 504, an internal error, or a failed or dropped connection, including an Account Pooler that could not reach the provider): retried after about a minute, doubling on each attempt.
- A subscription-window limit with a reported reset time: retried shortly after the window opens, with random spread so threads on one account do not wake together. Credit and spend limits are not retried.
For Account Pooler routes, retry timing comes from the pool's earliest usable account for the failed request's model, including parent pools, so a generic provider 429 without quota windows can still schedule a retry. Unknown resets, authentication failures, and unavailable pool sources do not schedule retries.
A turn gets at most four automatic retries. The maximumWait setting
(6 hours by default, or 24 hours or No limit) skips a subscription-limit
retry whose reset is farther away:
bb plugin config provider-retry set maximumWait "24 hours".
A pending retry is an ordinary durable queued row, shown on the thread's queue card with its reason and time, and survives restart.
bb provider-retry status [thread-id] [--json]
bb provider-retry explain [thread-id] [--json]
bb provider-retry retry <thread-id> [--json]
bb provider-retry cancel <thread-id> [--json]
status defaults to the current thread and lists every thread outside one.
explain reports the last recorded scheduling or skip decision; it is
historical and survives restart, so use status for what is still pending.
Decisions from before the plugin version that records them are not
backfilled. The plugin RPC decision.get accepts { threadId } and returns
the same nullable diagnostic.
retry sends the pending row now; cancel deletes it. Inspect the failed turn
before retrying manually, and avoid duplicating an existing queued retry. Use
the core bb thread retry command for an intentional manual retry of a turn
with no pending row; follow its live help for selection and scheduling flags.
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.
- 7d ago Changed · +3 lines · +6 tokens per session edbfa9f5e389
- 13d ago Changed · +21 lines · +3 tokens per session 2b67459ce183
- 18d ago Changed · +11 lines e482abb6e25c
- 1mo ago First seen · 18 lines · 17 tokens per session scan A 6ca735038c95
provider-retry is a skill published in the GitHub repository get-bb/bb (4,656 stars, last pushed today), licensed MIT. It adds 26 tokens to every session and 589 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…