VibeScore CLI

The build

Parsed from a ccusage report covering 1 session.

How to read this: Active build time is measured from this project’s Claude Code session transcripts. A pause of more than 30 minutes between a reply and the next instruction counts as time away, not build time; Claude’s own turns always count, so a long autonomous run is work rather than idle. Wall-clock is the plain span from first activity to last. Cost is the API-equivalent value of the tokens this build consumed, priced at published per-token rates. It is not necessarily money anyone paid — on a flat-rate subscription the same work is covered by the monthly fee. Where two figures are shown above, the first is this app’s launch stats — its first snapshot — and the smaller one after the slash is its cumulative total as of the latest snapshot. Full history is below.

About

vibescore-cli reads the session logs Claude Code already keeps on your machine and reports what one project cost to build: tokens, cost, and time to ship. Nothing is uploaded; it prints to your terminal and you choose what to paste. What it does vibescore-cli turns the transcripts Claude Code already writes to ~/.claude/projects into a submission-ready report for one project: the folder you run it from, and anything nested under it. It joins your session data with ccusage's per-model price table to report token counts, cost, and two measures of build time: active time (you and Claude actually working) and wall-clock time (first activity to last). Run it, paste the output on the submit page, done. npx --yes vibescore-cli | pbcopy Why it's safe to run Read-only. It only reads existing local log files. It doesn't touch your code, your git history, or anything outside ~/.claude/projects. Nothing is uploaded. The command writes to stdout. What happens to that output, clipboard, a file, nowhere, is entirely your call. No file paths in the report. Only a project's bare folder name is included, so pasting a report never discloses your directory layout. Open source, MIT licensed. The full source is on GitHub, so you can read exactly what it does before you run it. No install prompt slipped through. --yes isn't a convenience flag, it's what stops npx from writing its install confirmation into the piped output instead of your report.

Stack