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 agentmods add skills/get-bb/bb/memorynpx skills add get-bb/bb --skill memorygit clone --depth 1 https://github.com/get-bb/bbWhat 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 | $0.00032 | $0.00707 |
| Opus 5 | $0.00016 | $0.00353 |
| Sonnet 5 | $0.00006 | $0.00141 |
| Haiku 4.5 | $0.00003 | $0.00071 |
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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BB memory
This plugin is provider-independent. Recommend disabling provider-native memory under Settings → Providers to avoid duplicated or conflicting stores.
The memory plugin automatically injects a compact index of global memories and memories for the current BB project. The index contains summaries only.
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
Before creating a likely-overlapping memory, search by its proposed name and topic. Update an existing record instead of creating a contradiction:
bb memory update <id> --expected-version <version> \
--summary "<new summary>" \
--details "<new details>" \
--reason "<why the memory changed>" \
--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 First seen · 95 lines · 32 tokens per session scan A 186e8ba80fbb
memory is a skill published in the GitHub repository get-bb/bb (2,762 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session and 707 once invoked, about $0.0002 per session on Opus 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
emil-design-eng
This skill encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great.
cradle-cli
Use whenever you need to read, inspect, wait on, or mutate Cradle-owned state or workflows, including issues, delegation, sessions, awaits, CI/review waits, timed waits, Work inspection, workspaces and git inspection, Chronicle, automations, usage, observability, skills, agents, profiles, providers, preferences…
elysiajs
Create backend with ElysiaJS, a type-safe, high-performance framework.
transitions-dev
Production-ready CSS transitions for web apps. Use when implementing notification badges, dropdowns, modals, panel reveals, page transitions, card resizes, number pop-ins, text swaps, icon swaps, success checks, avatar group hovers, or error state shakes. Triggers on "add a transition", "animate the dropdown", "make…
userinterface-wiki
UI/UX best practices for web interfaces. Use when reviewing animations, CSS, audio, typography, UX patterns, prefetching, or icon implementations. Covers 11 categories from animation principles to typography. Outputs file:line findings.
cradle-observability-debugger
Debug Cradle local observability data by querying SQLite events/incidents/timeline, runtime snapshots, metrics, and server logs.