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/auditnpx skills add bugrabilge/bilge-development-kit --skill auditgit 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.00048 | $0.01640 |
| Opus 5 | $0.00024 | $0.00820 |
| Sonnet 5 | $0.00010 | $0.00328 |
| Haiku 4.5 | $0.00005 | $0.00164 |
Grade A, and why
audit 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 2d 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 — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/audit - Codebase Audit
$ARGUMENTS
Purpose
Project-wide codebase health analysis. Unlike /review (file/PR focused), /audit examines the entire project: architecture patterns, dependency risks, complexity hotspots, and tech debt.
Sub-commands
/audit - Full audit (all dimensions)
/audit architecture - Architecture patterns and violations
/audit dependencies - Dependency graph, outdated/vulnerable packages
/audit complexity - Cyclomatic complexity hotspots
/audit tech-debt - Tech debt inventory with effort estimates
/audit size - File/module size analysis
Behavior
When /audit is triggered:
1. Project Discovery
Auto-collect project context using Read, Glob, and Grep tools:
- Tech stack: Read
package.json,pyproject.toml,go.mod,Cargo.toml - File count: Use Glob to count source files
- Lines of code: Use Bash with simple commands (no pipes)
- Recent commits: Use
git log --oneline -10
2. Architecture Audit
Analyze project structure for:
| Check | What to Look For |
|---|---|
| Pattern consistency | Is it feature-based, domain-driven, or flat? Are there violations? |
| Circular dependencies | Import cycles between modules |
| Layer violations | UI importing from DB layer, utils importing from features |
| Dead code | Exported but never imported files/functions |
| Config sprawl | Too many config files at root level |
| Entry point clarity | Is the app's starting point obvious? |
3. Dependency Audit
# Node.js
npm audit 2>/dev/null || true
npm outdated 2>/dev/null || true
# Python
pip audit 2>/dev/null || true
pip list --outdated 2>/dev/null || true
# General
cat package-lock.json 2>/dev/null | python3 -c "import json,sys; d=json.load(sys.stdin); print(f'Total deps: {len(d.get(\"packages\",{}))}')" 2>/dev/null || true
Check for:
- Vulnerable packages — known CVEs
- Outdated majors — 2+ major versions behind
- Abandoned packages — no updates in 2+ years
- Duplicate packages — same functionality, different libs
- Bundle impact — largest dependencies by size
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.
- 2d ago First seen · 215 lines · 48 tokens per session scan A 9559708d4d83
audit is a skill published in the GitHub repository bugrabilge/bilge-development-kit (10 stars, last pushed 4mo ago), licensed MIT. It adds 48 tokens to every session and 1,640 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.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…