model-usage

Summarize per-model usage and costs from CodexBar local logs.

1|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/abhiunix/community-registry --skill model-usage-abhiunix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: model-usage
Source: https://github.com/abhiunix/community-registry/tree/main/skills/development/model-usage
Command: npx skills add https://github.com/abhiunix/community-registry --skill model-usage-abhiunix

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

CodexBar generates per-model usage costs from local logs, making cost visibility and tracking effortless.

Core Features & Use Cases

  • Per-model cost aggregation from daily modelBreakdowns logs for Codex or Claude.
  • Current-model views with latest daily cost and total model costs; all-model views with ranked totals.
  • Quick integration with downstream tooling via JSON or plain text outputs for dashboards and reporting.

Quick Start

Run the model_usage.py script to generate a per-model cost summary from CodexBar local logs.

Frequently Asked Questions about model-usage

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

FAQPage Schema
How do I track per-model AI usage costs from CodexBar local logs?

Track per-model AI usage costs from CodexBar local logs by running the model_usage.py script, which aggregates daily modelBreakdowns to provide cost totals for Codex or Claude.

Can I output model usage cost summaries in JSON for downstream dashboards?

Yes, you can output model usage cost summaries in JSON format, enabling quick integration with downstream tooling, reporting workflows, and cost tracking dashboards.

What is the best way to get a cost breakdown for all AI models used locally?

Get a cost breakdown for all AI models used locally by requesting an all-model view, which aggregates daily modelBreakdowns into ranked total costs across every model recorded in the logs.

How do I restrict cost tracking summaries to a specific day range?

Restrict cost tracking summaries to a specific day range by applying the optional day-restriction parameter, filtering the aggregated modelBreakdowns logs to calculate costs only for the specified period.

Does this tool require any external dependencies to aggregate model costs?

No, this tool requires no external dependencies to aggregate model costs, operating entirely on local CodexBar logs to generate per-model usage summaries without additional setup.

Why does my current-model cost snapshot show different totals than the all-model view?

A current-model cost snapshot shows the latest daily cost and total for one model, while the all-model view aggregates ranked totals across every model, causing apparent differences in the reported usage metrics.