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/build-fixnpx skills add bugrabilge/bilge-development-kit --skill build-fixgit 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.00692 |
| Opus 5 | $0.00022 | $0.00346 |
| Sonnet 5 | $0.00009 | $0.00138 |
| Haiku 4.5 | $0.00004 | $0.00069 |
Grade A, and why
build-fix 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build Error Resolution Knowledge Base
Domain knowledge for diagnosing and fixing build errors across frameworks and languages.
Error Pattern Database
JavaScript / TypeScript
| Error Pattern | Root Cause | Fix |
|---|---|---|
Cannot find module 'X' |
Package not installed | npm install X / pnpm add X |
Module not found: Can't resolve './X' |
Wrong import path | Check file exists, fix relative path |
has no exported member 'X' |
Wrong named import | Check actual exports, use correct name |
Type 'X' is not assignable to type 'Y' |
Type mismatch | Add type assertion, narrow type, or fix data |
Cannot use JSX unless '--jsx' flag is provided |
tsconfig missing jsx | Add "jsx": "react-jsx" to tsconfig |
Unexpected token '<' |
JSX in .js file | Rename to .jsx/.tsx or configure babel |
ERESOLVE unable to resolve dependency tree |
Peer dep conflict | Use --legacy-peer-deps or align versions |
JavaScript heap out of memory |
Bundle too large | Increase NODE_OPTIONS=--max-old-space-size=4096 |
Python
| Error Pattern | Root Cause | Fix |
|---|---|---|
ModuleNotFoundError: No module named 'X' |
Package not installed | pip install X |
ImportError: cannot import name 'X' |
Wrong import or circular | Check actual exports, fix circular deps |
SyntaxError: invalid syntax |
Python version or typo | Check Python version, fix syntax |
IndentationError |
Mixed tabs/spaces | Normalize indentation |
TypeError: X() got unexpected keyword |
API change | Check library version, update call |
Next.js Specific
| Error Pattern | Root Cause | Fix |
|---|---|---|
'use client' must be added |
Server/client boundary | Add 'use client' directive |
Dynamic server usage |
Static page using dynamic API | Add export const dynamic = 'force-dynamic' |
Hydration mismatch |
Server/client HTML differs | Fix conditional rendering, use suppressHydrationWarning |
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 · 74 lines · 43 tokens per session scan A 0a314b0b3640
build-fix 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 692 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…