Borrowing it
Nothing to install: this file belongs to lglucas/ai-dev-operating-system. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/lglucas/ai-dev-operating-system/main/.claude/commands/bp-review.mdgit clone --depth 1 https://github.com/lglucas/ai-dev-operating-systemWrote 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/commands/lglucas/ai-dev-operating-system/bp-review)<a href="https://agentmods.dev/commands/lglucas/ai-dev-operating-system/bp-review"><img src="https://agentmods.dev/badge/commands/lglucas/ai-dev-operating-system/bp-review.svg" alt="Measured on agentmods" 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.00045 | $0.00084 |
| Opus 5 | $0.00023 | $0.00042 |
| Sonnet 5 | $0.00009 | $0.00017 |
| Haiku 4.5 | $0.00005 | $0.00008 |
Grade A, and why
bp-review 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 7d 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.
What it actually says
/bp-review
Run BP revision after user feedback: apply corrections, run impact review, produce BP v0.0.2, update changelog and session log.
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.
- 7d ago First seen · 8 lines · 45 tokens per session scan A f01c7791960e
bp-review is a command published in the GitHub repository lglucas/ai-dev-operating-system (11 stars, last pushed 29d ago), licensed MIT. It adds 45 tokens to every session and 84 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 commands, from other repositories
cost-report
Generate a local Claude Code cost report from the ECC cost-tracker metrics log.
slack-gif-creator
Toolkit for creating animated GIFs optimized for Slack, with validators for size constraints and composable animation primitives. This skill applies when users request animated GIFs or emoji animations for Slack from descriptions like "make me a GIF for Slack of X doing Y".
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first.
sap-fi-closing
A step-by-step checklist for closing SAP Financial Accounting records at the end of a month or year. It covers accounting periods, unpaid invoices, assets, foreign currencies, journal entries, and financial-statement checks.
estimate-gcp-cost
Estimate GCP resource costs and provide optimization recommendations.
delegate-claude
Delegate to local Claude Code (Grok background task; live tools in task log).