model-usage

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

117|8|Updated Jan 20, 2026
One-click install
npx skills add https://github.com/geezerrrr/motive --skill model-usage-geezerrrr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: model-usage
Source: https://github.com/geezerrrr/motive/tree/main/Motive/Resources/Skills.bundle/model-usage
Command: npx skills add https://github.com/geezerrrr/motive --skill model-usage-geezerrrr

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Per-model usage costs from CodexBar's local logs are hard to compute manually, slowing cost awareness and model comparison.

Core Features & Use Cases

  • Trigger on demand: summarize model-level usage data from CodexBar logs when asked or to feed automation.
  • Supports current-model (latest daily) and all-model breakdowns for Codex or Claude.
  • Outputs text or JSON to integrate into reports, dashboards, or automation pipelines.

Quick Start

Ask Motive to summarize CodexBar usage for the current or all models using the 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 summarize per-model usage costs from CodexBar local logs?

Summarize per-model usage costs from CodexBar local logs by processing local JSON data with optional date filtering to output human-readable text or JSON for current-model or all-model breakdowns.

What's the best way to compare Codex and Claude model usage costs locally?

Compare Codex and Claude model usage costs locally by summarizing all-model totals from CodexBar's local JSON logs, applying optional date filtering to isolate specific usage periods.

Do I need the CodexBar CLI on PATH to analyze local cost logs?

You need the CodexBar CLI on PATH and access to the local cost JSON logs to analyze per-model usage costs, as the summarization process reads directly from those local JSON files.

Can I output model usage summaries as JSON for automation pipelines?

You can output model usage summaries as JSON for automation pipelines by using the appropriate flags, switching from human-readable text to structured JSON data for reports and dashboards.

How does local JSON date filtering work for current-model summaries?

Local JSON date filtering restricts current-model summaries to specific time ranges, processing the latest daily usage data from CodexBar logs to calculate costs for targeted periods.