Tamp

Set up Tamp token compression proxy for OpenClaw to reduce Anthropic API input token costs. Use when the user asks to save tokens, reduce API costs, set up t...

This skill is coherent with its stated goal of running a local Tamp proxy. Before installing: (1) review and pin the npm package version (or clone and build from the GitHub repo) to ensure there is no unexpected telemetry or exfiltration; (2) remember the proxy will see your Anthropic API key in request headers — run it only on localhost or inside a locked-down container/VM and do not bind it to an external interface; (3) if you run as a service, run under an unprivileged user and inspect logs to ensure keys are not written; (4) consider adding an upstream (direct Anthropic) fallback and monitor requests until you trust the behavior. If you want higher assurance, audit the tamp source code (the skill itself provides the repository link) before using it in production.

Type: OpenClaw Skill Name: tamp Version: 1.3.0 The skill instructions in SKILL.md direct the agent to install a third-party Node.js proxy (@sliday/tamp) and route all Anthropic API traffic, including sensitive API keys, through it. It also establishes persistence by creating a systemd user service (~/.config/systemd/user/tamp.service). While the stated purpose of token compression for cost savings is plausible, the introduction of a Man-in-the-Middle (MitM) component for sensitive credentials and the automated setup of background persistence are high-risk behaviors that warrant caution.