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/braintrustdata/bt/bt-reviewnpx skills add braintrustdata/bt --skill bt-reviewgit clone --depth 1 https://github.com/braintrustdata/btWhat 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.00081 | $0.01401 |
| Opus 5 | $0.00041 | $0.00700 |
| Sonnet 5 | $0.00016 | $0.00280 |
| Haiku 4.5 | $0.00008 | $0.00140 |
Grade A, and why
bt-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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLI Best Practices Review
Audit the bt CLI codebase against two reference documents:
- clig.dev guidelines — industry CLI best practices
- bt codebase patterns — established internal conventions for consistency
When to Use
- When a user asks to review, audit, or check the CLI
- When triggered via
/bt-review - After implementing new commands or subcommands
- Before releases to ensure CLI quality
Review Process
1. Scope the Review
Determine what to review:
- Full audit: All commands and subcommands
- Targeted review: Specific command or area (e.g., just
prompts, just error handling) - Diff review: Only changed files on the current branch vs main
To scope a diff review, run git diff main --name-only -- '*.rs' and focus on changed files.
2. Load Reference Documents
Read both reference files:
references/clig-checklist.md— industry CLI guidelines organized by categoryreferences/bt-patterns.md— established codebase patterns to check for consistency
3. Analyze Source Code
clig.dev Compliance
For each category in the checklist, examine relevant source files:
- Args & flags: Read
src/args.rsandsrc/main.rs— check clap derive attributes, flag naming, long/short forms - Help text: Check all
#[command]and#[arg]attributes for descriptions, examples, and help templates - Error handling: Grep for
anyhow::,.context(,eprintln!, and error types — verify human-readable messages - Output: Check stdout vs stderr usage, TTY detection, color handling, JSON output support
- Subcommands: Review
src/*/mod.rsfiles for consistency in naming and structure - Interactivity: Check
dialoguerusage for TTY guards and--no-inputsupport - Robustness: Look for timeout handling, progress indicators (
indicatif), signal handling - Config: Check env var handling (
dotenvy,clapenv features), XDG compliance
Pattern Consistency
Compare new or changed code against references/bt-patterns.md. Check:
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 132 lines · 81 tokens per session scan A e123294815ef
bt-review is a skill published in the GitHub repository braintrustdata/bt (13 stars, last pushed 5d ago), licensed Apache-2.0. It adds 81 tokens to every session and 1,401 once invoked, about $0.0004 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…