plugin-guide-maintenance

plugin-guide-maintenance is a skill for Claude Code, Codex from get-bb/bb. It costs 23 tokens per session (1,116 once invoked), scanned A, original, MIT.

A maintenance workflow for keeping a public guide accurate when the Plugin SDK changes. It covers changes to documented plugin APIs, examples, test fixtures, and SDK inventories.

In plain words
What is it for?
Use it when adding, renaming, stabilizing, or removing public members in the Plugin SDK, app slots, or plugin API. It helps trace visible plugin features to their source code and tests.
Why use it?
It helps prevent the guide from describing APIs that have changed, while also checking that new public API names and compatibility rules are documented.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it when adding, renaming, stabilizing, or removing public members in the Plugin SDK, app slots, or plugin API. It helps trace visible plugin features to their source code and tests.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/get-bb/bb/plugin-guide-maintenance
About the project

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.

get-bb/bb · 4,324 stars · on GitHub · getbb.app

Install

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.

Any agent
npx skills add get-bb/bb --skill plugin-guide-maintenance
Clone the repo
git clone --depth 1 https://github.com/get-bb/bb

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for plugin-guide-maintenance

README.md
[![agentmods](https://agentmods.dev/badge/skills/get-bb/bb/plugin-guide-maintenance/github.svg)](https://agentmods.dev/skills/get-bb/bb/plugin-guide-maintenance)
Your own site
<a href="https://agentmods.dev/skills/get-bb/bb/plugin-guide-maintenance"><img src="https://agentmods.dev/badge/skills/get-bb/bb/plugin-guide-maintenance/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.

agentmods 80×15 button for plugin-guide-maintenance

Your own site · 80×15
<a href="https://agentmods.dev/skills/get-bb/bb/plugin-guide-maintenance"><img src="https://agentmods.dev/badge/skills/get-bb/bb/plugin-guide-maintenance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 23 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,116 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00023 $0.01116
Opus 5.5 $0.00009 $0.00446
Sonnet 5.5 $0.00005 $0.00223
Haiku 4.5 $0.00002 $0.00112

Measured 20d ago against content hash b5a433224b06, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

plugin-guide-maintenance 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 20d 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.

.bb/skills/plugin-guide-maintenance/SKILL.md · 125 lines

How it starts

The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Maintain the Plugin Guide

The Plugin Guide is bb's public Plugin SDK reference. For a public API change, follow the full workflow. For annotation-only maintenance, start at Maintain annotation layout, skip the public-API section, and then follow the annotation-only verification path.

Confirm a public API change

Build the declarations and inspect the SDK change:

pnpm exec turbo run build:types --filter=@get-bb/plugin-sdk
git diff -- packages/plugin-sdk/package.json packages/plugin-sdk/src

Continue only when the API change affects a Guide card, API symbol list, or fixture. If the Guide remains accurate, do not change it.

New public members also require:

  • an experimental_ name, or an Experimental type name;
  • an entry in docs/api_to_audit.md;
  • compatibility with released SDK users unless the user approves the break.

Find the product source

For a visible method, inspect these sources:

  1. The app component that shows the surface.
  2. The slot, collector, or adapter that inserts the plugin content.
  3. The closest app test that defines the real states.

Record stable source paths and anchors in plugins/plugin-api-docs/src/anatomy-manifest.json. Use labels, roles, data attributes, class constants, and state names as anchors. The @bb/app tests check the anchors against the source.

For a method without a visible surface, use the Plugin backend group. Do not invent interface elements.

Add the Guide entry

For a new Guide entry, run the scaffold command with its sources and symbols:

pnpm exec turbo run scaffold:surface-entry --filter=bb-plugin-plugin-api-docs -- \
  --id <stable-id> \
  --title "<visible-product-object>" \
  --group <group> \
  --source <source-path> \
  --api-symbol <exported-name>

Complete the applicable changes:

  • Update plugins/plugin-api-docs/src/surfaces.ts.
  • Prefer an existing card unless the API creates a new product surface.
  • Keep existing surface IDs stable and list each exact exported symbol.
  • Name example plugins in firstParty by display name. A plugin missing from plugins/plugin-api-docs/src/first-party-plugins.json needs a row there; the @bb/scripts tests check each row against the plugin's manifest.
  • For a visible method, update wireframes.tsx and its marker.
  • Match the real ownership, labels, roles, order, states, actions, and outcome.
  • Keep Guide annotations separate from the product interface.
  • Add focused tests for the entry, source anchors, trigger, and outcome.

Read the full file on GitHub · 125 lines

Changes

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.

  1. 20d ago Changed · +2 lines b5a433224b06
  2. 22d ago Changed · +6 lines 7dc2649cd70f
  3. 1mo ago Changed b740c65a73aa
  4. 1mo ago Changed · -77 tokens per session 7f81ca2a0b38
  5. 1mo ago Changed · +27 lines · +15 tokens per session 6de426b58b0d
  6. 1mo ago First seen · 90 lines · 85 tokens per session scan A 16b5017c03a3

Subscribe to this mod's changes

plugin-guide-maintenance 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 1,116 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.

Related

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…

bearlike/Grove · 92 tokens

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…

bearlike/Grove · 100 tokens

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.

bearlike/Grove · 68 tokens

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…

bearlike/Grove · 90 tokens

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…

bearlike/Grove · 118 tokens

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…

bearlike/Grove · 92 tokens