add-rtk

Install rtk to proxy Bash tool calls into agent containers.

Updated May 7, 2026
One-click install
npx skills add https://github.com/Bartunek/nanoclaw --skill add-rtk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-rtk
Source: https://github.com/Bartunek/nanoclaw/tree/main/.claude/skills/add-rtk
Command: npx skills add https://github.com/Bartunek/nanoclaw --skill add-rtk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a secure, token-efficient way to run Bash commands inside agent containers by routing them through the rtk proxy, significantly reducing token usage during development.

Core Features & Use Cases

  • Proxy Bash tool calls through the host into containers to achieve token savings on common dev commands.
  • Automatically mount the rtk binary into containers and inject a PreToolUse hook to filter Bash invocations.
  • Use Case: Teams running containerized development workflows can achieve predictable token savings with minimal changes to existing setups.

Quick Start

Install the rtk host binary, identify the target agent group, mount rtk into the container config, enable the PreToolUse hook, and restart affected containers.

Frequently Asked Questions about add-rtk

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reduce token usage when running Bash commands inside agent containers?

To reduce token usage for Bash commands inside agent containers, you can route tool calls through an rtk proxy, achieving 60–90% savings on common dev commands.

How does proxying Bash dev commands through a host work?

Proxying Bash dev commands through a host works by mounting the rtk binary into containers and injecting a PreToolUse hook into settings.json to filter and route invocations.

How do I install and configure a proxy for containerized development workflows?

Configure the proxy by installing the rtk host binary, selecting the target agent group, wiring container mounts, enabling the PreToolUse hook, and restarting affected containers.

Can I apply proxy settings across agent groups without disrupting existing configurations?

Yes, you can apply proxy settings across agent groups without disruption because the installation relies on deterministic steps and idempotent operations to safely modify configurations.

Do I need to restart containers to activate the Bash proxy hook?

Yes, you need to restart affected containers to activate the proxy, ensuring the newly mounted rtk binary and injected PreToolUse hook take effect for Bash tool calls.