Broedkrummen Overkill Token Optimizer

What This Skill Does

The Broedkrummen Overkill Token Optimizer is a specialized utility designed for OpenClaw agents to manage, compress, and search through extensive conversation histories and command outputs. By leveraging the 'oktk' (Overkill Token Kit) CLI, this skill significantly reduces the token footprint of long-running sessions, ensuring that your agent stays within context window limits without sacrificing memory performance. It provides tools for granular token counting, session indexing for semantic retrieval, and CLI-based output compression to prune unnecessary metadata while preserving essential information.

Installation

To begin, ensure you have the core oktk CLI tool installed on your system. You can install it globally via npm by running npm install -g oktk. Once the dependency is satisfied, install the skill into your OpenClaw environment using the command: clawhub install openclaw/skills/skills/broedkrummen/broedkrummen-overkill-token-optimizer. Ensure that your environment variables are configured correctly if you have placed oktk in a non-standard directory by exporting export OKTK_BIN=/path/to/oktk in your shell configuration file.

Use Cases

• Long-term Project Context: Maintain a clean history by indexing old sessions, allowing the agent to recall specific technical decisions without reloading entire logs.
• High-Volume Debugging: Use the compress command to strip redundant CLI noise when analyzing complex git logs or build outputs.
• Cost Management: Monitor token consumption in real-time to avoid high API costs during complex automation sequences.

Example Prompts

1. "Check my current token usage and let me know if we are nearing the threshold for this session."
2. "Index the previous three sessions so that I can perform a hybrid search for the implementation details of the login module."
3. "Run 'git status' but use the token optimizer to compress the output so we don't waste context space."

Tips & Limitations

• Prerequisites: The tool relies heavily on the oktk binary. If the binary is missing or unreachable, the compression and search features will fail.
• Storage: Data is stored locally in ~/.openclaw/workspace-memory-builder/.session_index/. Periodically clear this directory if you notice high disk usage.
• Optimization Strategy: Always run token-optimizer check before executing large tasks to ensure your current compression level is sufficient for the intended workload.