01. RTK / Rust Token Killer
Type: Terminal output filter
In simple words: Like a filter that removes noisy terminal lines before AI reads them. Directly reduces noisy output from common Git, test, lint and build commands.
Publisher instructions: https://github.com/rtk-ai/rtk
📦 Install on your computer (once)
- Open normal Terminal (VS Code: Terminal → New Terminal). Run
rtk --versionandrtk gainto see whether the correct RTK is already installed. - If RTK is missing, choose one: Windows PowerShell:
winget install rtk-ai.rtk; macOS/Linux with Homebrew:brew install rtk-ai/tap/rtk. For other systems see the official installation page. - Close and reopen Terminal. Run
rtk --versionandrtk gainagain. The first should show a version; the second should show an RTK usage/savings screen. If only the first works, you may have the unrelated RTK package.
Claude Code CLI
📦 How to install
Follow the one-time installation above. No second copy of RTK / Rust Token Killer is needed for this computer.
⚙️ How to configure
- Open your practice project folder in VS Code (File → Open Folder). Open Terminal → New Terminal.
- Run
rtk init --dry-runto preview the RTK settings/files it would create. Nothing is changed yet. - If permitted, run
rtk initwithout--dry-run. This sets up RTK for this folder and Claude Code. Review any hook/instruction files it writes (a hook is an automatic command helper). - Close and reopen your Claude Code session. Never override an organization policy to enable hooks.
🚀 How to use it in your project
- In the same project Terminal, type
claudeto open Claude Code chat. - In the AI chat box, paste: “Run
git statusin this project. Do not edit files. Show the result.” Approve only the read-only command if prompted. - Open a second normal Terminal and run
rtk gain; compare the usage screen with its earlier value. RTK should have recorded activity if the command was eligible for rewriting. If not, check the hook setup or try a supported test/build command.
Check: Read the terminal or agent activity to confirm the add-on was actually used.
Codex CLI
📦 How to install
Follow the one-time installation above. No second copy of RTK / Rust Token Killer is needed for this computer.
⚙️ How to configure
- Open your practice project folder in VS Code (File → Open Folder). Open Terminal → New Terminal.
- Run
rtk init --codex --dry-runto preview the RTK settings/files it would create. Nothing is changed yet. - If permitted, run
rtk init --codexwithout--dry-run. This sets up RTK for this folder and Codex. Review any hook/instruction files it writes (a hook is an automatic command helper). - Close and reopen your Codex session. Never override an organization policy to enable hooks.
🚀 How to use it in your project
- In the same project Terminal, type
codexto open Codex chat. - In the AI chat box, paste: “Run
git statusin this project. Do not edit files. Show the result.” Approve only the read-only command if prompted. - Open a second normal Terminal and run
rtk gain; compare the usage screen with its earlier value. RTK should have recorded activity if the command was eligible for rewriting. If not, check the hook setup or try a supported test/build command.
Check: Read the terminal or agent activity to confirm the add-on was actually used.
GitHub Copilot CLI
📦 How to install
Follow the one-time installation above. No second copy of RTK / Rust Token Killer is needed for this computer.
⚙️ How to configure
- Open your practice project folder in VS Code (File → Open Folder). Open Terminal → New Terminal.
- Run
rtk init --copilot --dry-runto preview the RTK settings/files it would create. Nothing is changed yet. - If permitted, run
rtk init --copilotwithout--dry-run. This sets up RTK for this folder and Copilot CLI. Review any hook/instruction files it writes (a hook is an automatic command helper). - Close and reopen your Copilot CLI session. Never override an organization policy to enable hooks.
🚀 How to use it in your project
- In the same project Terminal, type
copilotto open Copilot CLI chat. - In the AI chat box, paste: “Run
git statusin this project. Do not edit files. Show the result.” Approve only the read-only command if prompted. - Open a second normal Terminal and run
rtk gain; compare the usage screen with its earlier value. RTK should have recorded activity if the command was eligible for rewriting. If not, check the hook setup or try a supported test/build command.
Check: Read the terminal or agent activity to confirm the add-on was actually used.
Visual Studio Code (Copilot Chat)
📦 How to install
Follow the one-time installation above. No second copy of RTK / Rust Token Killer is needed for this computer.
⚙️ How to configure
- Open your practice project folder in VS Code (File → Open Folder). Open Terminal → New Terminal.
- Run
rtk init --copilot --dry-runto preview the RTK settings/files it would create. Nothing is changed yet. - If permitted, run
rtk init --copilotwithout--dry-run. This sets up RTK for this folder and VS Code Copilot Chat. Review any hook/instruction files it writes (a hook is an automatic command helper). - Close and reopen your VS Code Copilot Chat session. Never override an organization policy to enable hooks.
🚀 How to use it in your project
- Open Copilot Chat → Agent in the same VS Code folder.
- In the AI chat box, paste: “Run
git statusin this project. Do not edit files. Show the result.” Approve only the read-only command if prompted. - Open a second normal Terminal and run
rtk gain; compare the usage screen with its earlier value. RTK should have recorded activity if the command was eligible for rewriting. If not, check the hook setup or try a supported test/build command.
Check: Check Copilot Chat’s agent/tool activity, not just the wording of the answer.
Be careful: Never replace full logs when details are essential. There is another unrelated rtk project: check rtk gain.