yukti

Yukti

A lightweight Claude Code plugin that routes each pipeline stage to the right model — Haiku to explore, Opus to plan + review, Sonnet to implement. Claude Code stays the same to use; you just type /yukti:smart <task> instead of letting one model do everything.

Target savings: ~50% cost reduction vs always-Opus on routine code work, with quality on par for that workload. Numbers below are illustrative — real measurement lands in v0.2.0. The architecture is designed for it; the receipts are still being collected.

If you've seen plugins claim "80% token savings," they're either measuring cost (not tokens) or compromising on quality. This README won't make that mistake. We will publish measured numbers from real-world usage when we have them, not before.

Composes with the ecosystem. Yukti is the routing layer. For cross-session memory install claude-mem. For structural code review with blast-radius analysis install code-review-graph. We don't try to be everything.

---

What it does

It splits a coding task across four specialist subagents, each running on the cheapest model that can do that step well:

Step	Subagent	Model	Why this model
1. Locate files	explorer	Haiku	Fast, cheap, good enough for grep + glob
2. Plan phases	planner	Opus	Long-horizon reasoning matters here
3. User confirms	(you)	—	The quality firewall
4. Implement each phase	implementer	Sonnet	Near-Opus on focused tasks, much cheaper
5. Verify	hook + Bash	—	Typecheck/test gate
6. Review	reviewer	Opus	Catches what Sonnet missed

The orchestrator (smart-orchestrator, also Opus) runs on a deliberately tiny tool set — only Agent, Read, Bash — so it physically cannot do the work itself. It can only delegate.

Why it works

This plugin is the codification of practices that Claude itself recommended for making Sonnet punch above its weight:

• One phase per session. Sonnet's coherence drops on long horizons. Each phase = a fresh implementer invocation with a tight context.
• Files are pre-resolved. The implementer subagent has no Grep or Glob tool — it cannot wander. Files are given to it by the planner.
• Edit, don't rewrite. Hard rule in the implementer's system prompt. Sonnet's rewrite urge is real and expensive.
• Mandatory plan review. The orchestrator will not skip the user-confirmation step. This is the single highest-leverage quality gate in the system.
• Verification at every phase. The implementer runs the phase's verification command and reports. The Stop hook is a safety net.
• Read caps. A PreToolUse hook injects limit: 500 on any Read call without an explicit limit. Prevents accidental 5000-line reads.

Install

Plugin marketplace — recommended for almost everyone

Run inside any Claude Code session:

/plugin marketplace add akii09/yukti
/plugin install yukti@akii09-yukti

Yukti is installed once at the user level and available across every project you open with Claude Code. Skills are namespaced (/yukti:smart, /yukti:status, /yukti:plan, /yukti:review) so they never collide with other plugins or future built-in commands.

To upgrade later:

/plugin upgrade yukti

When to choose another path

Your situation	Use this
Normal user, want savings on every project	Marketplace install above ✅
Locked-down env (corporate proxy, no marketplace, CI runner)	Fallback installer (below)
You want to enforce Yukti for every contributor of one specific repo	Fallback installer, commit .claude/ to that repo
Plugin development / quick eval against a fork	claude --plugin-dir ./yukti (below)

Fallback — per-project install (no marketplace required)

Drops the agents, skills, hooks, and bin scripts into the current project's .claude/ directory. Skills are not namespaced in this mode — they're invoked as /smart, /plan, /explore, /implement, /review. That means autocomplete won't surface them under /yukti, and they may collide with anything else in your project that defines those names.

curl -sSL https://raw.githubusercontent.com/akii09/yukti/main/install.sh | bash

If jq is available it's used for clean JSON merging; otherwise the script falls back to sed.

Plugin development

Clone and load the plugin directly without a marketplace:

git clone https://github.com/akii09/yukti.git
claude --plugin-dir ./yukti

Skills appear as /yukti:smart etc. Useful for evaluating a fork or developing changes.

Use it

The main command:

/yukti:smart Add a dark mode toggle to the settings page