a1673f7428
RTK was documented as delivering "60-90% token savings", which reads as a cost reduction. What RTK actually reduces is bash output bytes. Those are one contributor to input tokens, which are themselves only part of a bill that also counts output tokens, so the reduction dilutes at every step. - add docs/guide/resources/savings-explained.md as the canonical explainer: the savings chain, both estimators, and what RTK does not reduce - rescope the headline claim across README (7 languages), the guide, hook rules, agent definitions and module READMEs - relabel per-command tables as bash output reduction, keeping every figure - document that reported tokens are estimates: rtk gain uses bytes/4 (src/core/tracking.rs), filter tests use split_whitespace().count(). Neither is a real tokenizer, so ratios hold but absolute counts do not Remove figures that had no source: the $3/Mtok constant and its $36 example, the +/-10% tokenization accuracy claim, the 99.5% hook-install figure, the invented session tables in README and INSTALL, and the 30-50% parser range. CHANGELOG is untouched. Shipped release notes stay as a historical record.
GitHub Copilot Hooks
Part of
hooks/— see alsosrc/hooks/for installation code
Specifics
- Uses the
rtk hook copilotRust binary (not a shell script) -- nojqdependency - Auto-detects two input formats: VS Code Copilot Chat (snake_case
tool_name/tool_input) and Copilot CLI (camelCasetoolName/toolArgswith JSON-stringified args) - VS Code format: returns
updatedInputfor transparent rewrite - Copilot CLI format: returns
permissionDecision: "deny"with suggestion (Copilot CLI API doesn't supportupdatedInput)
Testing
bash hooks/test-copilot-rtk-rewrite.sh