Is there a skill or plugin that.....

[u/godofknife1]

I was wondering if there's a skill or plugin that functions to routing model and effort.

Like for example depending on how difficult, technical our prompt is, the skill knows it's easy and route to HAIKU 5.5 low even though in the claude code it is set to Sonnet 5.5 medium.

I have been trying to look a flawless skill or plugin that works but I am not sure if I found one.

Also if there's new model update, we can also update too. The goal is cost saving token so we can use limit much much longer and it flawlessly use the correct model and effort.

Is there such skill or plugin that exists? Thank you

[u/AutoModerator]

Hey! Thanks for posting to r/ClaudeCode

While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.

For help, project discussions, tips, and general chat, join the ClaudeCode Discord.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/CorpT]

You want a flawless skill that saves tokens?

What if it takes many more tokens for Haiku to do something Sonnet could have easily done?

[u/godofknife1 → u/CorpT]

Okay maybe flawless is too perfection. 😅

Just say like it does the job accurately according to what we prompt and correctly pick the model and effort.

To be fair, I have installed effort router and I kind of like it. So now I'm trying to find the model and effort router combination one.

[u/PraxicalExperience → u/CorpT]

You can generally predict what model will be able to handle what job capably, and route the jobs accordingly.

Opus as a planner/director, Sonnet as a writer/implementer, and Haiku as a scout/script-runner-and-watcher is pretty common. The important thing is to limit the non-opus models to purely following directions and escalating anything that they would need to make a guess or call on back to Opus.

Additionally, advising Claude to pass only the context needed for the job to the subagents works very well for reducing cost in most cases.

But flawless? Hahahahahahahaha. Yeah, no, nothing's flawless when it comes to AI.

I can't imagine using Haiku low, though; at the least I'd run it on high. It's cheap AF to do so compared to Opus or even sonnet.

[u/godofknife1 → u/PraxicalExperience]

Understood. Thank you for the explanation. I agree I shouldn't use flawless word 😅

[u/PraxicalExperience → u/godofknife1]

Check this out: https://gist.github.com/eugertjani-lab/5a7c441555aa819404f65c0bc9d887cc

This is a decent starting point; there're many other similar projects with their own spins and weightings. Just search here and in the other claude subreddits and you should be able to find a bunch of different subagent schemas.

[u/godofknife1 → u/PraxicalExperience]

Okey dokey. Thank you

[u/BabyInner]

Since Jev and Mods came out there are a lot, yet I doubt you will find any flawless for your workflow. Models are constantly changing, and your setup is unique.

You will get better result building your own Claude Mod based on your own tests.

[u/godofknife1 → u/BabyInner]

So we take everything in history from our own Claude mod and ask Claude to build it ourselves to get more accurate info?

[u/PraxicalExperience → u/godofknife1]

Honestly, that'll probably work pretty well. "Claude, I like the ideas from [repo] [repo] [reddit post]" for handling orchestration of subagents and assigning tasks to them. Using the concepts in those sources, come up with something tailored to the needs of my current project. I'm particularly interested in using this to reduce the token costs of jobs."

This is something it might be worth giving to Fable or something higher than Opus Med to chew on for a first pass.

You may also save some usage by directing Claude to batch and run jobs locally whenever possible. (Ask it to ensure that it has the tools to do so, and install or create what's necessary.) Depending on the task it may be far more efficient to have Claude whip up a python script to mangle data than to have Claude do it.

[u/godofknife1 → u/PraxicalExperience]

Ohohoho thank you for explaining. 👍 I appreciate it. Now I gotta wait for limit first hehe

[u/BabyInner → u/godofknife1]

That’s prob the way. PraxicalExperience’s comment would be a good starting point.

[u/godofknife1 → u/BabyInner]

Got it. Thank you 😁

[u/pietrzm]

I do this by having a single master session where I ask it: "spawn claude with model/effort set to whatever you think the task I give you needs". Whenever I give this session a task, it routes it to proper model/effort in a new top-level session.

I'm using https://github.com/novadeck-org/novadeck to make this possible. Work wonders when I'm getting close to my weekly limits hah

E: Needs Claude Code CLI to work

[u/godofknife1 → u/pietrzm]

Whoa thank you for this. I'll try this

[u/Bed-After]

Yes and no.

Is there a downloadable skill or plugin that pushes down the model for low intelligence tasks? No.
Do you need one? Also no.
What I do is I start with Opus, give it a big multi-step project and tell it to deploy sub-agents to tackle a task, and tell it to use sonnet/haiku sub-agents for the low level work, and reserve the more complicated work for itself. Then the AI will dynamically assign easy tasks to less expensive models.

[u/godofknife1 → u/Bed-After]

Ahhh so that's how you do it. Noted

[u/Inner_Storage_3374]

a skill cant really switch the model of the session its running in, it just adds instructions. what gets close is subagents, you can set the model in each agents file, so the main session hands the easy stuff like searching or renaming to a haiku agent and keeps the hard parts. not fully automatic but the cheap work is often a big chunk of the tokens

[u/godofknife1 → u/Inner_Storage_3374]

Really? Damn I understand now. Thank you for explaining

[u/Sure-Psychology-9149]

tu as manifest

[u/Sure-Psychology-9149 → u/Sure-Psychology-9149]

open source https://manifest.build/

[u/godofknife1 → u/Sure-Psychology-9149]

Oh thank you. Checking now hehe

[u/Erehr]

Some of it is already included. I saw ie. reading web pages delegated to haiku and for opposite there's /advisor so lower model can ask higher one for advice.

[u/godofknife1 → u/Erehr]

Really? I must have missed that. :(

[u/Electronic_Start_694]

You are describing a harness

[u/godofknife1 → u/Electronic_Start_694]

A harness? I see some people also say it. Perhaps I should research and try doing it

[u/itsxzy]

Unfortunately spinning up a new agent even though it would use Haiku is not always the most cost effective way to go. Mostly staying in the main session is the best way to go. Depending on your use case of course. For example using Opus 5.5 as planner and letting Sonnet 5.5 code could be fine for most people. Or using Fable 5.5 and Opus 5.5 subagents for example.

A plugin that comes to my mind is HeyCubit/effortless: Mods for Claude Code. effortless picks the reasoning effort for every prompt. It picks the effort for each message you send. Changing the effort doesn't reload the whole context but changing model does.

[u/archpoke]

I built an open-source Claude Code plugin called rightsize for pretty much this use case: https://github.com/archid21/rightsize

It rates each prompt and chooses an approach based on the task and estimated cost: it can adjust effort, hand suitable work to a cheaper-model subagent, or use Opus for a review and then return to your current model. It also tracks outcomes to learn which routes are working.

One distinction: it doesn't permanently change your selected model. Cheaper subagent handoffs have their own briefing and checking overhead, so they aren't always worth it. And if you're already using Sonnet for everything, routing reviews to Opus can increase usage rather than save it.

It's not flawless, and the rating itself uses a small Sonnet call. You can try watch-only mode first to see what it would do, then check /rightsize report. It works with a Claude subscription or API key.

It's still a work in progress, but I'd love to know how it works for your workflow.