Reduce Claude Code tool output with three tools
Try RTK, Headroom or Context Mode, with usage checks before you trust their token savings.
Published · 4 sources · Resume reading
RTK, Headroom and Context Mode each reduce the tool output sent to your model, according to their repositories [2][3][4]. I would try one at a time so you can check what changed and whether Claude still gets the details your task needs.
Check your current session usage
Run this inside Claude Code before changing your setup. Anthropic documents session token usage and estimated costs under /usage [1].
/usageYou should see usage information for your account and session. Per the docs, the session cost is an estimate; subscription billing does not use that estimate [1]. Save the figures alongside the task you asked Claude to do.
Try RTK for shell output
The RTK README documents a Homebrew install and a check that distinguishes this package from other tools named RTK [2]. Run these commands in your terminal.
brew install rtk
rtk --version
rtk gainYou should see the installed version and RTK's savings dashboard [2]. Its Claude Code integration uses a hook to rewrite supported shell commands to RTK equivalents.
Warning: The following command changes your global Claude Code integration. The README says it also offers proxy configuration; review those choices before accepting them [2].
rtk init -gAfter using Claude, run rtk gain again to inspect RTK's recorded savings [2].
Try Headroom through its local proxy
Headroom's README documents an isolated install with uv. Its wrapper starts a local proxy and launches Claude through it [3].
Warning: The wrapper also installs Serena for code navigation and registers it for the Claude project in ~/.claude.json, per the README. Review that integration if you already manage MCP configuration [3].
uv tool install --python 3.13 "headroom-ai[all]"
headroom wrap claudeUse another terminal to check the installation and routing with the documented health check [3].
headroom doctorLaunch future sessions with headroom wrap claude when you want them routed through Headroom [3].
Try the Context Mode plugin
Context Mode's README describes running tools in a sandbox and keeping large results outside the conversation until needed. Install its Claude Code plugin by entering these commands inside Claude [4].
/plugin marketplace add mksglu/context-mode
/plugin install context-mode@context-modeRestart Claude Code, then run the plugin's diagnostic command [4].
/context-mode:ctx-doctorYou should see its checks marked [x], per the README. After using the plugin, inspect its context statistics [4].
/context-mode:ctx-statsYou now have the chosen tool's statistics to compare with Claude Code's session usage. Repeat a comparable task and check the answer's correctness before deciding to keep that setup.
Keep this guide
Filed under Cost and context, Claude Code
Sources
- Claude Code documentation: usage and costscode.claude.com