Add plugin entry: agent-plugins

[patleeman]

What the plugin does

Agent Plugins installs packages that follow the Agent Plugins spec once in BB, materializes their skills for agent sessions, and routes approved MCP tools to Codex and other BB providers. The release adds independent enable/disable controls for each discovered skill and MCP server. It is not a Claude marketplace integration.

Source release

• Repository: https://github.com/patleeman/bb-plugins.git
• Plugin subdirectory: packages/bb-plugin-agent-plugins
• Release: agent-plugins/v0.1.0
• Selected source range: ^0.1.0

Plugin checks

• 33 focused tests passed
• TypeScript typecheck passed
• BB plugin build passed
• BB SDK compatibility check passed
• npm pack --dry-run contains the runtime bundles, metadata, manifest, and schemas
• Live BB reload and per-resource toggle checks passed

Marketplace checks

• npm ci --ignore-scripts passed
• npm run build passed
• npm run check passed, including public Git release liveness
• Entry ID, source subdirectory, release tag prefix, and host icon validated against the current marketplace schema

Permissions and security

The plugin reads plugin sources and stores installed plugin data under BB-managed storage. Skills are materialized only when enabled. MCP servers remain approval-gated; enabled stdio servers run user-selected plugin commands, and supported local HTTP configuration is validated before use. Sensitive MCP environment and header values are redacted from the settings snapshot.

[SawyerHood]

Automated note from a Claude Code agent, posted on behalf of the marketplace maintainer.

Thank you for the Agent Plugins work. We are rejecting this version for now because it cannot activate on the current BB SDK.

• SDK 0.4.16 rejects experimental_statusLabels during tool registration (server.ts:265, server.ts:273).
• The entry range selects only agent-plugins/v0.1.0.
• Later tags remain outside that range, and v0.2.2 still uses the old field.

Please use presentation.labels, raise the SDK floor, and publish a new matching tag. Then verify that the exact marketplace source reaches the running state.

[SawyerHood]

Automated note from a Claude Code agent, posted on behalf of the marketplace maintainer.

We are requesting changes for the reasons in the automated review comment above. Please reply after a new matching release is available.

[patleeman]

Thanks for the review — a matching release is now available.

Fix: experimental_statusLabels is replaced with presentation.label at all six tool registrations (server.ts). The plugin activates cleanly against the current SDK surface.

Release: agent-plugins/v0.3.0 (commit 3d2ff7f) is pushed to the public repository. The entry now tracks ^0.3.0, which resolves to that tag; earlier tags (v0.1.x–v0.2.x) are outside the range.

SDK floor: raised to bbPluginSdk >=0.4.16, devDependency repinned to @get-bb/plugin-sdk@0.4.21.

Verification:

• 63 focused tests pass, including suite installs that activate the real server under the 0.4.21 SDK test harness (tool registration with presentation.label accepted).
• TypeScript typecheck, bb plugin build, and npm pack --dry-run artifact checks pass.
• Marketplace branch revalidated after rebase onto current main: npm run build and npm run check (including public Git release liveness) pass; the catalog entry resolves to tag agent-plugins/v0.3.0, commit 3d2ff7f.
• Install attempt from this exact marketplace source on a host running SDK 0.4.15 is refused by the engines guard ("requires bb plugin SDK >=0.4.16"), confirming the floor behaves as intended. A live running-state check on an SDK >=0.4.16 host is still pending on my side; I'll follow up once complete.