Token Counter

Track and analyze OpenClaw token usage across main, cron, and sub-agent sessions with category, client, model, and tool attribution. Use when the user asks where tokens are being spent, wants daily/weekly token reports, needs per-session drilldowns, or is planning token-cost optimizations and needs evidence from transcript data.

This skill appears to do what it says: parse local OpenClaw session data and produce token-usage reports. Before installing or running it, do the following: (1) Inspect scripts/token_counter.py locally (you already have it) to ensure no unexpected network or credential use — the script appears local-only. (2) Note that SKILL.md expects an executable named token-counter but the shipped file is token_counter.py; run it explicitly with python3 or add a wrapper. (3) Be aware the tool reads session transcripts and cron payloads (sensitive data). If you don't want it to access your real OpenClaw data, run it in a sandbox or point it to a copy by setting the appropriate env vars/CLI args. (4) Consider editing the hard-coded DEFAULT_* paths to use your environment variables or explicit CLI arguments to avoid accidental reads of /Users/mikek/... . (5) If you need higher assurance, run the script in a restricted environment and grep for any network/socket calls before allowing it to access production data.

Type: OpenClaw Skill Name: token-counter Version: 1.0.0 The OpenClaw AgentSkills skill bundle 'token-counter' is benign. Its code and documentation are fully aligned with its stated purpose of analyzing local OpenClaw token usage. The `SKILL.md` and `agents/openai.yaml` files contain no prompt injection attempts or instructions for unauthorized actions. The `scripts/token_counter.py` script accesses only local OpenClaw data files, performs no network communication, and lacks any malicious execution patterns. While the `--output` argument in `token_counter.py` could theoretically allow writing to arbitrary file paths if an absolute path is provided, this is a common feature for reporting tools and does not indicate malicious intent by the skill author, especially given the `SKILL.md` examples show writing within the designated `$OPENCLAW_WORKSPACE`.