skills.rest
alexgreensh
alexgreenshCOMMUNITY
Explore all skills by this author →
Website𝕏@alexgreenshGitHub

token-optimizer

Audit OpenClaw agent setups for token waste and context bloat.

1.8k|149|Updated Feb 26, 2026
Search Tags:#optimization#audit#token#cost-analysis#openclaw#token-waste#context-bloat
One-click install
npx skills add https://github.com/alexgreensh/token-optimizer --skill token-optimizer-alexgreensh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: token-optimizer
Source: https://github.com/alexgreensh/token-optimizer/tree/main/openclaw/skills/token-optimizer
Command: npx skills add https://github.com/alexgreensh/token-optimizer --skill token-optimizer-alexgreensh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenClaw agent setups often accumulate token waste and context bloat, leading to higher costs and slower responses. The Token Optimizer audits configurations to surface inefficiencies and opportunities to optimize token usage.

Core Features & Use Cases

  • Phase 0: Detect + Scan: Collect session data to compute basic metrics and identify whether there are any sessions to analyze.
  • Phase 1: Audit: Run detailed waste detection and group findings by severity, with actionable recommendations.
  • Phase 2: Coaching: Explain why each issue matters and quantify potential cost savings.
  • Phase 3: Actionable Fixes: Provide exact configuration changes and verification steps to implement the fixes.

Quick Start

Run the scan to collect session data, then perform the audit to identify waste and apply the recommended fixes.

Frequently Asked Questions about token-optimizer

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

FAQPage Schema
How do I reduce token waste and context bloat in OpenClaw agent setups?▼

To reduce token waste in OpenClaw agent setups, run a phased audit that scans session data, detects inefficiencies, groups findings by severity, and outputs actionable configuration fixes with quantified dollar impact.

What causes high token costs in long-running OpenClaw sessions?▼

High token costs in long-running OpenClaw sessions are caused by context bloat and accumulated token waste. An audit can surface these specific inefficiencies and identify opportunities to optimize token usage.

How do I audit my OpenClaw deployment for token usage inefficiencies?▼

You audit OpenClaw deployments for token usage inefficiencies by collecting session data in a scan phase, then running a detailed waste detection audit that groups findings by severity and provides actionable recommendations.

Does the token cost analysis work for setups with multiple OpenClaw agents?▼

Yes, the token cost analysis applies to OpenClaw deployments with multiple agents and long-running sessions. It evaluates the configuration to reveal inefficiencies and quantify potential cost savings.

How are token optimization findings reported and prioritized?▼

Token optimization findings are reported as severity-grouped results with dollar impact quantification. The workflow explains why each issue matters and provides exact configuration changes and verification steps to implement fixes.

Related Skills

Explore More Software Engineering Skills→
netanel-abergelnetanel-abergel
5

usage-costs

Report AI token usage and estimate USD costs from OpenClaw logs.

Community
Intermediate
gonzalezpazmonicagonzalezpazmonica
47

headroom-optimization

Compress AI context windows using a 5-phase framework to reduce token usage.

Community
Intermediate
ZESCODEZESCODE

context-budget

Audit token consumption across agents, skills, rules, and MCP servers.

Community
Intermediate
copilot-ldcopilot-ld
1

libmemory

Construct token-budgeted memory windows from conversation history and tools.

Official
Advanced