OpenClaw Cost Guard

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)

1) Data source (important)

Prefer session JSONL logs (they contain per-call usage, often with real USD cost):

• - OpenClaw: INLINECODE1
• Legacy/compat: INLINECODE2

Do not estimate from “current context window” style token fields.

2) Quick commands

Daily costs (last 7 days)

Today / yesterday

Top expensive sessions

JSON output (for dashboards)

3) If cost is missing (fallback estimate)

Some providers may omit usage.cost. You can provide per-1M-token prices:

CODEBLOCK4

4) Budget alerts

The extractor can run as a budget check:

CODEBLOCK5

• - If budget is exceeded, it prints an ALERT and exits with code 2 (default).
• For non-failing checks:

CODEBLOCK6

Wiring it to a cron alert (recommended)

5) Token-saving playbook (teach the AI)

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."