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/bugrabilge/bilge-development-kit/reviewnpx skills add bugrabilge/bilge-development-kit --skill reviewgit clone --depth 1 https://github.com/bugrabilge/bilge-development-kitWhat 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.00043 | $0.00838 |
| Opus 5 | $0.00022 | $0.00419 |
| Sonnet 5 | $0.00009 | $0.00168 |
| Haiku 4.5 | $0.00004 | $0.00084 |
Grade A, and why
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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/review - Code Review
$ARGUMENTS
Purpose
This command performs a structured code review on specified files, directories, or recent changes.
Sub-commands
/review - Review all staged/unstaged changes
/review [file/dir] - Review specific file or directory
/review pr - Review current PR changes
/review security - Security-focused review
/review performance - Performance-focused review
Behavior
When /review is triggered:
-
Identify scope
- What files/changes to review
- Auto-collect context using tools:
- Run
git branch --show-current - Run
git diff --cached --stat - Run
git diff --stat - Run
git log --oneline -5
- Run
-
Multi-agent analysis Invoke relevant agents based on file types:
File Pattern Agent Focus *.tsx, *.jsx, *.cssfrontend-specialistComponent quality, a11y, performance *.ts (server), *.pybackend-specialistAPI design, security, error handling *.test.*test-engineerTest quality, coverage gaps prisma/*, migrations/*database-architectSchema quality, query performance Dockerfile, CI/*devops-engineerConfig quality, security All files security-auditorVulnerabilities, secrets, OWASP -
Synthesize findings
- Combine all agent findings
- Prioritize by severity
- Provide actionable fixes
Output Format
## Code Review Report
### Scope
[Files reviewed, line count]
### Summary
| Severity | Count |
|----------|-------|
| Critical | X |
| Warning | X |
| Info | X |
### Findings
#### Critical
1. **[File:Line]** - [Issue description]
- Why: [Explanation]
- Fix: [Code suggestion]
#### Warnings
1. **[File:Line]** - [Issue description]
- Fix: [Suggestion]
#### Suggestions
1. **[File:Line]** - [Improvement idea]
### Verdict
[APPROVE / REQUEST CHANGES / NEEDS DISCUSSION]
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 · 135 lines · 43 tokens per session scan A 5df2d4b03bec
review is a skill published in the GitHub repository bugrabilge/bilge-development-kit (10 stars, last pushed 4mo ago), licensed MIT. It adds 43 tokens to every session and 838 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-31.
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…