OpenClaw Token Usage
v1.2.0Inspect token usage from local OpenClaw transcripts across a specified time range. Use when the user asks how many tokens were consumed in OpenClaw, GitHub C...
⭐ 0· 115·0 current·0 all-time
byLu Yanqiang@lujohn74
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description promise (inspect token usage from local OpenClaw transcripts) matches the bundled Python script which reads ~/.openclaw/agents/*/sessions/, parses transcript JSONL, aggregates token metrics, and emits summaries/CSV/JSON/markdown. There are no unrelated binaries, credentials, or config paths requested.
Instruction Scope
SKILL.md tells the agent to run the included script with time range, tz, and optional scope filters; the script implementation confines itself to reading transcript files under the user's OpenClaw directory and producing local outputs. There are no instructions to read unrelated system files, environment variables, or to send data to external endpoints.
Install Mechanism
No install spec is present (instruction-only with a bundled script). No remote downloads or archive extraction are used. Risk is limited to local execution of the provided Python script.
Credentials
The skill requests no environment variables or credentials. It accesses files only under the user's home OpenClaw paths (sessions and sessions.json), which is proportionate to its stated purpose.
Persistence & Privilege
The skill is not always-enabled and uses normal agent invocation. It does not request persistent system-wide privileges or modify other skills' configuration in the reviewed code.
Assessment
This skill appears to do what it says: it reads OpenClaw transcript files from your home directory and summarizes token usage locally. Before running, confirm the transcript path (~/.openclaw/agents/...) is where you keep the data you want analyzed, and that you are comfortable running a third‑party Python script on those files. The script can write JSON/CSV/markdown to paths you supply—verify output paths to avoid overwriting important files. If you need extra assurance, inspect the remainder of the script (the truncated portion) yourself for any network calls or subprocess invocations; if no network calls are present, running it locally is low-risk. Also ensure your Python environment supports zoneinfo or pass a simple tz like UTC/UTC+8 as advised in SKILL.md.Like a lobster shell, security has layers — review code before you run it.
latestvk97crgsx0jypgqdf3x4227nzrn83255y
License
MIT-0
Free to use, modify, and redistribute. No attribution required.