model-usage

Summarize per-model CodexBar costs from local JSON logs.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/lalomorales22/penguins --skill model-usage-lalomorales22
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: model-usage
Source: https://github.com/lalomorales22/penguins/tree/main/skills/model-usage
Command: npx skills add https://github.com/lalomorales22/penguins --skill model-usage-lalomorales22

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

CodexBar cost data is often stored locally and scattered; this skill consolidates per-model usage and spend into an accessible summary.

Core Features & Use Cases

  • Summarize per-model costs from CodexBar's local cost JSON logs for Codex or Claude.
  • Identify the current top-cost model or provide a full per-model breakdown for cost analysis.
  • Use case: quickly identify which models contribute most to spend and compare across providers.

Quick Start

Run the bundled script to summarize per-model CodexBar costs from the local JSON log.

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 usage costs from local CodexBar logs?

You can summarize per-model usage costs by running a script that parses the CodexBar cost payload, aggregates expenses from modelBreakdowns, and outputs a text or JSON summary for Codex and Claude models.

Can I identify which model is currently contributing the most to my API spend?

Yes, you can detect the current top-cost model by parsing the local cost JSON logs and comparing the aggregated expenses across the available modelBreakdowns.

What is the best way to compare AI model costs across different providers like Codex and Claude?

The best way to compare provider costs is to aggregate per-model spend from local CodexBar logs, which supports a full per-model breakdown to help you identify which models contribute most to your overall costs.

How do I parse CodexBar cost data to output a structured JSON breakdown?

You can parse the CodexBar cost payload by applying a script that extracts and aggregates model costs from the modelBreakdowns field, allowing you to output the results directly in a structured JSON format.

Does this cost aggregation approach work with locally stored JSON files only?

No, the cost aggregation works with both local CodexBar logs and provided JSON data, allowing you to parse and summarize per-model usage costs from either source.

Why do I need to aggregate model costs from the modelBreakdowns field?

Aggregating costs from the modelBreakdowns field is necessary because CodexBar cost data is often scattered locally, and consolidating it provides an accessible summary to quickly identify your top-cost models.