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 commands/syz-coder/codebase-knowledge-wiki/crate-router-mapgit clone --depth 1 https://github.com/SYZ-Coder/codebase-knowledge-wikiWhat 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.00016 | $0.00298 |
| Opus 5 | $0.00008 | $0.00149 |
| Sonnet 5 | $0.00003 | $0.00060 |
| Haiku 4.5 | $0.00002 | $0.00030 |
Grade A, and why
crate-router-map 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.
This is a copy
88% identical to build-domain-map — 10 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Use the backend service spec skill as the primary workflow.
Read the skill source from the first available location:
.claude/skills/backend-service-spec-skill/SKILL.mdskills/backend-service-spec-skill/SKILL.mdai-skill-lib/backend-service-spec-skill/SKILL.mdbackend-service-spec-skill/SKILL.md
If the route crosses frontend, mobile, Python, task, bridge, callback, webhook, or mixed-stack boundaries, also read the cross-tech-stack extension from the first available location:
.claude/skills/cross-tech-stack-spec-skill/SKILL.mdskills/cross-tech-stack-spec-skill/SKILL.mdai-skill-lib/cross-tech-stack-spec-skill/SKILL.mdcross-tech-stack-spec-skill/SKILL.md
Then execute the crate_router_map workflow for:
$ARGUMENTS
Generate route artifacts under mydocs/routermap/ unless the user gives another path. Split synchronous calls, asynchronous messages, scheduled or compensation links, and realtime channels. Mark each segment as fact-closed, fact-send-side, fact-receive-side, contract-visible, or clue.
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 · 29 lines · 16 tokens per session scan A 09752bc3b731
crate-router-map is a command published in the GitHub repository SYZ-Coder/codebase-knowledge-wiki (9 stars, last pushed 2mo ago), licensed MIT. It adds 16 tokens to every session and 298 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to build-domain-map, differing in 10 lines, and is treated as a copy.
Other commands, from other repositories
android
Command "android" from zhagqn/agentwork, covering /android [subcommand] [args] and 执行前必读.
compose-test
Run Compose UI tests with Espresso. Verify critical user flows.
app-store-audit
Run an enterprise pre submission compliance audit on an iOS or Android app against Apple App Store and Google Play rejection rules. Pass a project path or run from the project root.
build-verify
Run the full build / test / analyze / format verification pass for this Flutter app.
mobile-performance-check
Analyze mobile app for performance issues using the mobile-best-practices database.
swift-feature
Implement a new Swift feature end-to-end: analysis, confirmation, implementation, and build validation.