Junior Toolbox: local models supervised by Opus
A toolbox for an Android agent: skills, official Google MCPs and a bridge to local models via LM Studio. Up to 70% token savings.
I’m working on a fun thing right now — the Junior Toolbox.
The idea: you download a Toolbox (haven’t picked a name yet) with a base kit for an Android development agent.
In my case that’s:
- skills based on superpowers
- Android CLI (the official skills and MCPs from Google itself)
- a set of architecture practices (actual MVI-MVVM pattern examples with sample classes)
- and the coolest part — a bridge to local models via LM Studio
How does it work?
You have great skills, and expensive Opus uses them to create tasks. These tasks are fairly simple (say, create a class with fields).
Why burn Opus tokens when a local LLM can handle it?
So my box has a smart Opus that supervises its underlings — local models: hands out assignments, gives feedback, and once it verifies everything is fine, delivers the result to the customer, i.e. you.
The hardest tasks like brainstorming stay strictly with Opus.
The result is up to 70% token savings. Sounds like magic, doesn’t it?
Everything works already, but there are rough edges. More on that later.
And the best part: you can put anything into this toolbox.
A new person joins your team, and you just tell them: install this box via brew. A friendly wizard helps set everything up — et voilà, you know for sure they’ll produce good results, because you control and extend the tool set based on your own expertise.
Let’s call it — the Junior Toolbox 😎