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/waelmas/codeplow/kb-onboardnpx skills add waelmas/codeplow --skill kb-onboardgit clone --depth 1 https://github.com/waelmas/codeplowWhat 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.00098 | $0.03173 |
| Opus 5 | $0.00049 | $0.01587 |
| Sonnet 5 | $0.00020 | $0.00635 |
| Haiku 4.5 | $0.00010 | $0.00317 |
Grade C, and why
kb-onboard scanned grade C with 1 finding 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.
Tells the agent never to refusehighAnti-refusal
Suppressing the ability to decline removes a core safety control; a later harmful request then succeeds.
- **Don't refuse.** If you can't find a perfect handoff, work with what's available. Something is always better than nothing. How it starts
The opening of the file, as written. The whole thing — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
kb-onboard - Session Briefing
Read the latest session handoff and project overview to quickly brief yourself (or the agent) on the current state of the project. Lean and fast - get context, then get to work.
Robustness rules (read first)
These rules exist because non-interactive invocations (claude -p "...", Copilot CLI -p, etc.) can end the agent's turn prematurely in the middle of multi-step skills. Rule #6 is the performance rule that matters most on smaller models.
-
Run every Bash call in this skill in the FOREGROUND. Never set
run_in_background: trueon any command here. Background completions can be misread as the end of your turn, causing the skill to terminate after preflight. If you need parallelism (e.g., listing + searching), call the commands sequentially instead. -
Complete Steps 0–5 before handing back control. The briefing in Step 4 is NOT an end-of-turn signal. Always produce it, then continue.
-
If the user's message contained instructions beyond
/kb-onboard, e.g. "/kb-onboard, then answer these questions" or "/kb-onboardand continue the feature" - complete the briefing first, then proceed with those instructions in the SAME turn. Do not stop after the briefing. -
If CLI calls (
obsidian vaults,obsidian vault info=name, etc.) fail or return unexpected values, fall through to filesystem mode immediately (CLI_MODE=0). A contested active-vault (from parallel agents or running scripts) is not a reason to abort - it's a reason to switch tofind/cat/grepon$VAULT_PATHand keep going. -
Emit a deterministic completion marker at the end of Step 5: literally output the line
<!-- kb-onboard:complete -->on its own line as an HTML comment. This tells both humans and downstream tooling that the skill ran to completion, and lets you confidently move on to any remaining instructions. -
FAST PATH when the user provides an explicit vault PATH. If the user's message specifies a filesystem path to the vault (e.g., "The vault is at
/path/to/Foo KB" or "use the vault at~/vaults/Foo"), you have everything you need to skip almost all of this skill. Concretely:- Set
VAULT_PATH=<provided path>,CLI_MODE=0. - Skip Step 0 (preflight), Step 1 (resolution algorithm), Step 1b (Vault Access Sequence) entirely. Do NOT run
command -v obsidian,obsidian vaults, orobsidian vault info=name. - Read exactly TWO files and stop: the newest file in
$VAULT_PATH/Sessions/(use a singlels -t Sessions/ | head -1to pick it), and$VAULT_PATH/Index.md(if present; if not, skip). Do NOT enumerate candidate overview filenames. Do NOT runobsidian search. Do NOT read anyArchitecture/or other vault subdirectories unless the user explicitly asks a follow-up about them. - Emit a one-paragraph briefing (≤ 80 words) capturing TL;DR + Next Steps + one Watch-Out. Do NOT produce the full block-quoted briefing format from Step 4.
- Emit
<!-- kb-onboard:complete -->and continue to any remaining instructions.
- Set
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 · 240 lines · 98 tokens per session scan C a6adc2c39302
kb-onboard is a skill published in the GitHub repository waelmas/codeplow (8 stars, last pushed 4mo ago), licensed MIT. It adds 98 tokens to every session and 3,173 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it C with 1 finding (tells the agent never to refuse). 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…