Monitors and analyzes Claude Code usage in real-time. Helps operations teams track API calls, usage patterns, and costs. Integrates with CLI and terminal workflows for easy deployment.
git clone https://github.com/paulrobello/par_cc_usage.gitMonitors and analyzes Claude Code usage in real-time. Helps operations teams track API calls, usage patterns, and costs. Integrates with CLI and terminal workflows for easy deployment.
[{"step":"Install the par_cc_usage CLI tool by running `pip install par-cc-usage` or `brew install par-cc-usage`. Ensure you have API access credentials configured in your environment.","tip":"Use `par_cc_usage --setup` to configure default tracking parameters like cost thresholds or alert channels."},{"step":"Run a baseline scan to establish normal usage patterns. Execute `par_cc_usage --baseline --days 7` to generate a 7-day report. Compare this against real-time data to identify anomalies.","tip":"Store the baseline report in your team's documentation (e.g., Notion or Confluence) for future reference."},{"step":"Set up real-time monitoring with `par_cc_usage --monitor --interval 5m`. This will track usage every 5 minutes and alert you to spikes via Slack, email, or webhook.","tip":"Configure alerts in `par_cc_usage --config alerts.json` to notify specific team members (e.g., DevOps or team leads) based on usage thresholds."},{"step":"Generate actionable reports for stakeholders. Use `par_cc_usage --report --team engineering --format markdown` to create a summary for your engineering team. Export raw data with `par_cc_usage --export --format csv` for finance or auditing.","tip":"Schedule automated reports with cron (e.g., `0 9 * * 1-5 par_cc_usage --report --team engineering`) to share weekly updates."},{"step":"Optimize usage based on recommendations. Use the `par_cc_usage --optimize --project [PROJECT_NAME]` command to get project-specific suggestions, or manually review the exported data in tools like Google Sheets or Tableau.","tip":"Combine par_cc_usage with Claude Code's built-in logging (e.g., `claude --log-level debug`) for deeper debugging of high-usage scenarios."}]
No install command available. Check the GitHub repository for manual installation instructions.
git clone https://github.com/paulrobello/par_cc_usageCopy the install command above and run it in your terminal.
Launch Claude Code, Cursor, or your preferred AI coding agent.
Use the prompt template or examples below to test the skill.
Adapt the skill to your specific use case and workflow.
Monitor and analyze Claude Code (par_cc) usage in real-time for [TEAM/ORGANIZATION]. Track [SPECIFIC_METRICS: API calls, token usage, cost, or performance bottlenecks] over the last [TIME_PERIOD: 24 hours/7 days]. Flag any anomalies or unexpected spikes in usage. Provide a summary of top contributors and suggest optimizations to reduce costs or improve efficiency. Output should include actionable recommendations for [TEAM_LEAD/DEVOPS_ENGINEER].
### Claude Code Usage Report - Engineering Team (Last 24 Hours) **Summary:** Total API calls: 12,487 (↑ 18% from baseline of 10,500) Total tokens processed: 4.2M (↑ 22%) Estimated cost: $187.34 (↑ $32.10 vs. daily average of $155.24) **Top 5 Highest Usage Projects:** 1. **Project Alpha** (AI-Powered Chatbot): 3,214 calls, 1.1M tokens 2. **Project Beta** (Data Pipeline): 2,890 calls, 980K tokens 3. **Project Gamma** (API Gateway): 1,765 calls, 650K tokens 4. **Project Delta** (Internal Tooling): 1,432 calls, 520K tokens 5. **Project Epsilon** (Legacy Migration): 987 calls, 310K tokens **Anomalies Detected:** - Project Alpha shows a 35% spike in API calls between 2:00 AM - 4:00 AM UTC (likely a batch processing job). - Project Gamma has 15% higher token usage per call than average (potential inefficiency in prompt design). **Cost Optimization Recommendations:** 1. **Project Alpha:** Implement caching for frequent queries to reduce redundant API calls. Potential savings: ~$45/day. 2. **Project Beta:** Review the data pipeline logic—consider batching smaller operations into larger chunks. Potential savings: ~$30/day. 3. **Project Gamma:** Audit prompt templates for verbosity. A 10% reduction in token count could save ~$18/day. **Action Items:** - [ ] Schedule a review with Project Alpha team to discuss caching strategy. - [ ] Run a token-efficiency audit for Project Gamma prompts. - [ ] Set up automated alerts for usage spikes >20% above baseline. **Next Steps:** Run `par_cc_usage --export --format csv` to generate a detailed report for finance. Flag the 2:00 AM - 4:00 AM window in Project Alpha for further investigation.
Accounting software with automated invoicing and reporting
AI assistant built for thoughtful, nuanced conversation
IronCalc is a spreadsheet engine and ecosystem
Customer feedback management made simple
Enterprise workflow automation and service management platform
Automate your spreadsheet tasks with AI power
Take a free 3-minute scan and get personalized AI skill recommendations.
Take free scan