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/cintia09/codenook/routernpx skills add cintia09/CodeNook --skill routergit clone --depth 1 https://github.com/cintia09/CodeNookWhat 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.00000 | $0.00542 |
| Opus 5 | $0.00000 | $0.00271 |
| Sonnet 5 | $0.00000 | $0.00108 |
| Haiku 4.5 | $0.00000 | $0.00054 |
Grade A, and why
router 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
router (builtin skill — self-bootstrap loader)
Role
The first sub-agent dispatched by the main session on every user
turn that isn't pure chit-chat. It self-bootstraps from a fresh context
by reading its own profile + the main-session contract + the workspace
state. (Historically it then handed off to router-triage, which has
been removed in M8.7; the conversational router-agent skill is the
current decision engine.)
CLI
bootstrap.sh --user-input "<text>" [--workspace <dir>] [--task <T-NNN>] [--json]
--user-input— required; the verbatim user utterance the router must triage. Truncated downstream by router-dispatch-build.--workspace— defaults to$CODENOOK_WORKSPACEthen upward search for.codenook/.--task— optional active task id; surfaced verbatim in the envelope even if notasks/<id>/state.jsonexists yet.--json— currently the only output mode.
Files read (in order)
<core>/agents/router.md— own profile (must exist)<core>/core/shell.md— main session contract (must exist)<ws>/.codenook/state.json— installed plugins + active tasks<ws>/.codenook/plugins/<id>/plugin.yaml— for each installed pluginconfig-resolve --plugin __router__— resolves model preference (tier_strongper decision #44)
CN_CORE_ROOT env var overrides the core directory location (used by
tests; defaults to the package root containing this skill).
Exit codes
| code | meaning |
|---|---|
| 0 | bootstrapped, ready (envelope on stdout) |
| 1 | bootstrap failure (missing profile/shell/state) |
| 2 | usage error |
Output schema
{
"role": "router",
"context": {
"active_tasks": ["T-001", ...],
"active_task": "T-007", // null if --task not passed
"installed_plugins": [{"id": "...", "version": "...",
"intent_patterns": [...], "_error": "..."?}],
"model": "opus-4.7"
},
"ready": true
}
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 61 lines · 0 tokens per session scan A ffe9f6fd2ed7
router is a skill published in the GitHub repository cintia09/CodeNook (5 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 542 tokens. 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…