majiayu000 Stats Tracker
Skill for tracking and analyzing Claude Code usage statistics.
When to Use
This skill activates when you:
- Want to see your usage statistics
- Track productivity over time
- Analyze model usage patterns
- Monitor usage streaks
- Plan based on usage limits
Keywords: stats, usage, analytics, productivity, streak, model usage, tokens, sessions, cost
Quick Commands
| Command | Description |
|---|---|
/stats |
View usage stats, streak, favorite model |
/usage |
View token usage and limits |
/context |
View current context usage |
/cost |
View session cost breakdown |
Understanding /stats Output
/stats
📊 Your Claude Code Stats
────────────────────────────
🏆 Favorite Model: Sonnet 4 (78% of sessions)
🔥 Current Streak: 12 days
📈 This Week: 847K tokens across 23 sessions
📉 Usage Graph: [▁▃▅▇█▆▄▂] (last 7 days)
Metrics Explained
| Metric | Description |
|---|---|
| Favorite Model | Most frequently used model |
| Current Streak | Consecutive days using Claude Code |
| This Week | Total tokens and sessions |
| Usage Graph | Visual of daily usage pattern |
Understanding /usage Output
/usage
📊 Usage This Period
────────────────────────────
Sonnet: ████████░░ 78%
Opus: ██░░░░░░░░ 15%
Haiku: █░░░░░░░░░ 7%
Resets: Monday 00:00 UTC
Model Selection Guide
Choose the right model for the task:
| Task Type | Model | Why |
|---|---|---|
| General coding | Sonnet | Best balance of speed/quality |
| Complex architecture | Opus | Deep reasoning, long context |
| Quick fixes | Haiku | Fast, efficient |
| Code exploration | Haiku (Explore) | Optimized for search |
| Documentation | Sonnet | Good writing quality |
| Bug investigation | Sonnet/Opus | Depends on complexity |
Cost Efficiency
| Model | Relative Cost | Best For |
|---|---|---|
| Haiku | $ | Quick tasks, exploration |
| Sonnet | $$ | Most development work |
| Opus | $$$ | Complex problems |
Daily Workflow with Stats
Morning Routine
1. /stats # Check streak, plan day
2. /usage # Check remaining budget
3. /rename feature-x # Name today's session
4. Start coding # Use appropriate model
During Development
# After complex task
/context # Check context usage
# When switching tasks
/stats # Quick progress check
End of Day
/stats # Review productivity
/usage # Check usage remaining
/cost # See session cost
Usage Optimization Strategies
If Usage is High
- Use Haiku more - For exploration and quick tasks
- Spawn Explore agents - Uses efficient Haiku model
- Background tasks - Don't consume extra tokens
- Be more targeted - Specific queries use less context
If Starting Fresh Week
- Plan major tasks - Allocate Opus for complex work
- Default to Sonnet - Best general-purpose model
- Reserve Haiku - For quick lookups and exploration
Maximizing Efficiency
# Good: Specific query
"Fix the null check on line 45 of auth.ts"
# Bad: Vague query (uses more context/tokens)
"Help me with the auth system"
Tracking by Feature
Use named sessions to track usage per feature:
# Start feature work
/rename billing-feature
# Work on feature...
# Check stats
/stats # See usage for this session
# Compare features
"How many tokens did billing vs auth use?"
Weekly Review Pattern
Every Friday:
1. /stats # Review week's usage
2. /usage # Check budget status
3. Note completions # What features finished?
4. Plan next week # Allocate model usage
Weekly Goals Template
Week Goals:
- [ ] Maintain 5-day streak
- [ ] Complete 3 features
- [ ] Use Opus only for architecture decisions
- [ ] Try Explore agent for research tasks
- [ ] Stay under 80% usage
Integration with Other Skills
With Session Manager
# Track stats per named session
/rename billing-feature
[work on feature]
/stats
# See usage specific to this session
With Context Manager
# Monitor both context and usage
/context # Current context budget
/stats # Overall usage patterns
With Async Runner
# Background tasks don't inflate usage
"Run build in background"
# Build output doesn't use tokens
Gamification Ideas
Streak Challenges
- 5-day streak: Bronze
- 10-day streak: Silver
- 30-day streak: Gold
- Try to never break your streak!
Model Efficiency Challenge
Challenge: Complete task with Haiku
1. Try Haiku first for any task
2. Escalate to Sonnet only if needed
3. Use Opus sparingly for max impact
Weekly Competition (Team)
- Compare completed features
- Compare usage efficiency
- Share tips for optimization
External Tools
ccusage (CLI Analytics)
# Install
npm install -g ccusage
# View usage
ccusage
# Daily breakdown
ccusage --daily
# Monthly view
ccusage --monthly
Claude Code Usage Monitor
Real-time terminal monitoring with:
- Token tracking
- Burn rate analysis
- Predictions for limits
CircleTel Productivity Patterns
Feature Development Session
Start: /rename feature-customer-billing
/stats # Baseline
Middle: [coding work]
/context # Check context
End: /stats # Compare to baseline
/cost # Session cost
Bug Fix Session
/rename BUG-1234-fix
/stats # Note starting point
[investigation and fix]
/stats # See investigation cost
# Typically: Sonnet for analysis, quick fixes
Architecture Planning
/rename architecture-review
# Use Opus for deep thinking
"Think about the best approach for..."
/stats # Higher usage expected
/cost # Worth it for good architecture
Best Practices
- Check stats daily - Start with
/stats - Match model to task - Don't use Opus for simple fixes
- Track by feature - Use named sessions
- Review weekly - Adjust workflow based on patterns
- Use Haiku for exploration - Spawn Explore agents
- Background for builds - Don't waste tokens on output
- Targeted queries - Specific questions = efficient usage
Troubleshooting
Stats seem wrong
# Check current session specifically
/cost
# Check usage for period
/usage
High usage unexpectedly
- Check for large file reads
- Review if background tasks are actually background
- Consider if queries could be more specific
Streak reset
- Streak requires at least one interaction per day
- Even
/statscounts - Check timezone (UTC-based)
Version: 1.0.0 Last Updated: 2025-12-10 For: Claude Code v2.0.64+