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/router-agentnpx skills add cintia09/CodeNook --skill router-agentgit clone --depth 1 https://github.com/cintia09/CodeNookWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/cintia09/codenook/router-agent)<a href="https://agentmods.dev/skills/cintia09/codenook/router-agent"><img src="https://agentmods.dev/badge/skills/cintia09/codenook/router-agent.svg" alt="Measured on agentmods" height="20"></a>What 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.01282 |
| Opus 5 | $0.00000 | $0.00641 |
| Sonnet 5 | $0.00000 | $0.00256 |
| Haiku 4.5 | $0.00000 | $0.00128 |
Grade A, and why
router-agent 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 4d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
router-agent (builtin skill — M8.2)
Role
Per-turn entry point the main session calls to dispatch a real subagent
for conversational task creation. The router-agent is the SOLE
domain-aware component on the task-creation side (see
docs/router-agent.md §2).
This skill ships:
| File | Purpose |
|---|---|
spawn.sh |
CLI entry the main session invokes once per user turn. Thin shell wrapper around render_prompt.py. |
render_prompt.py |
Deterministic context-prep + handoff helper. Acquires the per-task fcntl lock, mutates tasks/<tid>/, renders the system prompt, and on --confirm materialises state.json and runs the first orchestrator-tick. |
prompt.md |
Long-form system-prompt template for the spawned subagent. |
schemas/ |
M5 YAML DSL schemas for the four canonical files (shipped in M8.1). |
Layering reminder
spawn.sh does not call an LLM. Its job is the deterministic
context-prep + handoff envelope: it writes a fully-rendered prompt to
tasks/<tid>/.router-prompt.md and emits a JSON envelope that tells
the main session "go spawn a Task subagent with this prompt". The
subagent itself writes back to router-context.md / router-reply.md
/ draft-config.yaml; the next spawn.sh invocation observes the
new state.
This split keeps spawn.sh portable across host runtimes (Claude Code Task tool, Copilot CLI task tool, plain shell) while pinning all domain logic inside the subagent prompt.
Inputs
| Flag | Required | Meaning |
|---|---|---|
--task-id <T-NNN> |
yes | Task id to operate on (creates tasks/<tid>/ if absent). |
--workspace <path> |
yes | Workspace root. Tasks live under <ws>/.codenook/tasks/, plugins under <ws>/.codenook/plugins/. |
--user-turn <text> |
no | The user's latest utterance (omit on initial spawn before any user input). |
--user-turn-file <path> |
no | Same as --user-turn but read from a file (avoids shell-quoting hazards). |
--confirm |
no | Handoff mode: validate the current draft-config.yaml, materialise state.json, and run the first orchestrator-tick. |
What ships with it
7 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.
- 4d ago First seen · 103 lines · 0 tokens per session scan A 00346e0618c5
router-agent 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 1,282 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…