openclaw-usage-tracker

Track OpenClaw model usage and costs from session transcripts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps you understand and manage the token usage and associated costs of your OpenClaw agent sessions, providing clear breakdowns and insights into resource consumption.

Core Features & Use Cases

  • Usage Tracking: Scans session transcripts to report token usage and estimated costs.
  • Cost Reporting: Generates daily, weekly, or full-history cost reports with per-model token breakdowns.
  • Interactive vs. Cron Classification: Differentiates usage between interactive sessions and automated cron jobs.
  • Provider & Model Summaries: Provides summaries of costs and tokens by provider and specific models.
  • Trend Analysis: Analyzes usage trends over specified periods.
  • Use Case: A project manager wants to understand which agent is consuming the most tokens and incurring the highest costs. They can run a report for the last month to identify the top offenders and optimize their usage.

Quick Start

Run the daily cost report for yesterday's usage.

Frequently Asked Questions about openclaw-usage-tracker

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

FAQPage Schema
How do I track OpenClaw token usage and costs across different sessions?

Track OpenClaw token usage by scanning session transcripts to calculate costs based on provider API responses or estimated per-model pricing from openclaw.json. This generates detailed reports classifying consumption by interactive sessions, cron jobs, and heartbeats.

Can I generate cost reports for specific time periods like daily or weekly?

Yes, you can generate cost reports for daily, weekly, or full historical periods. These reports provide per-model token breakdowns and summarize costs by provider to help you analyze usage trends over specified intervals.

What is the best way to differentiate token costs between interactive sessions and automated cron jobs?

The best way to differentiate token costs is by scanning session transcripts to classify usage between interactive sessions and automated cron jobs. This classification provides clear breakdowns of resource consumption and associated costs by session type.

Does OpenClaw usage tracking require provider API responses to calculate costs?

No, OpenClaw usage tracking does not strictly require provider API responses. It calculates costs based on actual provider API responses when available, or falls back to estimated per-model pricing configured in the openclaw.json file.

How do I identify which OpenClaw models are consuming the most tokens?

Identify top token-consuming models by running historical cost reports that provide per-model token breakdowns. These reports summarize costs by specific provider and model, helping you pinpoint top offenders and optimize usage.

What limitations exist when estimating AI costs from session transcripts?

A key limitation is cost accuracy when provider API responses are unavailable, requiring fallback estimation using per-model pricing from openclaw.json. This means estimated costs may vary from actual billed provider charges.