Stop Sending Opus to Do Haiku's Job: Task-Aware Model Routing via MCP

Every Claude Max user has the same problem. $200/month, and they burn Opus tokens on tasks that Haiku could handle in milliseconds. You ask Claude to rename a variable. Opus handles it. You ask it to list files in a directory. Opus again. You ask it to architect a distributed system. Opus. Every task gets the same model, the same cost, the same latency. No layer exists between you and the model that says: "this task is simple, route it to the cheap model." Until now. The Problem: One Model Fits All Claude Code picks the model. You don't. And it has no concept of task weight. A typo fix and a system redesign both get Opus. That's like hiring a surgeon to put on a band-aid. The cost difference is real: Haiku : ~$0.001 per task Sonnet : ~$0.01 per task Opus : ~$0.10 per task If 60% of your daily tasks are Haiku-grade, you're burning 100x more than you need to on those tasks. The Solution: classify_task_complexity We built an MCP tool that scores every task across 6 dimensions before it to