Your LLM Doesn't Need 200 Lines of Test Output

You paste a command's output into your LLM context, and half of it is noise. go test -v on a medium-sized project dumps hundreds of lines of === RUN , --- PASS: , and timing info that no model needs to see. cargo test is worse. git status includes instructions you've read a thousand times. Every line you send is tokens you're paying for, and most of them carry zero information. The obvious fix is "just pipe through grep." That works until you need different filtering for success versus failure, or you want to keep error details while stripping pass lines, or you're using Claude Code and the output is captured automatically before you can touch it. The real fix is a tool that understands command output structure and compresses it before your LLM ever sees it. That tool exists, it's two weeks old, and it already ships 40 filters. What Is tokf? tokf is a config-driven CLI that sits between your terminal commands and your LLM context window, compressing output down to what matters. It's bu