Token Optimizer Measures where a setup spends its context window, proposes fixes, applies the ones the user approves, and re-measures. The deliverable is a before-and-after the user can verify, with every change backed up. Typical recovery is 5-15% of the window from config cleanup, more when compaction and caching settings are wrong for the way the user works. Token Optimizer's own skills ( , , , , ) are the measurement layer, so leave them out of every unused-skill, archive or consolidation suggestion, however rarely they run. Step 0: pick the right workflow for this runtime The audit below…