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-dispatch-buildnpx skills add cintia09/CodeNook --skill router-dispatch-buildgit 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-dispatch-build)<a href="https://agentmods.dev/skills/cintia09/codenook/router-dispatch-build"><img src="https://agentmods.dev/badge/skills/cintia09/codenook/router-dispatch-build.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.00540 |
| Opus 5 | $0.00000 | $0.00270 |
| Sonnet 5 | $0.00000 | $0.00108 |
| Haiku 4.5 | $0.00000 | $0.00054 |
Grade A, and why
router-dispatch-build 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
router-dispatch-build (builtin skill)
Role
Builds the canonical dispatch payload that the router sub-agent emits when it decides to hand off to a plugin worker or a builtin skill.
Two responsibilities:
- Construct a JSON payload conforming to architecture §3.1.7:
{role, target, task?, user_input, context: {plugins}}(context.active_phaseis RESERVED for M4 and is currently always omitted — the resolver/orchestrator that owns phase state is not wired into the router until M4.) - Enforce the 500-byte hard limit (decision #T-3) — truncating
user_inputto 200 chars +"..."if needed; failing if the envelope still doesn't fit after truncation. The limit is measured in UTF-8 bytes (CJK-safe). - Audit the dispatch by calling
dispatch-audit emitwith the final payload, so the architectural invariant "every handoff is logged" holds even when the router builds payloads inline.
CLI
build.sh --target <plugin-id|skill-name>
--user-input "<text>"
[--task <T-NNN>]
[--workspace <dir>]
[--json]
--target— required; either an installed plugin id or a builtin skill name. The presence of<ws>/.codenook/plugins/<target>/plugin.yamldeterminesrole(plugin-worker vs builtin-skill).--user-input— required.--task— optional active task id.--workspace— defaults to upward.codenook/search.--json— output mode (currently the only mode).
Exit codes
| code | meaning |
|---|---|
| 0 | payload built + audited; envelope on stdout |
| 1 | manifest missing OR payload still >500 bytes after truncate |
| 2 | usage error |
Output schema (also written to dispatch.jsonl preview)
{
"role": "plugin-worker" | "builtin-skill",
"target": "writing-stub",
"task": "T-007" // omitted if no --task
"user_input": "...", // ≤200 chars, ellipsis if truncated
"context": {"plugins": ["..."]} // active_phase: M4-deferred
}
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.
- 4d ago First seen · 60 lines · 0 tokens per session scan A ba22fee3a258
router-dispatch-build 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 540 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…