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 submit-a-plugingit 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/submit-a-plugin)<a href="https://agentmods.dev/skills/get-bb/bb/submit-a-plugin"><img src="https://agentmods.dev/badge/skills/get-bb/bb/submit-a-plugin/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/submit-a-plugin"><img src="https://agentmods.dev/badge/skills/get-bb/bb/submit-a-plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00023 | $0.00740 |
| Opus 5.5 | $0.00009 | $0.00296 |
| Sonnet 5.5 | $0.00005 | $0.00148 |
| Haiku 4.5 | $0.00002 | $0.00074 |
Grade A, and why
submit-a-plugin 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 1mo 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Submit a plugin
Submit a public plugin to the BB Community marketplace. The marketplace stores plugin metadata. The plugin code stays in its Git repository or npm package.
Choose the task
If the user asks only for instructions, explain the process without remote changes.
If the user asks for a submission, prepare and validate everything possible. Ask only for information that the plugin, Git, npm, GitHub, or marketplace cannot supply.
A submission request does not approve a release. Before the first Git push, tag, npm publication, or other release mutation, show the exact account, repository, commit, package, version, source, and commands. Get approval for that release.
Do not expose credentials, private URLs, or local secrets.
Read current contracts
The marketplace contract can change independently from BB releases. Read these files from the default branch of https://github.com/get-bb/marketplace:
- README.md
- schema/marketplace-v2.schema.json
- marketplace.base.json, for the current category IDs
- icons/README.md
- At least two current files in entries/
An entry file uses the version 2 entry fields. Read schema/marketplace-v2.schema.json for those fields. The older schema/marketplace.schema.json file describes the frozen version 1 output document. Do not use it as the entry contract.
Treat those files as the contract. Use this skill for workflow and quality rules.
Workflow
- Read repository instructions, package.json, Git state, and release state.
- Validate the plugin with its package manager and bb plugin build.
- Select and verify one public release source.
- Get separate approval before any release mutation.
- Create one marketplace entry with a vendored icon.
- Install the plugin and capture its screenshots.
- Copy the plugin PLUGIN_OVERVIEW.md file into the marketplace. The public marketplace requires an overview file on every entry.
- Validate the marketplace repository.
- Commit only the entry, icon, screenshots, and overview file.
- Open a pull request from the submitter account.
What ships with it
4 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.
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.
- 1mo ago Changed · -48 tokens per session 05628c2179e9
- 1mo ago Changed · +16 lines · +7 tokens per session bcb61bfefe3b
- 1mo ago First seen · 71 lines · 64 tokens per session scan A 4b544c164572
submit-a-plugin is a skill published in the GitHub repository get-bb/bb (4,324 stars, last pushed today), licensed MIT. It adds 23 tokens to every session and 740 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-08-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…