add-rtk
Install rtk token-compression proxy into agent containers. Routes Bash tool calls through rtk for 60–90% token savings on dev commands (git, cargo, pytest, docker, kubectl, etc.).
Profile →npx skills add nanocoai/nanoclaw --skill add-rtk --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Add rtk Install [rtk](https://github.com/rtk-ai/rtk) — a CLI proxy delivering 60–90% token savings on common dev commands (git, cargo, pytest, docker, kubectl, etc.) — and wire it transparently into agent containers via the Claude Code `PreToolUse` hook. ## What this sets up - `rtk` binary at `~/.local/bin/rtk` on the host - `~/.local/bin/rtk` mounted read-only at `/usr/local/bin/rtk` inside the target agent group's containers - `PreToolUse` hook in the agent group's `settings.json` so every Bash call is automatically filtered through rtk — no CLAUDE.md instructions needed ## Integration tests This skill has **no in-tree integration test** by design. Its only functional reach-ins are runtime operator actions — the host-only `ncl groups config add-mount` (Step 3) and the `settings.json` `PreToolUse` hook write (Step 4) — neither of which leaves a line in the source tree whose deletion a test could catch. There are no package dependencies or Dockerfile edits to guard either. Conformance is idempotent apply + `REMOVE.md`; the mount and hook are verified at runtime (see Verify). ## Step 1 — Install rtk on the host ```bash curl -fsSL https://raw.githubusercontent.com/rtk-ai/rtk/refs/h
- What this sets up
- Integration tests
- Step 1 — Install rtk on the host
- Step 2 — Identify the target agent group
- Step 3 — Mount rtk into the container config
- Step 4 — Add the PreToolUse hook to settings.json
- Step 5 — Restart the container
- Verify
- Troubleshooting
- rtk: command not found inside the container
- Hook not firing
- Binary won't execute — permission denied
curl -fsSL https://raw.githubusercontent.com/rtk-ai/rtk/refs/heads/master/install.sh | sh find ~/.local ~/.cargo/bin ~/bin -name rtk 2>/dev/null mv "$(which rtk 2>/dev/null)" ~/.local/bin/rtk chmod +x ~/.local/bin/rtk # if needed ncl groups list ncl groups config add-mount --id <group-id> \ ncl groups config get --id <group-id> Look for the /usr/local/bin/rtk mount jq '.hooks.PreToolUse = ((.hooks.PreToolUse // []) ncl groups restart --id <group-id>
What does the add-rtk skill do?
Install rtk token-compression proxy into agent containers. Routes Bash tool calls through rtk for 60–90% token savings on dev commands (git, cargo, pytest, docker, kubectl, etc.).
How do I install it?
Run `npx skills add nanocoai/nanoclaw --skill add-rtk --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From nanocoai/nanoclaw, a repository with 30,426 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.