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-context-scannpx skills add cintia09/CodeNook --skill router-context-scangit 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-context-scan)<a href="https://agentmods.dev/skills/cintia09/codenook/router-context-scan"><img src="https://agentmods.dev/badge/skills/cintia09/codenook/router-context-scan.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.00483 |
| Opus 5 | $0.00000 | $0.00242 |
| Sonnet 5 | $0.00000 | $0.00097 |
| Haiku 4.5 | $0.00000 | $0.00048 |
Grade A, and why
router-context-scan 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 5d 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.
What it actually says
router-context-scan (builtin skill)
Role
Lightweight, fast workspace inventory consumed by the router sub-agent at every triage call. Produces a ≤2KB JSON envelope summarising:
- which plugins are installed (
id+version) - which tasks are active (status != done/cancelled), capped by
--max-tasks - pending HITL queue size
- pending fan-out subtask count (sum of
subtasks[]lengths across active tasks) - workspace warnings (>100MB on disk OR >10K files)
The router uses this output to decide whether to dispatch, ask for confirmation, or escalate to HITL — without needing to walk the workspace itself.
CLI
scan.sh [--workspace <dir>] [--max-tasks N] [--json]
--workspace— defaults to upward search for a.codenook/ancestor; exit 2 if none found.--max-tasks— truncateactive_tasks(default 20).--json— currently the only output format (reserved for future human-readable mode); accepting it is a no-op flag.
Exit codes
| code | meaning |
|---|---|
| 0 | scan complete |
| 2 | usage / workspace not located |
Output schema
{
"installed_plugins": [{"id": "...", "version": "..."}, ...],
"active_tasks": [{"task_id": "T-001", "plugin": "...",
"phase": "...", "last_tick_at": "..."}],
"hitl_pending": 0,
"fanout_pending": 0,
"workspace_warnings": ["..."]
}
Implementation notes
- O(n) scan of
.codenook/plugins/*/plugin.yamland.codenook/tasks/*/state.json; no shell-outs to git/find for size. - File-count and byte-count walks are bounded — they short-circuit once they exceed the warning thresholds (10K files, 100MB).
- Output is shrunk to ≤2KB by truncating
workspace_warningsfirst, then reasons in active_tasks; never the structural fields.
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.
- 5d ago First seen · 58 lines · 0 tokens per session scan A 6b20e5804842
router-context-scan 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 483 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…