Skip to content

For Claude Code & Codex users

Your report card for vibe coding

Vibemetric scores how you work with Claude Code and Codex and recommends what to change, so you:

  • Ship faster
  • Build better
  • Save tokens
Terminal
45
45/ 100Jul 6
  • Planning & Specs3
  • Context Engineering5
  • Memory & Knowledge5
  • Tool Integration6
  • Orchestration I: Task Mapping4
  • Orchestration II: Feedback Loops5
  • Testing & Evals5
  • Human Steering6
  • Security3
  • Efficiency & Cost3

Next: Write the pass/fail checks before the AI starts

Built by engineers from

  • LinkedIn
  • Intel
  • eBay

Know your baseline. Then raise it.

  1. See where you stand

    • You used your most expensive model to translate a short email. Those tokens were wasted.
    • You asked for “a login page” without saying what done looks like, so the AI built it twice.
    • Your sessions ran with every permission check off, and nothing stopped a push to main.
    65/ 10010 DIMENSIONS

    You give AI real tools it keeps reusing, and it checks live behavior on its own. But you rarely say what “done” means up front, so design tasks end in rounds of taste corrections.

    • Planning & Specs4
    • Context Engineering7
    • Memory & Knowledge7
    • Tool Integration9
    • Orchestration I: Task Mapping6
    • Orchestration II: Feedback Loops7
    • Testing & Evals8
    • Human Steering8
    • Security5
    • Efficiency & Cost4
  2. Know what to fix

    • Ask the AI to write down what done looks like before it writes any code.
    • Add a hook that blocks pushes to main, even when permission checks are off.
    • Send translations and short edits to a small, cheaper model.

    PLANNING & SPECS

    Problem: You asked for “a login page” without saying what done looks like.

    Prompt: Agree on done before the AI starts

    Before you write code, list what a user must be able to do and how we will check it. Wait for my OK.
  3. Ship better work

    • You are now making 80% more commits and shipping your product 2.5 times faster.
    • The AI gets a task right on the first try twice as often, so you redo far less work.
    • You spend 40% fewer tokens on the same amount of work.
    91/ 100+52 since Apr 6
    Apr 6Sep 21

    Security58

    Efficiency & Cost47

The rubric

10 dimensions, 100 points.

  • Planning & Specs

    Do you and the AI agree on the outcome, how it’s checked, and the constraints before work starts?

  • Context Engineering

    Does each project have a concise, well-structured CLAUDE.md or AGENTS.md that covers what AI must know, kept current?

  • Memory & Knowledge

    Is AI memory kept accurate, so stale or mixed-up memories don’t cause mistakes?

  • Tool Integration

    Does your recurring work run through tools and skills by default, and do you share the proven ones?

  • Orchestration I: Task Mapping

    Is the work broken into the right pieces and wired together: order, inputs and outputs, and who does each?

  • Orchestration II: Feedback Loops

    Do results decide the next step (fix, recheck, stop, escalate) and does the loop improve from experience?

  • Testing & Evals

    Is checking a habit: tests that fit each project, real-flow checks of changes, and regular evals for AI features?

  • Human Steering

    Do you examine the AI’s work and redirect it with clear reasons, then check the effect?

  • Security

    Is the agent limited to what each task needs, and is what it builds checked for security problems?

  • Efficiency & Cost

    Do models, effort, and usage match each task’s difficulty, adjusted from actual results?

PRIVACY FIRST

Vibemetric never sees your transcripts.

Your sessions are read on your Mac and scored by your own Claude Code or Codex, under your own account. Here’s exactly what happens to them.

No Vibemetric server sees them

Scoring runs through your own Claude Code or Codex, exactly as when you use it yourself. The free app has no account, and Vibemetric’s server never receives your sessions. Pro only sends your API key to check your plan.

Read-only, all the way down

Vibemetric never writes to ~/.claude or ~/.codex. The Claude run it starts can only Read, Grep and Glob. No shell, no edits, no web.

Secrets are stripped first

Before anything is read, the digest removes API keys, tokens, webhook URLs and database connection strings it recognizes.

You decide what stays

Each result keeps its redacted digest on your Mac until you delete the result. Your CLI saves the scoring run in its history, but Vibemetric leaves it out of later scores, so it can’t skew them.

Pricing

Your score is free. Pro helps you raise it.

Free

$0forever

The full score, on your Mac. Open source.

  • AI Native Score out of 100
  • All 10 dimensions, each with the case that earned it
  • Recommendations for every dimension
  • Score history with what changed since last time
  • Menu bar score, Markdown and image export

Pro

$9.99per month

7-day free trial

Everything in Free, plus tools and progress from our server.

  • Specific tool picks for each dimension, with setup steps
  • A curated tool catalog, updated every week
  • How you compare with other Vibemetric users
  • Progress over time, and whether each change worked
  • Team view: see your team’s scores, gaps, and trends

Then $9.99 per month. Cancel anytime.

Questions

What does it cost?

The app and the full score are free. Pro is $9.99 a month or $99 a year, with a 7-day free trial, and adds tool picks, comparisons, progress tracking and a team view. Scoring itself runs on your existing Claude plan through the claude command you already have installed, like any other Claude Code session.

Which tools does it read?

Claude Code and Codex today, including Claude Code subagent transcripts. Cursor and Grok are next.

Why does scoring take five minutes?

The rubric only counts connected evidence: a rule saved in one session and used in a later one, or a failed check that was fixed and rerun. Finding those takes reading, not counting.

Is the score stable?

Scores come from an AI reviewer, so they can move a point or two between runs. Reasons always cite the sessions they come from, so you can check them.

Why does macOS ask before it opens the app?

macOS asks once about any app downloaded from the internet. Vibemetric is signed and notarized by Apple, so click Open. Updates install automatically after that.

Get your score.

Open the .dmg, drag Vibemetric into Applications, and open it. Needs Claude Code or Codex installed and signed in.

macOS 14+ · Apple Silicon and Intel · 5 MB download

Download for Mac