Best alternative to claude-token-optimizer (nadimtuhin)
Tokenade is the best alternative to claude-token-optimizer (nadimtuhin) — Universal token-optimization engine for AI coding agents — native hooks for 18 agents combine output filtering, semantic code search, skeleton compression, sandboxed execution, MCP proxying and a live savings dashboard in a single dependency-free binary.
Get TokenadeOutput Filtering
Format-aware compactors cover git, cargo, kubectl, terraform, docker and more — 60–99% reduction on the noisiest commands. Command rewriting further trims source-side before the shell even runs.
Output Filtering
Not available. claude-token-optimizer is a one-time scaffold generator; it does not intercept tool outputs at runtime.
Semantic Code Search
Finds the most relevant files for a task and sends only those to the model, instead of the whole repo. Runs fully on-device with no external vector database and no model downloads — fast even on large codebases.
Semantic Code Search
Not available. The tool scaffolds a directory structure; it does not index or search code.
Skeleton Compression
Signatures-only view of source files, YAML, Markdown and Terraform — −64% on file reads while preserving every top-level declaration. Stacks on top of output filtering for maximum savings.
Startup Token Reduction
The generated CLAUDE.md + .claudeignore + lazy-loadable directories reduce per-session startup load by ~90% on bloated projects (e.g. 11,000 → 800 tokens on a RedwoodJS project). One-time benefit; no ongoing compression.
Third-Party MCP Optimization
tokenade mcp-proxy wraps any third-party MCP server's launch command in the agent's MCP config, so every tool result (verbose JSON, logs, console output) is folded on the way back — set once, not per call. Image results pass through untouched.
Lazy MCP Loading
Not available.
Mechanism Breadth
The only tool combining output filtering + semantic search + skeleton compression + sandbox execution + MCP proxying + secret redaction + content-addressed cache in a single binary. On the open THOL benchmark (Claude Code 2.1.183 campaign) it is the only tool measured significantly cheaper than the control: cost ratio 0.84 [0.72, 0.95], 120/120 successful runs.
Mechanism Breadth
Single mechanism: startup scaffold optimization. Does not reduce tool-output, file-read, or MCP manifest tokens during the session.
Savings Dashboard
tokenade dashboard shows measured savings, per-command and per-project breakdown, and framework-detection status. Local logs rotate automatically with built-in secret redaction.
Savings Measurement
cto measure gives a one-shot pre-scaffold estimate of startup token waste. No ongoing runtime tracking.
claude-token-optimizer (nadimtuhin) at a glance
claude-token-optimizer (nadimtuhin) starts at Free (open source). npm CLI scaffolder that generates a structured CLAUDE.md + companion files, a .claudeignore and lazy-loadable history directories, claiming ~90% reduction in per-session startup token load.
Pros
- cto measure shows you exactly how many tokens you waste before you change anything — great 'Aha!' moment
- 13-framework auto-detection (Express, Next.js, Django, Rails, Spring Boot…) from package.json/go.mod/etc.
- Zero ongoing runtime cost — pure scaffold, no hook or proxy daemon
- npm-installable, npx-runnable, no native build required
Cons
- One-time benefit: once generated, the scaffold is static and won't re-measure or self-update
- Does not reduce tool-output tokens, file-read tokens, or MCP manifest costs
- Savings depend entirely on how bloated the project's CLAUDE.md was to begin with
Ready to cut costs with Tokenade?
Join the teams that already chose Tokenade over claude-token-optimizer (nadimtuhin).
Get Tokenade