mirror of
https://github.com/rtk-ai/rtk.git
synced 2026-09-19 07:33:17 +08:00
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.
801 B
801 B
Ruby on Rails
Part of
src/cmds/— see also docs/contributing/TECHNICAL.md
Specifics
Percentages below are reductions in bash output, measured with RTK's token estimator rather than a real tokenizer.
rake_cmd.rsfilters Minitest output viarake test/rails test; state machine text parser, failures only (85-90% reduction)rspec_cmd.rsuses JSON injection (--format json) with text fallback; failures only (60%+ reduction)rubocop_cmd.rsuses JSON injection, groups by cop/severity (60%+ reduction)- All three modules use
ruby_exec()fromutils.rsto auto-detectbundle execwhen a Gemfile exists - TOML filter
bundle-install.tomlstripsUsinglines frombundle install/update(90%+ reduction)