token-usage-monitor

Visualize OpenClaw token usage, model spend, and change timelines in a dashboard.

Updated Feb 18, 2026
One-click install
npx skills add https://github.com/AIDEN0602/openclaw --skill token-usage-monitor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: token-usage-monitor
Source: https://github.com/AIDEN0602/openclaw/tree/main/skills/token-usage-monitor
Command: npx skills add https://github.com/AIDEN0602/openclaw --skill token-usage-monitor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenClaw token usage, cost tracking, and model-change history can be hard to monitor across time and models. This Skill provides a centralized dashboard to visualize usage and spend, enabling faster decisions.

Core Features & Use Cases

  • Visualize token usage across models and time windows.
  • Compare model costs and highlight cost-saving opportunities.
  • Track model change timelines to identify when updates occur.
  • Use Case: When a user asks for "token usage check" or "cost by model," generate the dashboard and share the snapshot link.

Quick Start

Run the token dashboard script with your Jarvis profile to publish a 30-day usage dashboard.

Frequently Asked Questions about token-usage-monitor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I visualize OpenClaw token usage and model spend in a dashboard?

You can visualize OpenClaw token usage and model spend by running the publish_token_dashboard.sh script with your Jarvis profile, which generates a 30-day usage dashboard using a recent token_usage_snapshot.json data source.

What's the best way to compare model costs and track token usage over time?

Comparing model costs and tracking token usage is handled by a centralized dashboard that supports configurable time windows and multiple models, highlighting cost-saving opportunities and visualizing spend trends.

Do I need a specific data source to monitor token usage and model change timelines?

Yes, monitoring token usage requires a recent token_usage_snapshot.json file generated under the workspace/scripts path, plus a compatible runtime to serve the dashboard frontend and execute the publish script.

Can I track when model updates occur alongside token consumption metrics?

Tracking model change timelines alongside token consumption is supported natively, allowing you to identify when model updates occur and correlate those changes with usage spikes or cost shifts in the same dashboard view.

Why does my token usage dashboard require a workspace scripts directory?

The token usage dashboard requires the workspace/scripts directory because the publish_token_dashboard.sh script and the token_usage_snapshot.json data source must both be generated and accessed from that specific path to function correctly.