Most of us optimize prompts. Very few of us optimize ROI. Here's what I found tracking my Claude Code spend.

If you’re vibe coding with Claude Code, measure what ships to production. Run this: npx claude-roi See what made it to git vs what just burned tokens. Cost per commit. Orphaned sessions. Line survival. And many more insights. Most of us are optimizing prompts. Very few of us are optimizing ROI. All local. Open source. GitHub: Akshat2634 / Codelens-AI Agent Productivity-to-Cost Correlatorcodelens-ai Codelens AI Agent Productivity-to-Cost Correlator — Is your AI coding agent actually shipping code? Codelens AI ties Claude Code token usage to actual git output. It reads your local Claude Code session files, correlates them with git commits by timestamp, and serves a dashboard answering: "Am I getting ROI from my AI coding agent?" One command, zero config All data stays local Works with any git repo where you've used Claude Code Installation Option 1: Run directly (no install) npx claude-roi Option 2: Install globally # npm npm install -g claude-roi # pnpm pnpm add -g claude-roi # yarn yar