skill-cost
v0.1.0Track per-skill token usage and costs from OpenClaw session logs. Use when user asks about skill-level spending, which skill costs the most, or wants a per-skill cost breakdown. IMPORTANT: This is a bash-tool skill. You MUST use the bash/shell tool to execute commands.
Installation
Please help me install the skill `skill-cost` from SkillHub official store.
npx skills add dzwalker/skill-cost
Skill Cost — USE BASH TOOL
You MUST use the bash or shell tool to run these commands. No other method works.
Commands
Per-skill cost report:
bash ~/.openclaw/workspace/skills/skill-cost/skill-cost.sh report
Last 7 days:
bash ~/.openclaw/workspace/skills/skill-cost/skill-cost.sh report --days 7
Since a specific date:
bash ~/.openclaw/workspace/skills/skill-cost/skill-cost.sh report --since 2026-03-01
JSON output:
bash ~/.openclaw/workspace/skills/skill-cost/skill-cost.sh report --format json
Top skills by cost:
bash ~/.openclaw/workspace/skills/skill-cost/skill-cost.sh ranking
Detail for a specific skill:
bash ~/.openclaw/workspace/skills/skill-cost/skill-cost.sh detail poe-connector
Compare two skills:
bash ~/.openclaw/workspace/skills/skill-cost/skill-cost.sh compare poe-connector web-search
DO NOT
- Do NOT use
sessions_spawn— it will fail - Do NOT use browser — it will fail
- Do NOT use any approach other than
bashtool — only bash works
How It Works
- Scans OpenClaw session JSONL files at
~/.openclaw/agents/*/sessions/ - Parses assistant messages for tool calls and token usage
- Attributes token usage to skills by matching bash command paths and tool names
- Aggregates and reports per-skill costs with model and daily breakdowns
Notes
- No API keys required — reads directly from local session files
- No external Python dependencies (stdlib only)
- Skill attribution uses bash command paths and SKILL.md tool mappings
- Tokens for multi-skill messages are proportionally split across skills
- Usage not attributable to any skill is categorized as (built-in) or (conversation)