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 github-pr-statusgit 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/github-pr-status)<a href="https://agentmods.dev/skills/get-bb/bb/github-pr-status"><img src="https://agentmods.dev/badge/skills/get-bb/bb/github-pr-status/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/github-pr-status"><img src="https://agentmods.dev/badge/skills/get-bb/bb/github-pr-status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00034 | $0.00535 |
| Opus 5.5 | $0.00014 | $0.00214 |
| Sonnet 5.5 | $0.00007 | $0.00107 |
| Haiku 4.5 | $0.00003 | $0.00053 |
Grade A, and why
github-pr-status 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 today.
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.
What it actually says
GitHub PR Status
The plugin finds the pull request for an environment's current branch by
running gh in the environment's workspace on its machine, so forks, upstream
remotes and the machine's own gh login apply. The composer banner, the Info
panel and sidebar plugins read their PR status from it.
bb pull-request show <environment-id> [--json]
bb pull-request ready <environment-id> [--json]
bb pull-request draft <environment-id> [--json]
bb pull-request merge <environment-id> [--method merge|squash|rebase] [--json]
showprints the PR number, state, branch, attention, checks, review and mergeability.--jsonprints{ "outcome": "available", "pullRequest" },{ "outcome": "absent" }or{ "outcome": "unavailable", "message" }.readyneeds a draft PR,draftneeds an open PR andmergeneeds an open PR GitHub reports as mergeable. Each re-reads the PR first and fails with the reason otherwise.- bb never wakes a machine for PR work. When the environment's machine is
suspended or offline,
showreportsunavailableand the actions fail with a message naming the machine. ghmust be installed and logged in on that machine.
Other plugins read the same data through RPC. pullRequests is a keyed read:
pass up to 200 environment ids and get one row per id. While a client watches
a row, the plugin re-checks it every 30 seconds when checks are pending,
auto-merge is on, the PR is queued or mergeability is unknown. It also
re-checks after a thread on the environment goes idle or the environment's
refs, status or metadata change, and refreshes viewers only when the row
changes.
experimental_useRpcKeyedQuery({
pluginId: "bb--github-pr-status",
contract,
method: "pullRequests",
keys: [environmentId],
});
bb plugin rpc inspect bb--github-pr-status prints the input and output schemas
for pullRequests, markReady, markDraft and merge.
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.
- today First seen · 50 lines · 34 tokens per session scan A 4f8f71670688
github-pr-status is a skill published in the GitHub repository get-bb/bb (4,556 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 535 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-10-23.
Other skills, from other repositories
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…
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…
gl-cli
Use GitLab from the terminal without registering an MCP server. Covers authenticating the zereight-mcp-gitlab CLI (PAT or OAuth device flow) and reading merge requests, diffs, discussions, issues, and pipelines. Use when the user asks about a GitLab MR/issue/pipeline and no GitLab MCP tools are available, or wants…
gitlab-mcp-skill
Use this skill when working with the GitLab MCP server tools for merge requests, issues, repositories, pipelines, work items, variables, dependency proxy, vulnerabilities, webhooks, search, CI catalog, and related GitLab workflows.
connect
Choose which wiki this session uses, the team project's pages on the Nimbalyst server or the project's local wiki of files, and connect a repository to its team project. Use at the start of a task before any wiki tool, when a wiki tool returns reponotbound, ambiguousproject, pinmismatch, projectnotaccessible…
git-commit
Create git commits using Nimbalyst's interactive commit proposal widget. ONLY use when the user explicitly clicks "Commit with AI" button or asks for "smart commit". For regular commit requests, use standard git commands instead.