Token Optimizer

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

作者 alexgreensh7c05b7088364d081e066e11ffafd9b110184d1d2無授權條款2.5K 個星標收錄於 2026年10月9日更新於 2026年10月9日儲存庫今天更新

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

AI 產生的概覽

稽核 OpenClaw 代理設定的 token 浪費與上下文膨脹,提供美元節省估算與設定修正建議。

功能
引導對 OpenClaw 代理設定進行稽核:先執行掃描,再於可設定的天數範圍內執行浪費偵測稽核。它依嚴重程度分組呈現發現,以淺白語言說明每種浪費模式,並估算每月美元成本。接著提供具體設定變更,包含檔案路徑、欄位名稱、修改前後的值以及驗證方式。
適用情境
適用於 OpenClaw 代理設定疑似耗用過多 token 或成本過高、需要找出浪費模式的情況。也適合需要依優先順序排列的可執行設定修正,而非原始 token 計數時使用。
執行需求
需要可用的 npx token-optimizer 命令列工具(透過 npx 呼叫),並能存取 OpenClaw 工作階段資料;此技能未附帶任何指令碼。

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

來源與署名

來源:alexgreensh/token-optimizer位於openclaw/skills/token-optimizer提交7c05b70

授權條款: 無授權條款

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

檢舉或申請下架