Skill Detail

Reduce agent token burn on repo-scale coding commands with the rtk CLI proxy

<p>Use rtk when an agent keeps wasting context on noisy shell output from large repos and you need smaller command responses before the model sees them.</p>

Developer ToolsMulti-Framework
Developer Tools Multi-Framework Published
⭐ 25.4k GitHub stars
INSTALL WITH ANY AGENT
npx skills add agentskillexchange/skills --skill reduce-agent-token-burn-on-repo-scale-coding-commands-with-the-rtk-cli-proxy Copy
Works best when you want a reusable capability, not another fragile one-off prompt.
At a glance
Tools required
A shell-heavy coding-agent workflow, a supported agent such as Claude Code, Codex, Cursor, Gemini CLI, or Cline/Roo, and permission to install a local RTK hook or call rtk directly.
Install & setup
<p>Install <code>rtk</code> with Homebrew, the upstream install script, or a Git-based install, then run <code>rtk init -g</code> or the agent-specific init flag for your tool. Restart the agent shell afterward so commands like <code>git</code>, <code>grep</code>, and test runners are routed through RTK's output filters.</p>
Author
RTK AI
Publisher
Company
Last updated
Apr 13, 2026
Quick brief

rtk gives an agent a narrow shell-output compression workflow. It sits in front of commands like git status, git diff, grep, cat, and test runners, then filters and condenses the output before it reaches the model context. That makes it useful in repo-scale coding sessions where shell output, not reasoning, is what burns tokens.

How it works

What this skill actually does

The boundary is clear enough to be skill-shaped. Invoke it when the task is shrinking noisy command output for an existing coding-agent workflow, not when the user wants a new coding agent, an IDE extension, or a general terminal replacement. The job-to-be-done is context-saving shell mediation for large-codebase work.