rtk hits 59.7K stars: a zero-dependency Rust proxy that cuts agent token use 60 to 90%

Every story above generates tokens, and tokens are money. rtk is the clearest "do this today" item in the whole dataset. It's a single Rust binary, 59,658 stars, created January 22 and pushed as recently as June 7, that proxies common dev commands and claims 60 to 90% reductions in token consumption for agentic coding. Source: GitHub

Here's why this one's real and not vanity-metric noise. It's not a lone repo. Token economics is becoming a whole tooling category, and it showed up from five different directions in today's findings. headroom (16.5K stars) compresses tool outputs, logs, and RAG chunks before they hit the model, claiming 60 to 95% fewer tokens with "same answers." Source: GitHub codeburn audits your transcripts for re-read files and bad read-to-edit ratios. Cloudflare added hard spend caps to its AI Gateway. And a whole Substack genre now exists on Claude Code token optimization. When a category converges from that many independent angles in one week, it's not a fad. It's a missing layer of the stack getting built.

The reason this matters more than it sounds: agentic coding sessions routinely burn 40K to 80K tokens before a single line gets written. Subagent fan-out, autocompact cascades, MCP servers loading 18K+ tokens per turn each. Average spend for people running these tools all day is landing at $400 to $1,500 a month per developer. If you're running Claude Code or Codex on a cron, or you've got agents doing batch work overnight, that's a recurring bill that compounds.

What to do: try rtk or headroom on your actual workload this week and measure. Don't take the 60 to 90% on faith, run codeburn first to get your baseline, then drop the proxy in and compare. The reductions are real but workload-dependent, and a command-level proxy (rtk) and a context-level compressor (headroom) attack different parts of the spend. They stack. I'd test both.

The bigger signal is that "make the agent cheaper" graduated from a prompt trick to infrastructure. A year ago you optimized tokens by writing tighter prompts. Now there's a binary you drop in front of your toolchain. That's the maturity curve every successful dev category follows, from a thing you do by hand to a thing you install.