Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add melodic-software/claude-code-plugins/plugin install multi-agentWrote 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/melodic-software/claude-code-plugins/route)<a href="https://agentmods.dev/skills/melodic-software/claude-code-plugins/route"><img src="https://agentmods.dev/badge/skills/melodic-software/claude-code-plugins/route/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/melodic-software/claude-code-plugins/route"><img src="https://agentmods.dev/badge/skills/melodic-software/claude-code-plugins/route.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.00135 | $0.01063 |
| Opus 5.5 | $0.00054 | $0.00425 |
| Sonnet 5.5 | $0.00027 | $0.00213 |
| Haiku 4.5 | $0.00014 | $0.00106 |
Grade A, and why
route 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 13d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Workflow scripts and orchestrating skills read their model and effort choices
from here, so the choice lives in one role map with a recorded basis per
default, and a team or a person can change it without editing any script.
Keys, layers and the fan-out guard are owned by
${CLAUDE_PLUGIN_ROOT}/reference/config.md.
Arguments
<role|all>: one oforchestrator,worker,verifier,retrieval, orallfor the whole map.code|research|mechanical: optional workload; applies the role'sworkloads.<w>keys (research lowers the worker's effort by default).session=<alias>: the session model's alias. When the caller did not pass one, fill it from your own model ID: the family name in it (opus,sonnet,haiku,fable) is the alias. When you cannot tell, omit it; the resolver then treats the session as frontier, which keeps fan-out stages off the session model.
Run
${CLAUDE_SKILL_DIR}/scripts/route.sh $ARGUMENTS
Append session=<alias> when $ARGUMENTS carries none and you know your model
family.
Output
The JSON exactly as printed, in one fenced json block. Below it, one line per
role in this form:
<role>: single <model|inherit: omit the model option> @ <effort>; fanout <model|inherit: omit the model option> @ <effort>
Write inherit: omit the model option wherever a variant's omit_model is
true, so a caller copying the line passes no model and the agent runs on the
session model. Then list every entry of notes (a skipped layer, a rejected
value, an ignored key) as written. Exit 2 means an unknown role or argument:
relay the valid roles from the error and stop.
A caller launching a workflow passes the JSON's roles object as
args.roles, unchanged.
What this skill does NOT do
- Write any configuration layer. That is
/multi-agent:setup apply. - Route a named agent. An agent dispatched by its own type, such as
implementation:implementer,implementation:scoped-implementerorimplementation:phase-verifier, owns its tier through its own frontmatter and its dispatcher's rules. The map governs genericagent()calls and Agent dispatches without a named type. - Choose between a workflow and subagents. That is
/multi-agent:assess. - Check the defaults against upstream. That is
/multi-agent:audit-defaults.
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.
- 13d ago First seen · 91 lines · 135 tokens per session scan A 7f4f7718661e
route is a skill published in the GitHub repository melodic-software/claude-code-plugins (25 stars, last pushed today), licensed MIT. It adds 135 tokens to every session and 1,063 once invoked, about $0.0005 per session on Opus 5.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-10-03.
Other skills, from other repositories
parallel-orchestrator
Manage parallel Claude Code workstreams using git worktrees. Use when: splitting large tasks across multiple workers, coordinating parallel development, monitoring worker progress, integrating completed work, analyzing work item documents (code reviews, issue lists). Triggers: parallel, orchestrator, worktrees…
parallel-worker
Execute focused implementation tasks in a parallel workflow. Use when: working on assigned files in a worktree, making checkpoint commits, signaling dependencies or blockers, completing orchestrator-assigned tasks. Triggers: worker, checkpoint, worktree, assigned scope, commit prefix, parallel task.
optimize-local-search
For NP-hard optimization: TSP, scheduling, assignment problems. Uses greedy construction + local improvement (2-opt, hill climbing).
pass-function-as-arg
For generic algorithms: strategy pattern, callbacks, configurable behavior. Pass functions as parameters to customize algorithm behavior.
solve-constraint-puzzle
For constraint satisfaction: Sudoku, scheduling, N-queens, logic puzzles, SAT-like problems, assignment problems. Uses propagate-then-search pattern.
test-with-examples
For example-driven development: test cases as specifications, input/output pairs, documentation through examples.