Track OpenClaw usage costs and provide detailed reports by date and model. Supports daily, weekly, and monthly report formats for Discord and other messaging channels.
Security Analysis
high confidenceThe skill's code, install steps, and runtime instructions are consistent with its stated purpose (parsing local OpenClaw session logs to produce cost reports); it does not request credentials or contact external endpoints.
Name/description match the implementation: the scripts parse OpenClaw JSONL session logs (~/.openclaw/agents/*/sessions/*.jsonl) using jq to compute costs by date and model. Required binary (jq) and the provided CLI wrapper are appropriate for this task.
Instructions and scripts operate only on local OpenClaw session logs and produce text/JSON/Discord-formatted reports. This is expected for a cost-tracking tool, but it means the skill requires read access to potentially sensitive local session logs (timestamps, messages, errorText, model names, token counts). No instructions or code transmit data to external services or hardcoded remote endpoints.
Install spec only installs jq via Homebrew (well-known package manager). There are no downloads from arbitrary URLs or archive extractions. This is low-risk and proportional to the stated need for JSON parsing.
The skill declares no required environment variables or credentials and the code does not attempt to read tokens/keys. Minor inconsistency: package.json's 'openclaw' metadata lists 'bash' and 'jq' as required bins while registry metadata listed only 'jq' — bash is normally available on supported OSes and this is a small mismatch rather than a security issue.
The skill does not request always:true and does not modify other skills or system-wide configs. A cron example is provided for automated reporting, but that's an optional configuration file (config/cron-examples.json) and not an automatic system change by the installer.
Guidance
This skill appears to do exactly what it says: read local OpenClaw session logs and produce cost reports. Before installing or running it, consider: 1) The scripts read ~/.openclaw/agents/*/sessions/*.jsonl which may contain sensitive message text and metadata — only run if you trust the source and are comfortable allowing read access to those logs. 2) The tool does not post to Discord automatically (report_discord.sh formats output and prints it); if you wire it into a cron or agent action that posts to external channels, review those delivery steps and credentials separately. 3) There's a small metadata mismatch (package.json mentions bash + jq while registry lists jq only) — not harmful but worth noting. If unsure, inspect the scripts locally (they are included) and run them with --format json on a copy of your logs or in a restricted environment first.
Latest Release
v1.0.2
Big change: Cost tracking and reporting system fully refactored for OpenClaw, with easier automation and Discord-ready reporting. - Renamed skill to openclaw-cost-tracker with new OpenClaw-compatible file paths and model details. - Replaced old token-based scripts with shell scripts (cost_report.sh, report_discord.sh) using jq for accurate cost parsing. - Added CLI entry point and configuration/examples for scheduling and formatting reports. - Removed deprecated/inaccurate scripts for legacy Clawdbot. - Supports daily, weekly, monthly, and custom date-range cost summaries, including model breakdown. - Outputs results in formats ready for Discord and other messaging platforms.
Popular Skills
Published by @vincentqiu on ClawHub
