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/onboardnpx skills add bugrabilge/bilge-development-kit --skill onboardgit 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.00056 | $0.01384 |
| Opus 5 | $0.00028 | $0.00692 |
| Sonnet 5 | $0.00011 | $0.00277 |
| Haiku 4.5 | $0.00006 | $0.00138 |
Grade A, and why
onboard 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 — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/onboard - Project Onboarding
$ARGUMENTS
Purpose
One command to make your AI assistant fully project-aware. Scans the project, detects tech stack, maps architecture, generates a project-specific CLAUDE.md, initializes Memory Bank, and reports potential issues.
Behavior
When /onboard is triggered:
Phase 1: Tech Stack Detection
Scan for manifest files and detect:
| File | Detects |
|---|---|
package.json |
Node.js, framework (next, react, vue, svelte, express), dependencies, scripts, package manager |
requirements.txt / pyproject.toml / setup.py |
Python, framework (django, fastapi, flask) |
go.mod |
Go, modules |
Cargo.toml |
Rust, crates |
pubspec.yaml |
Flutter/Dart |
Gemfile |
Ruby on Rails |
docker-compose.yml / Dockerfile |
Containerization |
tsconfig.json |
TypeScript config |
.env.example / .env.local |
Environment variables |
Also detect:
- Package manager: lockfile priority (pnpm-lock.yaml > yarn.lock > package-lock.json > bun.lockb)
- Test runner: jest.config, vitest.config, pytest.ini, .mocharc
- Linter: .eslintrc, .prettierrc, ruff.toml, .flake8
- CI/CD: .github/workflows/, .gitlab-ci.yml, Jenkinsfile
- Database: prisma/schema.prisma, drizzle.config, alembic.ini, migrations/
Phase 2: Architecture Mapping
Read the directory structure and identify:
- Entry points: src/index.ts, app/layout.tsx, main.py, cmd/main.go
- Project pattern: monorepo (packages/), feature-based (src/features/), domain-driven (src/domain/), flat
- Key directories: what each top-level directory does
- Config files: summarize important configs (next.config, vite.config, webpack.config)
- API routes: src/app/api/, routes/, controllers/
Phase 3: Key File Summary
Read and summarize (1-2 lines each):
- Entry point files
- Main config files
- Schema/model files (prisma schema, models/, types/)
- Existing README.md (if any)
Phase 4: Generate Project CLAUDE.md
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 · 179 lines · 56 tokens per session scan A 176a42ec286b
onboard is a skill published in the GitHub repository bugrabilge/bilge-development-kit (10 stars, last pushed 4mo ago), licensed MIT. It adds 56 tokens to every session and 1,384 once invoked, about $0.0003 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…