model-usage

Summarize CodexBar cost usage by model from JSON input.

87|20|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/openaeon/OpenAEON --skill model-usage-openaeon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: model-usage
Source: https://github.com/openaeon/OpenAEON/tree/main/skills/model-usage
Command: npx skills add https://github.com/openaeon/OpenAEON --skill model-usage-openaeon

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires codexbar, python, json, subprocess, and includes scripts (resource) and references (resource) components.

What problem does it solve?

It helps you quickly understand which Codex or Claude models you actually used and what they cost, without manually digging through raw local logs.

Core Features & Use Cases

  • Per-model cost summaries: Produces a readable breakdown for either the current (most recent) model or totals across all available models.
  • JSON-driven and scriptable: Works from CodexBar CLI output (directly or via an input JSON file/stdin) and can emit JSON for automation.
  • Current-model logic: Detects the most recent daily entry and selects the model with the highest cost within that entry, with a fallback to the last modelsUsed value when breakdowns are missing.

Use case: You want to compare spending patterns across different Codex/Claude models from local CodexBar logs and decide which models to prioritize.

Quick Start

Ask the AI to run the model usage summary for Claude across all local cost entries by using CodexBar CLI JSON as input.

Frequently Asked Questions about model-usage

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

FAQPage Schema
How do I summarize per-model cost usage from CodexBar local logs?

You can summarize per-model usage by running the Skill with CodexBar cost JSON as input, which it reads from the CLI or a file to compute totals from modelBreakdowns for each Codex or Claude model.

Can I output the model usage cost breakdown as JSON for automation?

Yes, the Skill can output per-model cost summaries as JSON instead of text, allowing you to use the computed totals from modelBreakdowns in automation and budgeting workflows.

How does the Skill detect the current model from daily cost entries?

The Skill detects the current model by selecting the model with the highest cost from the most recent daily entry, with a fallback to the last modelsUsed value when breakdowns are missing.

Do I need Python and subprocess to run the CodexBar cost analysis?

Yes, the Skill requires Python and subprocess dependencies to execute scripts that parse CodexBar cost JSON and compute per-model totals from local telemetry data.

What is the best way to compare spending patterns across different Claude models?

The best way to compare spending patterns is to generate a full historical model breakdown from CodexBar cost JSON, which computes totals across all models to help you decide which Claude or Codex models to prioritize.

Limitations of using local telemetry JSON for model cost analysis?

A limitation is that the analysis depends on modelBreakdowns in the CodexBar JSON; if breakdowns are missing, the Skill falls back to the last modelsUsed value, reducing per-model cost accuracy.