Manually route a query to the optimal Claude model (Haiku/Sonnet/Opus)
Manually route queries to specific Claude models (Haiku, Sonnet, or Opus) using the /route command. Use this when you need to override automatic model selection for cost optimization or to ensure maximum capability for complex tasks.
/plugin marketplace add 0xrdan/claude-router/plugin install claude-router@claude-router-marketplaceThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Override automatic model selection and force a specific Claude model for your query.
/route <model> <query>
Where <model> is one of:
haiku or fast - Use Haiku for simple, quick taskssonnet or standard - Use Sonnet for typical coding tasksopus or deep - Use Opus for complex analysisParse $ARGUMENTS to extract the model and query:
| Argument | Executor | Model |
|---|---|---|
haiku or fast | fast-executor | Haiku |
sonnet or standard | standard-executor | Sonnet |
opus or deep | deep-executor | Opus |
/route opus What's the syntax for a TypeScript interface?
Result: Routes to Opus (deep-executor) regardless of query complexity.
/route haiku Fix the authentication bug in login.ts
Result: Routes to Haiku (fast-executor) for cost savings.
/route sonnet Design a caching system
Result: Routes to Sonnet (standard-executor).
If the user doesn't provide a valid model, respond with:
Usage: /route <model> <query>
Models:
haiku, fast - Quick, simple tasks (cheapest)
sonnet, standard - Typical coding tasks (default)
opus, deep - Complex analysis (most capable)
Example: /route opus Analyze the security of this authentication flow