An open API service indexing awesome lists of open source software.

https://github.com/ahkamboh/tokentrim

Drop-in cost-optimized Claude Code subagents β€” route grunt work to cheap Haiku, keep Opus for the hard 10%. MIT, zero runtime.
https://github.com/ahkamboh/tokentrim

ai-agents claude-code cost-optimization developer-tools subagents

Last synced: 11 days ago
JSON representation

Drop-in cost-optimized Claude Code subagents β€” route grunt work to cheap Haiku, keep Opus for the hard 10%. MIT, zero runtime.

Awesome Lists containing this project

README

          

tokentrim

Drop-in cost-optimized Claude Code subagents β€” route grunt work to cheap Haiku, climb to Opus/Fable only when the job earns it.


MIT
8 agents
4 tiers
zero runtime


🌐 Live site ·
⚑ Set up ·
Tiers Β·
How it saves

---

You're a vibe coder running everything on one expensive model. Most of what it does is **grunt work** β€” grepping for a function, reading a log, running tests, fixing a typo β€” and you're paying frontier-model prices for all of it.

tokentrim is **8 ready-made Claude Code subagents** spread across four model tiers. Drop them into `.claude/agents/` and Claude Code automatically does the grunt work on cheap **Haiku**, normal coding on **Sonnet**, and only climbs to **Opus**/**Fable** for the rare task that truly needs it β€” no `/model` switching, just cheaper sessions.

## ⚑ Set it up with your AI agent

Paste this into **Claude Code, Cursor, Codex β€” or any AI agent** and it installs tokentrim for you:

```
Set up tokentrim for me β€” a pack of cost-optimized Claude Code subagents that route
grunt work (search, reading, tests, trivial edits) to cheap Haiku so my expensive
model only does the hard parts (github.com/ahkamboh/tokentrim). Do this:

1. git clone https://github.com/ahkamboh/tokentrim ~/tokentrim
2. Ask me: install to THIS project or globally? then run
bash ~/tokentrim/install.sh --project (from my project root) OR
bash ~/tokentrim/install.sh --global
3. Confirm .claude/agents/trim-*.md lists 8 agents.
```

## Or install it yourself

```bash
git clone https://github.com/ahkamboh/tokentrim
bash tokentrim/install.sh --project # β†’ ./.claude/agents (committable, per-repo)
# or
bash tokentrim/install.sh --global # β†’ ~/.claude/agents (all your projects)
```

Run it with no flag and it asks which you want. Safe to re-run β€” it never overwrites an agent you've edited (skips it unless you pass `--force` or `--backup`).

## Model tiers β€” which model for what

tokentrim defaults everything to the **cheapest tier that can do the job** and only climbs when the task demands it. That climb is the whole game:

| Tier | Model | Cost | Reach for it when… | Agent |
|------|-------|------|--------------------|-------|
| 1 Β· top | `fable` claude-fable-5 | πŸ”΄ priciest (~2Γ— Opus) | a **huge, long-horizon, autonomous** job must stay coherent across many steps β€” codebase-wide migration, sweeping multi-file refactor, deep research+build | `trim-marathon` |
| 2 Β· hard | `opus` claude-opus-4-8 | 🟠 high | the **hard 10%** β€” architecture, a subtle cross-cutting bug, tricky concurrency/security/data tradeoffs | `trim-architect` |
| 3 Β· normal | `sonnet` claude-sonnet-4-6 | 🟑 mid | **everyday coding** β€” implement a feature, write tests, a moderate refactor, review a diff | `trim-coder` |
| 4 Β· grunt | `haiku` claude-haiku-4-5 | 🟒 cheapest, fastest | **high-volume legwork** β€” search, readβ†’digest, run tests, trivial edits, version/API lookups | `trim-scout Β· trim-reader Β· trim-runner Β· trim-edit Β· trim-deps` |

Most of a session lives in tier 4 (cheap). Tiers 1–2 are deliberate escalations β€” they cost *more* when used, but only on the few tasks that actually need them.

## The 8 agents

| Agent | Model | Does |
|-------|-------|------|
| `trim-scout` | 🟒 haiku | find files / symbols / usages β†’ paths only |
| `trim-reader` | 🟒 haiku | read big/many files β†’ a tight digest |
| `trim-runner` | 🟒 haiku | run tests / build / lint β†’ failures only |
| `trim-edit` | 🟒 haiku | trivial mechanical edits (rename, typo, import, version) |
| `trim-deps` | 🟒 haiku | version / API / docs lookup |
| `trim-coder` | 🟑 sonnet | everyday coding β€” features, tests, moderate refactors, reviews |
| `trim-architect` | 🟠 opus | hard design / deep debugging (a thinker β€” returns a plan) |
| `trim-marathon` | πŸ”΄ fable | huge long-horizon jobs β€” migrations, sweeping refactors |

## How it saves β€” and roughly how much

Two honest mechanisms, no magic:

1. **Cheap model does the legwork.** Work delegated to a `haiku` agent runs on Haiku, not your pricey main model.
2. **Your main context stays lean.** Each subagent has its *own* context window and returns a short digest β€” so a 2,000-line log or four full files never pile into your expensive main thread.

```
You: "Find every call site of useAuth and read the 3 biggest."
Without tokentrim ~38k tokens on your MAIN model (Opus) grep + 3 full files in context
With tokentrim ~3k on Opus + the rest on Haiku trim-scout finds β†’ trim-reader digests
```

**Rough math β€” how much you save (illustrative, not a benchmark):**
Haiku is several times cheaper per token than Opus. If, say, ~60% of an Opus-main session is grunt work and it shifts to Haiku, your spend lands around `40% + 60%Γ·several β‰ˆ half` of what it was β€” realistically a **~30–60% lower bill** on an Opus-main session. Less if your main model is Sonnet; **~0% if your main is already Haiku**. (The opus/fable agents add cost *when used* β€” but only on the rare jobs that need them.)

**Speed:** Haiku runs faster and the leaner main context means less to re-read each turn, so grunt steps come back quicker. But your *main* reasoning model is unchanged, so end-to-end speed gains are **modest and situational** β€” the reliable win is **cost**, not raw speed. (No fake "3Γ— faster" badge here.)

> Numbers are illustrative of the mechanism β€” actual savings depend on your codebase, your main model, and how Claude routes.

## Tune it

Every agent is a plain markdown file in `.claude/agents/`. Open one and change `model:` (`haiku`/`sonnet`/`opus`/`fable`/`inherit`), tighten its `description:`, adjust `tools:`, or delete the ones you don't want. `trim-edit` and `trim-marathon` are the two most worth reviewing β€” keep `trim-edit` to trivial edits, and `trim-marathon` to genuinely huge jobs (it's your most expensive tier).

## Honesty β€” read this

- **It helps most if your main model is Opus or Sonnet.** Already on Haiku? There's little to save.
- **Delegation is Claude's choice.** Claude routes to these agents by reading their descriptions β€” tokentrim raises the odds, it can't force it.
- **It does not change your main-loop model.** The top-level model stays whatever you set; savings come from offloaded sub-tasks and a leaner context.
- **The escalation tiers cost more when used.** `opus`/`fable` agents are there for the rare hard/huge task β€” used sparingly by design.

## Uninstall

```bash
rm .claude/agents/trim-*.md
```

## License

[MIT](LICENSE) Β© [ahkamboh](https://github.com/ahkamboh) Β· built with [Claude Code](https://claude.com/claude-code)