Terminal Commands
Find commands that can flood context: tests, logs, Docker output, API responses, browser traces, and recursive directory reads.
Token cost checklist
Claude Code, Codex, Cursor, browser agents, and CI agents get expensive when the workflow keeps feeding them avoidable output. Use this checklist to remove the common waste before scaling a team setup.
Fast fixes
Most cost waste is not mysterious. It comes from commands, logs, and status reports that are useful to a machine once, then expensive every time they are pasted back into context.
2>&1 | head -c 4000 or a stricter cap.rtk git, rtk grep, rtk read, rtk diff, rtk test, rtk json, and rtk log when they fit.rg for searches and point the agent at exact files instead of asking it to rediscover the whole repo.What to inspect
Find commands that can flood context: tests, logs, Docker output, API responses, browser traces, and recursive directory reads.
Check AGENTS.md, CLAUDE.md, Cursor rules, and global instructions for command-output rules, rtk usage, and stop-loop rules.
Look for agents rereading old reports, screenshots, ledgers, and raw logs instead of using a compact current-state file.
Tool-specific audits
Review the repo instructions, command output, and repeated scans that make Claude Code sessions heavier than needed.
Claude Code AuditClean up rtk usage, byte caps, loop-state files, and browser or API checks that flood Codex context.
Codex AuditUse the general audit for Cursor, browser agents, CI agents, or mixed coding-agent workflows.
Buy AuditDecision rule
Add command caps and a repo instruction. This is often enough for one-off work.
Audit the workflow if agents repeatedly read huge files, logs, or generated artifacts.
Roll out shared rules, templates, and token-cost checks across repos before usage grows.
Need the cleanup done?