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 memorygit 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/memory)<a href="https://agentmods.dev/skills/get-bb/bb/memory"><img src="https://agentmods.dev/badge/skills/get-bb/bb/memory/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/memory"><img src="https://agentmods.dev/badge/skills/get-bb/bb/memory.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.00016 | $0.01001 |
| Opus 5.5 | $0.00006 | $0.00400 |
| Sonnet 5.5 | $0.00003 | $0.00200 |
| Haiku 4.5 | $0.00002 | $0.00100 |
Grade A, and why
memory 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 yesterday.
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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BB memory
This plugin is provider-independent. When diagnosing duplicate or conflicting memories, check whether provider-native memory is also enabled; recommend turning it off under Settings → Providers.
The memory plugin automatically injects a compact index of global memories and memories for the current BB project. The index contains summaries only. Settings → Memory lists every memory for the user to edit or delete.
bb memory catalog [--scope project|global|all] [--json]
bb memory search <query> [--scope project|global|all] [--json]
bb memory get <id> [--scope project|global|all] [--json]
bb memory history <id> [--scope project|global|all] [--limit 1-100] [--json]
Project-scoped commands use the invoking CLI's current BB project.
Retrieve progressively
When a memory summary may be relevant, inspect it instead of guessing:
- Search with
bb memory search "<query>" --scope all --json. - Read the selected record with
bb memory get <id> --scope all --json. - Treat remembered facts as potentially stale. Verify drift-prone facts when doing so is cheap or consequential.
Do not load every memory. Stop after the relevant records are clear.
Save durable learning
The agent may proactively write memory when information is likely to help in a future thread and is costly or error-prone to rediscover.
Use project scope for repository-specific information:
- commands, conventions, architecture decisions, paths, and environments;
- project-specific user preferences;
- verified quirks, failure causes, and reusable workarounds.
Use global scope only for broadly applicable information:
- user identity, communication preferences, and general workflow habits;
- preferences that clearly apply across repositories;
- stable cross-project operating conventions.
When scope is ambiguous, use project scope. Global scope must be explicit.
Create a memory with:
bb memory add --scope project \
--name <stable-kebab-name> \
--summary "<one-line routing summary>" \
--details "<complete durable detail>" \
--kind fact|preference|decision|procedure|episode|reference \
--tag <tag> \
--importance <0-100> \
--reason "<why this will help a future thread>" \
--json
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.
- yesterday Changed · +11 lines 0c0f6bda1c73
- 27d ago Changed · +12 lines b86cea821d14
- 1mo ago Changed · -16 tokens per session 9bc71ecebd88
- 1mo ago First seen · 95 lines · 32 tokens per session scan A 186e8ba80fbb
memory is a skill published in the GitHub repository get-bb/bb (4,324 stars, last pushed today), licensed MIT. It adds 16 tokens to every session and 1,001 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
cradle-plugin-nowledge-mem
Use the Nowledge Mem MCP tools registered by Cradle for Working Memory, Context Bundle, durable memory recall, explicit memory writes, and conversation thread lookup or capture. Invoke as /cradle-plugin-nowledge-mem when a task needs prior Nowledge context or a durable memory update.
recall
Answer from the project's wiki what was decided, why, and what it says about an area. Use when the user asks "why did we", "what did we decide", "is there a decision on" or "what does the wiki say", and before starting design or a non-trivial change in an area the wiki may cover.
start
Start using Nimbalyst Wiki: show how agents build a local wiki, capture decisions, track typed pages, open the local browser view, and optionally use a team wiki. Use when the user asks what this plugin does, which skills it has, or how to begin.
review-ui-leak-via-listeners
Normative reviewer for memory leaks where UI components or view classes are retained by listeners on properties of long-lived services (APP/Project) or by strong references in singletons (object, companion object, static fields). Use when reviewing tool-window panels, settings pages, dialogs, wizard steps, or any code…
chronicle
Analyze indexed Aily chat session history for prior decisions, tool executions, project summaries, usage tips, and session-store reindexing.
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…