Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Track OpenClaw/Clawdbot token and cost usage from session JSONL logs (prefer real usage.cost when present), generate daily/weekly summaries and top expensive sessions, and run budget checks (exit code on breach). Use to monitor spend, enforce budgets via cron/alerts, and apply a token-saving playbook to reduce output/tool-call cost.
Track OpenClaw/Clawdbot token and cost usage from session JSONL logs (prefer real usage.cost when present), generate daily/weekly summaries and top expensive sessions, and run budget checks (exit code on breach). Use to monitor spend, enforce budgets via cron/alerts, and apply a token-saving playbook to reduce output/tool-call cost.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Use this skill when you need: accurate cost reports (daily/weekly/lifetime) top expensive sessions guardrails to reduce token burn (without changing config unless user asks)
Prefer session JSONL logs (they contain per-call usage, often with real USD cost): OpenClaw: ~/.openclaw/agents/*/sessions/*.jsonl Legacy/compat: ~/.clawdbot/agents/*/sessions/*.jsonl Do not estimate from βcurrent context windowβ style token fields.
python3 {baseDir}/scripts/extract_cost.py --last-days 7
python3 {baseDir}/scripts/extract_cost.py --today python3 {baseDir}/scripts/extract_cost.py --yesterday
python3 {baseDir}/scripts/extract_cost.py --top-sessions 10
python3 {baseDir}/scripts/extract_cost.py --last-days 30 --json
Some providers may omit usage.cost. You can provide per-1M-token prices: export PRICE_INPUT=1.75 export PRICE_OUTPUT=14 export PRICE_CACHE_READ=0.175 export PRICE_CACHE_WRITE=0 python3 {baseDir}/scripts/extract_cost.py --last-days 7
The extractor can run as a budget check: python3 {baseDir}/scripts/extract_cost.py --today --budget-usd 5 If budget is exceeded, it prints an ALERT and exits with code 2 (default). For non-failing checks: python3 {baseDir}/scripts/extract_cost.py --today --budget-usd 5 --budget-mode warn
Run it daily (or hourly) and if exit code is 2, send yourself a Telegram message. (Implementation depends on your OpenClaw channel setup; do not embed secrets in scripts.)
When the user says βuse as few tokens as possibleβ, apply: Default response budget: 1β6 lines, bullets > paragraphs Ask 1 question max (only if truly blocking) Progressive disclosure: offer details only if asked Tool calls: batch; avoid repeated status/browser calls No log dumps into chat; summarize + point to file path Hard limits: max 3 web iterations (search/fetch) per task Optional phrasing to keep yourself in check: "Answer in <=6 lines. If more is needed, ask permission."
Workflow acceleration for inboxes, docs, calendars, planning, and execution loops.
Largest current source with strong distribution and engagement signals.