Headroom repo
A compression layer that shrinks tool outputs, logs, files, and RAG chunks before they reach the LLM, cutting roughly 20 percent of tokens for coding agent traffic and 60 to 95 percent for JSON heavy payloads, while keeping answers the same.
What it does for you: This is the exact problem the scout newsletter's own build log has hit for months, runs blowing their context budget on raw registry, log, and JSON reads. Headroom sits in front of those reads as a library, a local proxy, or an MCP server, so Axion's context-mode workflow and any future Hermes runtime get the same token savings without hand rolling a summarizer for every new data source.
In practice: Reads like infrastructure a heavy MCP user built for themselves out of frustration, then generalized, exactly the kind of tool worth wiring in early rather than after the next context blowout.
For: Both runtimes. Ships as a Python library, a standalone proxy, and an MCP server, so it works the same whether the caller is Claude Code, a Hermes script, or any other MCP client.
Verdict: build now. Score 29. Directly solves a problem this newsletter's own operations have documented repeatedly, ships three integration paths, and has grown from an early stage review to 68.9k stars since it was last checked in July.
Build #1 Headroom: use the ai-implementation-build-intake skill to build this safely. Source: https://github.com/headroomlabs-ai/headroom. Save canonical skill/agent under AXION\Skills and AXION\Agents.
Source · 68.9k GitHub stars and Apache 2.0 license as of today, up from an early stage review on 2026-07-24. Documented savings: 20 percent fewer tokens for coding agent tool output, 60 to 95 percent fewer tokens for JSON payloads, per the repo README.