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

Source: Dev.to

If you’re vibe‑coding with Claude Code, measure what actually ships to production.

npx claude-roi

The tool shows:

• 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.

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
yarn global add claude-roi

Then run from anywhere:

claude-roi

Option 3: Clone and run from source

git clone https://github.com/Akshat2634/Codelens-AI.git
cd Codelens-AI

# Install dependencies (pick one)
npm install      # or
pnpm install     # or
yarn install

# Run it
node src/index.js

---

Prerequisites

• Node.js ≥ 18 – Download
• Git – installed and configured

---

Source & Contributions

View on GitHub – open source; PRs, feature requests, and ⭐ are welcome.

---

Track your AI ROI now!