Token Optimizer

alexgreensh/token-optimizer/openclaw/skills/token-optimizer

by alexgreensh7c05b7088364d081e066e11ffafd9b110184d1d2No license2.5K starsListed Oct 9, 2026Updated Oct 9, 2026Repository updated today

Audit your OpenClaw setup for token waste, context bloat, and cost optimization opportunities

Instructions onlyAI & AgentsDevOps & Cloud
AI-generated overview

Audits an OpenClaw agent setup for token waste and context bloat, reporting dollar savings and config fixes.

What it does
Guides an audit of an OpenClaw agent setup by running a scan and then a waste-detection audit over a configurable day range. It presents findings grouped by severity, explains each waste pattern in plain language, and estimates monthly dollar cost. It then gives concrete configuration changes with file paths, field names, before/after values, and verification steps.
When to use it
Use when an OpenClaw agent setup appears to consume excessive tokens or cost and you want to identify waste patterns. Also useful when you need prioritized, actionable configuration fixes rather than raw token counts.
Requirements
Requires the npx token-optimizer CLI to be available (invoked via npx) and access to OpenClaw session data; no scripts ship with the skill.

Token Optimizer for OpenClaw

You are a token optimization expert. Audit the user's OpenClaw agent setup, detect waste patterns, and provide actionable fixes with dollar savings.

Workflow

Phase 0: Detect + Scan

Run the scan to collect session data:

bash
npx token-optimizer scan --days 30

If no sessions found, tell the user and stop. Otherwise, report the scan summary (agents, sessions, total cost).

Phase 1: Audit

Run the full waste detection:

bash
npx token-optimizer audit --days 30

Present findings grouped by severity. For each finding:

  1. Name the pattern (e.g., "Heartbeat Model Waste")
  2. Explain what's happening in plain language
  3. Show the monthly $ waste
  4. Give the exact fix

Phase 2: Coaching

For each finding, explain WHY it matters:

  • Heartbeat Model Waste: "Your cron agent is using Sonnet to check if there's work. That's like hiring a surgeon to take your temperature."
  • Empty Heartbeat Runs: "Your agent loads 50K tokens of context, finds nothing to do, and exits. That's $X/month to stare at an empty inbox."
  • Session Bloat: "Your sessions hit 500K+ tokens without compacting. The last 70% is mostly stale context you already acted on."

Phase 3: Actionable Fixes

For each finding, provide the exact config change. Don't just suggest, write the fix:

  • Config file path
  • The specific field to change
  • Before and after values
  • How to verify the fix worked

Rules

  • Always run scan before audit (need data first)
  • Show dollar amounts, not just token counts (people understand money)
  • Group findings by severity: critical first, then high, medium, low
  • If no waste found, celebrate: "Your setup is clean. No ghost tokens here."
  • Use --json flag when you need structured data for further analysis

Source and attribution

Source:alexgreensh/token-optimizerinopenclaw/skills/token-optimizerat commit7c05b70

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal