claude-code-usage

What This Skill Does

The claude-code-usage skill is an essential utility for developers relying on the Claude Code CLI. It provides real-time visibility into your API consumption, specifically tracking your 5-hour session window and 7-day weekly quota. By interacting directly with the Anthropic OAuth API, this tool ensures you are never surprised by rate-limiting mid-task. It features a sophisticated CLI interface that translates raw API data into visual progress bars, status indicators, and actionable reset timestamps.

Installation

To integrate this into your OpenClaw environment, execute the following command:

clawhub install openclaw/skills/skills/azaidi94/claude-code-usage

Ensure that you have your Claude Code CLI already authenticated on your machine, as the skill relies on existing system credentials stored in your macOS Keychain or Linux secret-tool.

Use Cases

• Proactive Capacity Planning: Check your usage levels before starting a large refactoring task to ensure you won't hit a rate limit.
• Workflow Automation: Integrate output into your terminal status line or status bars using the JSON flag for machine-readable data.
• Automated Alerts: Utilize the session-reminder.sh script to set up a self-scheduling chain that notifies you exactly when your session resets, allowing you to maximize your coding sessions without manual polling.
• Monitoring: Track long-term consumption trends to manage your overall development velocity against weekly limits.

Example Prompts

1. "How much usage do I have left on my Claude Code session today?"
2. "Am I close to hitting my weekly rate limit for Claude Code?"
3. "Can you check my current Claude Code quotas and tell me when they reset?"

Tips & Limitations

• Caching: By default, the tool caches results for 60 seconds. If you need absolute precision after a heavy coding burst, use the --fresh flag.
• Environment: The skill requires functional system credential storage. If you run into authorization issues, re-authenticate the base Claude Code CLI first.
• Automation: For power users, the session reminder script is highly recommended to offload the burden of manual monitoring. If the cron job setup feels intrusive, stick to simple terminal aliases for quick --fresh checks.