Token Ledger (SQLite)

Audit-grade token and cost ledger for OpenClaw. Use when you need to (1) record every model call’s usage (input/output/cache read/cache write/cost) into SQLi...

This skill appears to do what it says: it watches your local OpenClaw session JSONL files and writes usage rows into ~/.openclaw/ledger.db, then provides queries and deterministic reports. Before installing or running it as a daemon: (1) Review the ledger_watcher.py code yourself (it will read session JSONL and store usage_raw — this may include message content); (2) Note the manifest is missing the expected com.openclaw.token-ledger-watcher.plist template referenced by render_plist.py and SKILL.md — you will need that file or must adapt the render step to your environment; (3) Test with the one-shot (--once) mode first to verify file paths and behavior; (4) If you intend to enable the LaunchAgent, understand it will run continuously as your user and read session files — only install it if you trust the code and accept the privacy tradeoff; (5) There are no network calls or external credentials requested by the included scripts, which reduces exfiltration risk, but always inspect any scripts before granting persistent execution. If you want higher assurance, ask the skill author for the missing plist file, or run the scripts in a sandboxed account first.

Type: OpenClaw Skill Name: token-ledger Version: 0.1.0 The token-ledger skill implements a usage tracking system that monitors OpenClaw session logs and stores data in a local SQLite database. It is classified as suspicious because it includes instructions in SKILL.md for the agent to establish system persistence on macOS via a LaunchAgent (com.openclaw.token-ledger-watcher.plist) and a background daemon (ledger_watcher.py). While these high-risk capabilities—persistence and monitoring of sensitive session data—are aligned with the stated purpose of an audit-grade ledger, they represent a significant system modification that warrants caution. No evidence of malicious intent, such as data exfiltration or unauthorized remote access, was found in the code logic.