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/juew/skill-routing-kit/skill-routernpx skills add juew/Skill-Routing-Kit --skill skill-routergit clone --depth 1 https://github.com/juew/Skill-Routing-KitWrote 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/juew/skill-routing-kit/skill-router)<a href="https://agentmods.dev/skills/juew/skill-routing-kit/skill-router"><img src="https://agentmods.dev/badge/skills/juew/skill-routing-kit/skill-router.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.00079 | $0.00675 |
| Opus 5 | $0.00039 | $0.00338 |
| Sonnet 5 | $0.00016 | $0.00135 |
| Haiku 4.5 | $0.00008 | $0.00068 |
Grade A, and why
skill-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 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Router
Use this skill as a diagnostic and routing-assistance layer. It does not replace Codex native skill discovery, Superpowers process skills, or subagent orchestration. It helps decide which capabilities are relevant, why they are relevant, and when not to use them.
Boundaries
- Do not execute the user's domain task unless the user asks you to continue after routing.
- Do not assume external connectors are authenticated or can see data.
- Do not treat registry cards as the source of truth. Use them as hints with provenance.
- Do not perform dynamic scanning unless the user asks to refresh or check the registry.
- Prefer local files, local repositories, browser verification, and build/test commands unless the user explicitly names an external app or the source of truth clearly lives there.
When To Use
Use this skill when the user asks things like:
- "Which skill should handle this?"
- "Why did this skill not trigger?"
- "Refresh the skill registry."
- "Review this skill description for trigger quality."
- "List likely skills/plugins for this task."
- "Help me improve skill/plugin hit rate."
When Not To Use
Do not use this skill for simple tasks with an obvious primary skill:
- Editing a local PDF: use the PDF skill.
- Creating a slide deck: use the presentation skill.
- Debugging a failing test: use systematic debugging first.
- Implementing a frontend app: use frontend app building/testing skills.
If the task is complex or ambiguous, perform a brief routing check and then continue with the selected primary skill.
Diagnostic Workflow
- Classify the user request:
- task type: explain, create, edit, debug, analyze, test, review, deploy
- source: local, web, GitHub, Gmail, Drive, Notion, Slack, Figma, Linear
- artifact: code, document, spreadsheet, presentation, PDF, image, webpage, report
- process need: planning, debugging, TDD, verification, review, orchestration
- Read the registry if available.
- Identify recommended skill/plugin candidates.
- Apply local-first and connector-explicit rules.
- Return concise output:
- Recommended skill
- Helper skills
- Why
- Do not use
- Needs confirmation
- If debug mode is requested, include skipped candidates and scoring details.
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.
- 4d ago First seen · 84 lines · 79 tokens per session scan A fe98d31beef3
skill-router is a skill published in the GitHub repository juew/Skill-Routing-Kit (145 stars, last pushed 2mo ago), licensed MIT. It adds 79 tokens to every session and 675 once invoked, about $0.0004 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…