← Back to Skills Marketplace
netanel-abergel

usage-costs

by Netanel Abergel · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ⚠ suspicious
84
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install usage-costs
Description
Report AI token usage and estimated costs. Use when: owner asks about costs today/yesterday/this week, per session, or per model. Shows main session, cron jo...
Usage Guidance
This skill appears to do what it claims (compute token usage/costs from OpenClaw data), but there are concrete operational risks you should consider before installing or enabling it: - Inspect the .context file (/opt/ocana/openclaw/workspace/skills/usage-costs/.context) before allowing the skill to run. Because the skill sources that file, any shell code in it would be executed — ensure it contains only simple key=value lines and no commands. - Confirm the OpenClaw CLI and the directories referenced (/opt/ocana/openclaw/cron/runs, /opt/ocana/openclaw/agents/main/sessions, /opt/ocana/openclaw/workspace/data) are accessible only to trusted users; the skill reads potentially sensitive session and run logs. - Be aware the skill appends to token-history.jsonl. If you want read-only reporting, avoid or sandbox the write step (or require manual approval before writes). - Prefer safer alternatives: instead of sourcing a shell file, the skill could parse a JSON config or accept explicit declared env vars. If you maintain this environment, consider replacing 'source' with a non-executing parser. - Run the skill with least privilege (non-root agent user) and, if possible, test in a staging environment first. Why 'suspicious' rather than 'benign': there is no evidence of misdirection or external exfiltration, but the use of 'source' on a file and implicit reading/writing of shared system files increases risk and constitutes a mismatch with the declared metadata (no env vars declared). If you can confirm the .context contents are benign and you accept the on-disk writes, the remaining footprint is reasonable for the stated purpose. If you want higher confidence, provide the contents of the .context file (or confirm it's purely key=value), and confirm file permissions/owners for the referenced paths — that information would allow raising confidence to high or downgrading the concern.
Capability Analysis
Type: OpenClaw Skill Name: usage-costs Version: 1.0.0 The usage-costs skill is a legitimate utility designed to aggregate and report AI token usage and costs. It functions by parsing local session logs, cron history, and status reports within the /opt/ocana/openclaw/ directory structure. The provided Python and Bash scripts are transparent, lack obfuscation, and perform only the described data aggregation tasks without any evidence of data exfiltration or unauthorized execution.
Capability Assessment
Purpose & Capability
The name/description (report token usage and estimated costs) matches what the SKILL.md does: it reads OpenClaw live status, cron run JSONL files, and token-history JSONL to compute usage and costs. No unrelated external services, credentials, or installs are requested.
Instruction Scope
Instructions tell the agent to 'source' a local .context file at /opt/ocana/... which will execute any shell code in that file (execution risk). The skill reads many local files (/opt/ocana/... cron runs, sessions, token-history) and explicitly instructs appending JSON to token-history.jsonl — i.e., it both reads and writes system-wide data. Reading those OpenClaw files is coherent for cost reporting, but sourcing an arbitrary file and writing to shared data increase the attack surface and privilege requirements.
Install Mechanism
Instruction-only skill with no install spec, no external downloads, and no dependencies. This is the lowest install risk.
Credentials
Registry metadata declares no required env vars, but SKILL.md expects variables provided by the sourced .context (OWNER_PHONE, PRICING_INPUT/OUTPUT/CACHE_READ). That mismatch means the skill will obtain configuration/secret values from an on-disk file rather than declared env vars. Sourcing a file to obtain these values can execute code and may expose hidden local settings; the skill does not request or need external API keys but it does access local potentially sensitive state.
Persistence & Privilege
The skill is not marked always:true and is instruction-only (no persistent install). However it instructs appending daily reports to /opt/ocana/openclaw/workspace/data/token-history.jsonl, so it will modify on-disk state under the OpenClaw workspace. Autonomous invocation is allowed by default (normal), which means the agent could run these read/write actions without extra user intervention.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install usage-costs
  3. After installation, invoke the skill by name or use /usage-costs
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial publish from Heleni workspace
Metadata
Slug usage-costs
Version 1.0.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is usage-costs?

Report AI token usage and estimated costs. Use when: owner asks about costs today/yesterday/this week, per session, or per model. Shows main session, cron jo... It is an AI Agent Skill for Claude Code / OpenClaw, with 84 downloads so far.

How do I install usage-costs?

Run "/install usage-costs" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is usage-costs free?

Yes, usage-costs is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does usage-costs support?

usage-costs is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created usage-costs?

It is built and maintained by Netanel Abergel (@netanel-abergel); the current version is v1.0.0.

💬 Comments