I've been building Claude Code tools for the past 60 days — mostly because I couldn't stop asking "wait, how much time am I actually spending on this?"

The result is 41 zero-dependency tools. Some examples:

- *cc-wrapped*: Spotify Wrapped for Claude Code — drag in your ~/.claude folder, get a visual year-in-review - *cc-session-stats*: Session durations, streaks, health warnings if you've gone 3+ hours without a break - *cc-agent-load*: How much time is actually YOU vs AI subagents? Mine is 35% me, 65% AI - *cc-ghost-log*: "Ghost Days" — days you had zero Claude Code sessions but committed code anyway - *cc-impact*: What did you actually build? Commits, lines added, files changed across all your repos - *cc-peak*: When are you most focused? Hour-of-day heatmap + optimal 4-hour working window - *cc-collab*: Are you getting better at working with Claude Code? Weekly commits-per-hour efficiency trend - *cc-focus*: Are you spreading too thin? Weekly project scatter — mine went from 4 projects to 1 (converging -40%) - *cc-score*: 0–100 productivity score. I'm 89/100 (A — Power User) - *cc-burnout*: Same data, different angle. My burnout risk: 60/100 (High). High score ≠ sustainable. - *cc-monthly*: Monthly retrospective in Markdown — paste it straight into your dev blog - *cc-predict*: The only forward-looking tool — projects your month-end stats based on last 14 days

All 41 tools are free, MIT licensed, zero dependencies. Most run in browser (no install), CLI versions available via npx.

The raw numbers from 60+ days: 3,580 sessions, 142 hours, 40 Ghost Days, 563 commits, +305k net lines.

Full data story at: https://yurukusa.github.io/cc-story/