Use CodexBar CLI local cost usage to summarize per-model usage for Codex or Claude, including the current (most recent) model or a full model breakdown. Trigger when asked for model-level usage/cost data from codexbar, or when you need a scriptable per-model summary from codexbar cost JSON.
Data sourced from ClawHub. View on ClawSkills
Select your agent
Option 1: Install via CLI (recommended)
Recommended (no pre-install needed)
npx clawhub@latest --dir ~/.claude/skills install model-usageOr via clawhub CLI (if already installed)
clawhub --dir ~/.claude/skills install model-usageβ οΈ Requires Node.js 18+. No Node? Use Option 2 below to download the ZIP instead. Install Node.js β
Option 2: Manual install (no Node required)
Download the ZIP, extract it, and place the folder at the path below. Restart your agent to activate.
Install path
~/.claude/skills/model-usage/π‘Extract and place the folder at the path above, then restart your agent.
What Model Usage can do for your AI workflow
Codexbar cli local cost usage directly from your Claude conversation
Works across Claude, Cursor, OpenClaw β install once, use everywhere
Trusted by 32,419+ developers worldwide
One-command installation β no complex setup required
Combine with other skills to build powerful multi-step AI workflows
Try these prompts with your AI agent after installing Model Usage
Help me get started with Model Usage
Explains what Model Usage does, walks through the setup, and runs a quick demo based on your current project
Use Model Usage to use CodexBar CLI local cost usage to summarize per-model usage for ...
Invokes Model Usage with the right parameters and returns the result directly in the conversation
What can I do with Model Usage in my developer & devops workflow?
Lists the top use cases for Model Usage, with example commands for each scenario
Guides & tutorials for AI skills
10 Fresh GitHub Agent Skills Added in June 2026
A hand-checked shortlist of recently updated GitHub agent skills that were not already in our catalog, excluding marketplaces, awesome lists, managers, and generic skill directories.
The 7 AI Skills Every Software Developer Should Have Installed in 2026
After testing dozens of developer-focused AI skills, these are the seven that have proven genuinely useful across different tech stacks and workflows β not just impressive demos, but tools that hold up under daily use.
Model Usage extends your AI assistant with the ability to use CodexBar CLI local cost usage to summarize per-model usage for Codex or Claude, including the current (most recent) model or a full model breakdown. Trigger when asked for model-level usage/cost data from codexbar, or when you need a scriptable per-model summary from codexbar cost JSON. Rather than leaving your conversation to handle this manually, you can ask your Claude agent directly β and it will take care of the task end-to-end, using Model Usage as its underlying capability.
Model Usage works across Claude, Cursor, OpenClaw through the Model Context Protocol (MCP) β an open standard that lets AI clients share tools and skills without lock-in. Because MCP is platform-agnostic by design, you install Model Usage once and it becomes available across all your AI clients. Whether you're working in Claude for focused sessions or Cursor for integrated workflows, the skill behaves consistently.
Model Usage installs like any other MCP skill: drop the folder into `~/.claude/skills/model-usage/` for global access, or `.claude/skills/model-usage/` to keep it scoped to one project. After a quick restart of Claude, you can trigger it explicitly with `/model-usage`, or let the AI decide when it's the right tool for your request.
With 32,419 installs, Model Usage has built a substantial following in the Developer & DevOps space. That install count reflects consistent demand from developers and teams who've found it genuinely useful. Like all skills on DiscoverAISkills, it is free to install and use. The broader AI skills ecosystem continues to expand as developers contribute new capabilities across categories like developer tools, data analysis, writing, automation, and more.
Place the skill folder at ~/.claude/skills/model-usage/ for personal use (all projects), or .claude/skills/model-usage/ for project-specific use. Restart your AI client, then invoke with /model-usage or let the AI discover it automatically.
Model Usage supports Claude, Cursor, OpenClaw. It integrates seamlessly with these AI platforms to extend their capabilities.
Model Usage is free to install. Check the repository for licensing information.
Use CodexBar CLI local cost usage to summarize per-model usage for Codex or Claude, including the current (most recent) model or a full model breakdown. Trigger when asked for model-level usage/cost data from codexbar, or when you need a scriptable per-model summary from codexbar cost JSON.
Model Router
A comprehensive AI model routing system that automatically selects the optimal model for any task. Set up multiple AI providers (Anthropic, OpenAI, Gemini, Moonshot, Z.ai, GLM) with secure API key storage, then route tasks to the best model based on task type, complexity, and cost optimization. Includes interactive setup wizard, task classification, and cost-effective delegation patterns. Use when you need "use X model for this", "switch model", "optimal model", "which model should I use", or to balance quality vs cost across multiple AI providers.
Model Router
Route model requests based on configured models, costs and task complexity. Use for routing general/low-complexity requests to the cheapest available model and for higher-complexity requests to stronger models.
Category
π»Developer & DevOpsAutomate my developer & devops tasks using Model Usage
Identifies repetitive steps in your workflow and sets up Model Usage to handle them automatically
Model Usage is categorized under Developer & DevOps. These skills help AI agents perform specialized tasks in this domain.
Model Alias Append
Automatically appends the model alias to the end of every response with integrated hook functionality and configuration change detection. Use when transparency about which model generated each response is needed. Use when: providing model transparency, tracking which model generated responses, monitoring configuration changes, or ensuring response attribution.