Per-model cost summaries from CodexBar CLI logs for Codex or Claude providers.
Works with
Supports two summary modes: \"current\" (most recent daily model with highest cost) and \"all\" (full model breakdown across all logged days)
Accepts input via live CodexBar CLI invocation, JSON file, or stdin; outputs as plain text or formatted JSON
Requires CodexBar CLI installed locally (macOS only via Homebrew; Linux support pending)
Falls back to last entry in modelsUsed when model breakdowns are u
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionmodel-usageExecute the skills CLI command in your project's root directory to begin installation:
Fetches model-usage from steipete/clawdis and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate model-usage. Access via /model-usage in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
350.1K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
350.1K
stars
Get per-model usage cost from CodexBar's local cost logs. Supports "current model" (most recent daily entry) or "all models" summaries for Codex or Claude.
TODO: add Linux CLI support guidance once CodexBar CLI install path is documented for Linux.
python {baseDir}/scripts/model_usage.py --provider codex --mode current
python {baseDir}/scripts/model_usage.py --provider codex --mode all
python {baseDir}/scripts/model_usage.py --provider claude --mode all --format json --pretty
modelBreakdowns.modelsUsed when breakdowns are missing.--model <name> when you need a specific model.codexbar cost --format json --provider <codex|claude>.codexbar cost --provider codex --format json > /tmp/cost.json
python {baseDir}/scripts/model_usage.py --input /tmp/cost.json --mode all
cat /tmp/cost.json | python {baseDir}/scripts/model_usage.py --input - --mode current
--format json --pretty).references/codexbar-cli.md for CLI flags and cost JSON fields.Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
I recommend model-usage for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
We added model-usage from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: model-usage is the kind of skill you can hand to a new teammate without a long onboarding doc.
Solid pick for teams standardizing on skills: model-usage is focused, and the summary matches what you get after install.
model-usage is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
model-usage reduced setup friction for our internal harness; good balance of opinion and flexibility.
Registry listing for model-usage matched our evaluation — installs cleanly and behaves as described in the markdown.
model-usage fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for model-usage matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in model-usage — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 45