Token Cost Monitor
v1.0.0Monitor OpenClaw API costs in real-time, set budget alerts, and optimize model spending. Track token usage by session and model, get cost optimization tips,...
⭐ 0· 72·0 current·0 all-time
by@redwoo
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description match the provided assets: SKILL.md, README, and a small helper script all focus on tracking OpenClaw token usage, budget alerts, and model routing. The skill assumes access to OpenClaw session commands (/status, /usage), which is expected for this purpose.
Instruction Scope
Runtime instructions stay within cost monitoring/optimization. A few examples show sending summaries to external endpoints (curl to Slack webhook, mail) and some vague example commands like "Analyze spending trend" — these are illustrative rather than imperative, but they do imply the user will provide webhooks/addresses and the agent may send data externally if configured. README's claim of "No external API calls" conflicts slightly with these examples.
Install Mechanism
No install spec — instruction-only plus a small shell script. No downloads or archive extraction. The included script is simple, prints pricing and tips, and declares no external endpoints or env access.
Credentials
The skill declares no required environment variables or credentials, which is appropriate. Example integrations (Slack webhook, email) would require user-supplied secrets/URLs but these are not requested by the skill itself. Verify you don't provide credentials implicitly when using those examples.
Persistence & Privilege
always is false and the skill does not request system or other-skill configuration changes. It does not require permanent presence or elevated privileges.
Assessment
This skill appears coherent and low-risk: it relies on OpenClaw session commands and contains only benign examples and a small read-only shell script. Before installing, ensure you trust the author (source is 'unknown'), confirm the OpenClaw CLI (/status, /usage) is available, and be careful when enabling examples that post to external endpoints (Slack webhook, email): only supply webhooks/credentials you control and review any commands that would transmit data. If you need stronger guarantees, ask the author for a signed provenance link or inspect the skill files locally before use.Like a lobster shell, security has layers — review code before you run it.
latestvk97b238sc9zd7bnf368qx7wvmh83pr0t
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
