Openclaw Cost Tracker
PassAudited by ClawScan on May 1, 2026.
Overview
This skill appears to do what it says—summarize OpenClaw costs from local session logs—but users should verify the separately installed diff CLI and avoid sharing generated summaries carelessly.
Before installing, confirm that you are comfortable with the skill reading your local OpenClaw session logs. If you use the preferred openclaw-cost-diff or ocost command, verify that the executable is the one you intended to install. Be careful when exporting JSON to dashboards or setting up the optional cron job, because cost and usage history can still reveal private workflow information.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
The tool can reveal local usage, model, request, token, and cost patterns from your OpenClaw history.
The fallback script reads persistent local OpenClaw session JSONL records. It appears to aggregate usage/cost fields, but those session files are still local agent history and should be treated as sensitive.
for session_file in sessions_dir.rglob("*.jsonl"):
...
entry = json.loads(line)
msg = entry.get("message", entry)Run it only on intended OpenClaw agent directories and review any JSON/text output before sending it to dashboards, alerts, or other people.
If the local openclaw-cost-diff or ocost executable is unexpected or modified, the agent could run code that is not part of this reviewed skill.
The primary recommended workflow depends on an executable that is not included in the bundled files reviewed here. This is disclosed, but its provenance and version are outside the artifact set.
the preferred diff workflow uses a separately installed CLI
Verify the installed diff CLI path, source, and version before allowing the agent to use it; otherwise use the bundled fallback script.
A cron setup would keep reading session usage and appending cost snapshots until you remove it.
The skill documents an optional scheduled job. It is user-directed and local, but it would continue running periodically if the user installs it.
Set up a cron to track spend over time: 0 0 * * * python3 /path/to/cost_tracker.py --days 1 --format json >> ~/cost-log.jsonl
Only create the cron job if you want ongoing tracking, store the log somewhere appropriate, and remove the scheduled job when no longer needed.