Borrowing it
Nothing to install: this file belongs to lewing/helix.mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/lewing/helix.mcp/main/.copilot/skills/mcp-tool-routing-copy/SKILL.mdgit clone --depth 1 https://github.com/lewing/helix.mcpWrote 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/lewing/helix.mcp/mcp-tool-routing-copy)<a href="https://agentmods.dev/skills/lewing/helix.mcp/mcp-tool-routing-copy"><img src="https://agentmods.dev/badge/skills/lewing/helix.mcp/mcp-tool-routing-copy/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/lewing/helix.mcp/mcp-tool-routing-copy"><img src="https://agentmods.dev/badge/skills/lewing/helix.mcp/mcp-tool-routing-copy.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00033 | $0.00512 |
| Opus 5 | $0.00016 | $0.00256 |
| Sonnet 5 | $0.00007 | $0.00102 |
| Haiku 4.5 | $0.00003 | $0.00051 |
Grade A, and why
mcp-tool-routing-copy 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 11d 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 — 33 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context
Use this when an MCP surface already has the needed tools, but callers still waste rounds because they cannot tell which tool to start with or what to do after a predictable failure. The goal is discoverability through copy, not a bigger tool surface.
Patterns
- Lead with the behavioral contract: what the tool is for, and when it is the right first move.
- If the tool only works for a subset of repos/pipelines/artifact layouts, say that explicitly in the description.
- In failure messages, route to the next concrete tool sequence instead of stopping at “not found” or “unsupported”.
- Keep the routing concise: “use X when / otherwise use Y” beats long implementation detail.
- Mirror the same routing story across related surfaces such as tool descriptions, guide tools, and built-in help text.
- Add regression tests at the copy seam: reflect method-level
DescriptionAttributetext for MCP tools, and assert guide/help section order so routing guidance stays ahead of deep detail. - For false-confidence risks, test both the success-selection copy and the failure-path copy; a warning without the next tool sequence is not enough.
Examples
- A structured-results tool says it parses Helix-hosted results when present, but directs callers to a build-system results API when those files are usually absent.
- A log-search tool says it is the remote-first path for console investigation and points callers to a guide tool for repo-specific search patterns.
- A repo guide adds a short “Start Here” section before deeper details so callers can choose the correct workflow quickly.
- A regression test reflects an MCP method description and asserts it still says “substring search, not regex” plus the repo-specific fallback/selection wording.
- A guide-rendering test verifies the “use AzDO results here” line appears before search-pattern inventories and that the recommended order pivots to structured results before log scraping.
Anti-Patterns
- Warning that a tool “may fail” without naming the fallback tool or workflow
- Burying the workflow choice after long inventories or implementation notes
- Adding a composite tool before tightening the routing copy on the existing tools
- Letting descriptions, guide output, and built-in help drift into different stories
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.
- 11d ago First seen · 33 lines · 33 tokens per session scan A 8a6b0f0e48ce
mcp-tool-routing-copy is a skill published in the GitHub repository lewing/helix.mcp (4 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 512 once invoked, about $0.0002 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-31.
Other skills, from other repositories
diagrams
Mermaid diagrams following the C4 model: context, container, component, sequence, ER and deployment. Use when saying "diagram", "visualize", or "architecture diagram".
e2e
Generate and run Playwright E2E tests traced to spec.md acceptance criteria, with an optional accessibility audit. Use when saying "e2e tests" or "a11y audit".
release-expert
Multi-repo release coordination: version alignment, RC lifecycle, release waves, rollback planning. Use when saying "release", "version alignment", or "cut an RC".
tdd-cycle
Execute full TDD red-green-refactor cycle with validation gates. Use when saying "TDD cycle", "test-driven development", or "full TDD workflow".
debug
Systematic 4-phase debugging with escalation protocol. Use when saying "debug", "investigate bug", "find root cause", "why is this failing", or "fix this bug".
increment
Plan a unit of work as a SpecWeave increment - spec.md with Problem, Scope, numbered ACs and an Approach, plus tasks.md. Use when starting a feature, bug, hotfix or refactor.