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/lee-w/maigo/command-routernpx skills add Lee-W/maigo --skill command-routergit clone --depth 1 https://github.com/Lee-W/maigoWhat 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.00095 | $0.01046 |
| Opus 5 | $0.00048 | $0.00523 |
| Sonnet 5 | $0.00019 | $0.00209 |
| Haiku 4.5 | $0.00010 | $0.00105 |
Grade A, and why
command-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 3d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command Router
Owner: orchestrator
Consumers: Codex sessions only. Claude Code uses commands/ as native slash commands.
Boundary
Codex plugin manifests do not expose Claude Code-style commands/ as native slash commands. Treat this skill as a compatibility shim:
- Improve model-side dispatch for Maigo-shaped input.
- Keep
commands/*.mdas the single source of truth; do not copy command behavior here. - Do not promise slash-command autocomplete, command palette entries, or platform-level interception.
- Prefer
maigo:<name> ...in Codex. A leading/maigo:*may be intercepted before it reaches the model.
Dispatch
Accept all of these forms:
maigo:<name> [arguments...]/maigo:<name> [arguments...]when it reaches the model- Natural language clearly asking to run a Maigo command
For every recognized command:
- Read
../orchestrator-voice/SKILL.mdcompletely. - Read
../narration/SKILL.mdcompletely. - Read
../../commands/<name>.mdcompletely. - Execute the command workflow with the remaining text as its argument string.
- Read every additional skill or agent file required by that command before applying it.
Resolve Maigo-local references from the plugin root:
skills/<skill>/SKILL.md->../<skill>/SKILL.mdfrom this skill directory.agents/<agent>.md->../../agents/<agent>.md.commands/<command>.md->../../commands/<command>.md.${CLAUDE_PLUGIN_ROOT}-> the plugin root two directories above this skill.
Known commands:
| Input | Command source |
|---|---|
maigo:address-comments |
commands/address-comments.md |
maigo:board |
commands/board.md |
maigo:crystallize |
commands/crystallize.md |
maigo:describe-pr |
commands/describe-pr.md |
maigo:doctor |
commands/doctor.md |
maigo:go |
commands/go.md |
maigo:memory |
commands/memory.md |
maigo:quick |
commands/quick.md |
maigo:remember |
commands/remember.md |
maigo:repo-audit |
commands/repo-audit.md |
maigo:retro |
commands/retro.md |
maigo:review |
commands/review.md |
maigo:take-issue |
commands/take-issue.md |
maigo:team |
commands/team.md |
maigo:triage-issue |
commands/triage-issue.md |
What ships with it
1 file 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.
- 3d ago First seen · 86 lines · 95 tokens per session scan A 17d6abd66579
command-router is a skill published in the GitHub repository Lee-W/maigo (14 stars, last pushed 9d ago), licensed MIT. It adds 95 tokens to every session and 1,046 once invoked, about $0.0005 per session on Opus 5. 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-30.
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…