What problem does it solve? Teams adopting a documentation index like Fux often cannot prove whether it actually reduces context-window and API costs. This Skill replaces illustrative ROI estimates with measured numbers computed from the project's real file sizes, giving an auditable answer to "is Fux actually saving me anything?" ## Core Features & Use Cases - Measured ROI report: Counts bytes across the index, rules, and governed code files, applying a transparent ~4-chars-per-token heuristic identically to both sides of the comparison. - Dollar pricing: Converts token counts into dollars at a configurable usd_per_mtok rate (defaulting to Claude Opus 4.8's $5/M input rate), with per-lookup and aggregate savings multipliers. - Cumulative tracking: When cost_tracking is enabled, reports lifetime tokens and dollars saved plus per-day, week, and month rates. - Use Case: Run /fux savings "how do we roll back a release" to compare the cost of reading whole governed files versus a Fux-guided lookup, then use a low multiplier as a signal to link more code_refs with fux refs or fux coverage. ## Quick Start Ask the assistant to run /fux savings on a specific question to see the measured token and dollar savings for that lookup.