Clawculator
v1.2.1Analyze OpenClaw costs and detect billing issues. Source code is fully bundled — nothing is fetched at runtime. Requires only the node binary.
⭐ 1· 461·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (cost forensics for OpenClaw) match the code and runtime instructions. The skill only requires node and reads OpenClaw config, session logs, workspace counts, and /tmp/openclaw for logs — all directly relevant to analyzing spend and session activity.
Instruction Scope
SKILL.md explicitly lists the files the skill reads and the files it may write; the code implements those reads (openclaw.json, sessions.json, session .jsonl transcripts, workspace file counts, /tmp logs). The skill watches and tails transcript .jsonl files (liveDashboard) and parses usage entries. It claims no network calls and no shell commands; the provided source files contain only local fs/path/os usage and no networking or child_process exec. Note: session keys/IDs are truncated when displayed, but the tool does read files that may contain tokens or API usage transcripts — outputs can therefore reveal truncated identifiers and cost data.
Install Mechanism
No install specification is included; all source code is bundled in the skill folder. There are no runtime downloads or archive extraction steps in the provided code. (The README shows user-directed curl/npx examples for manual installation, but those are optional user actions, not behavior of the skill itself.)
Credentials
The skill requires no declared environment variables or credentials. It may read an optional OPENCLAW_HOME environment variable as a fallback when discovering files (liveDashboard uses process.env.OPENCLAW_HOME). This is reasonable and proportional, but users should be aware the tool will read filesystem locations in the user's home directory (e.g., ~/.openclaw and ~/clawd).
Persistence & Privilege
The skill is not always-enabled and does not request persistent system privileges. It writes only when the user passes --md (writes a markdown report to the current working directory or --out path). The live dashboard opens file watchers while running but does not change other skills' configs or system settings.
Assessment
This skill appears internally consistent and does what it says: it inspects your OpenClaw config and session transcripts, computes cost estimates, and emits reports. Before running, consider: 1) inspect the bundled files (run.js, analyzer.js, reporter/mdReport/htmlReport) yourself — the author encourages auditing the folder. 2) The tool reads ~/.openclaw and session .jsonl transcripts which can contain usage records and identifiers; displayed session keys are truncated but some cost and timestamp data will be included in reports. 3) The skill writes a markdown report only when you pass --md (or --out=PATH) — be careful with the output path. 4) The README includes example curl/npx install commands; those would fetch code from the network if you run them yourself — the skill as packaged does not perform network requests. If you are comfortable with these behaviors and have inspected the bundled source, the skill is coherent with its stated purpose.Like a lobster shell, security has layers — review code before you run it.
latestvk97ad9wy3b008dkmyhrapfjgwx82enh1
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🦞 Clawdis
Binsnode