earlyink
134 first flagged16 Oct 2026

Review Bill: predict what an agent code review will cost before the PR lands

GitHub Action that scores PR code health and estimates agent-review token spend for teams paying per token.

Early · Pre-registered study links CodeHealth to cost

Written for: Solo builder

Next step

Read the paper for which health factors drive cost, build an Action using lizard or radon metrics, and backtest it on 50 public agent-authored PRs. Share the results in the Claude Code GitHub discussions.

Why now

Teams now hand code review to multi-agent pipelines billed per token, while agent-written PR volume keeps climbing. A cost estimate before review, plus a nudge to clean up unhealthy files first, fits the cost-per-task theme from earlier cards and is new in CI. Market pull is weak until review bills get large.

What became possible

A pre-registered study of 465 agent-authored pull requests from 246 repositories tests whether baseline CodeHealth predicts the token cost of agentic review and fixes beyond PR size. The paper's title reports that it does.

One way in

  1. review-bill Action

    Comments on each PR with a code-health score built from open complexity metrics and an estimated review-cost band, calibrated on public agent PRs.

    Customer
    Small teams running Claude Code or CodeRabbit-style review on every PR
    Model
    Free for public repos, $20 a month per private org

Competition

Early

I found no tool that predicts what an AI code review of a specific PR will cost before it runs, priced for the reviewer you actually use (Claude Code Review, CodeRabbit overage per file, Greptile credits, Copilot credits). What exists falls into three groups.

Full competition notes (12 competitors)

I found no tool that predicts what an AI code review of a specific PR will cost before it runs, priced for the reviewer you actually use (Claude Code Review, CodeRabbit overage per file, Greptile credits, Copilot credits). What exists falls into three groups. Vendors show averages and spend caps after the fact. Calculators and blog tables estimate at the team level. CI cost gates like ci-guardrail, tokentoll, TokenFlow and TokenDam measure the LLM spend of the app or of the agent that wrote the code, not of the reviewer. The code-health score on its own is crowded. pr-health-agent, Typo and react-doctor already do it, and established code-quality vendors give it away, so it shouldn't be what you sell. Your opening is the cost forecast for each PR. Make it accurate per vendor and use it to drive action: hold back or downgrade the review on PRs likely to be expensive, warn when a PR is likely to land in an outlier band like the reported $107 reviews, and suggest splitting the PR to save money. Calibrating on public agent PRs is a reasonable start, but an edge that lasts would come from adjusting the model against each team's real review bills. The risks are that the cost-gate tools and vendors like repowise and Codacy, who already write about cost per PR, are a short step away. Anthropic or GitHub could also add a pre-review estimate in their own products. And if review pricing moves to flat per-seat plans, the problem disappears, so this is a narrow, early opening rather than open space.

  • Claude Code Review (Anthropic)

    This is the service whose cost you'd be predicting. Anthropic says reviews average $15 to $25 and scale with PR size and complexity. Admins get a monthly spend cap and a choice of when reviews trigger, but I found no estimate shown before a review runs. One user reported paying $214 for two reviews, which shows how far bills can stray from the average.

  • GitHub Copilot code review billing

    A third-party guide says GitHub gives rough per-review credit ranges by tier: $0.05 to $1 on Lite and $0.25 to $5 on Balanced. These are published ranges, not a forecast for each PR.

  • Arnica AI Code Scanning Cost Calculator

    A free web calculator that estimates the yearly bill from team size and PRs per month, using fixed per-PR figures. It works at the team level, not per PR, and doesn't plug into CI.

  • ai-cost-estimator.com

    Blog content with tables of token use and cost by PR size. It's the same idea as your calibration, but as articles rather than a tool that comments on PRs.

  • repowise

    A vendor writing about review cost per PR at agent volume, plus a 200-PR budget for Claude Code Review. They clearly care about this topic and could add a feature for it.

  • ci-guardrail (wartzarbee)

    A GitHub Action that estimates how much a PR changes token cost, comments on the files responsible, and can fail the build or only warn. It's aimed at the runtime token cost of agent code, not the cost of reviewing the PR, but the mechanics are almost the same.

  • tokentoll

    Scans Python and JS/TS for LLM API calls and gives each PR a PASS, WARN or FAIL against a policy file. It covers app LLM spend, not review spend.

  • TokenFlow

    Reads local logs from Claude Code, Codex and Cursor and posts the agent's cost on the PR as a comment and status check, with budgets. It reports what was spent writing the code, not what reviewing it will cost.

  • TokenDam

    A linter for LLM token spend, with a GitHub App that fails builds when costs go up. It launched recently and has little traction.

  • pr-health-agent

    A Python command-line tool that scores PR health out of 100 across 13 categories, including complexity, and posts the result as a PR comment. This overlaps with the code-health score half of your idea.

  • Typo PR Health

    A commercial PR health score weighted on diff size, files changed and cyclomatic complexity. It also covers the code-health half.

  • react-doctor GitHub Action

    A health-score Action (0 to 100) for React codebases that comments on PRs. It only covers React.

Checked 2026-10-16

Risks

  • CodeHealth is a CodeScene metric, and open proxies may predict cost less well
  • Effect size may be too small to change behaviour
  • GitHub or review vendors can add a cost estimate natively

Strong team fit; market pull is the weak point (4).

tech 6 · pull 4 · space 7 · fit 8 · build 7

Exposed

Companies that could benefit or be threatened. News and context, not investment advice.

Momentum of its main topic

67 developments this week +27 vs last week
21 Sep: 0 developments22 Sep: 0 developments23 Sep: 0 developments24 Sep: 0 developments25 Sep: 0 developments26 Sep: 0 developments27 Sep: 0 developments28 Sep: 0 developments29 Sep: 0 developments30 Sep: 0 developments1 Oct: 0 developments2 Oct: 0 developments3 Oct: 0 developments4 Oct: 0 developments5 Oct: 0 developments6 Oct: 0 developments7 Oct: 0 developments8 Oct: 11 developments9 Oct: 3 developments10 Oct: 6 developments11 Oct: 2 developments12 Oct: 7 developments13 Oct: 11 developments14 Oct: 13 developments15 Oct: 14 developments16 Oct: 8 developments17 Oct: 10 developments18 Oct: 6 developments19 Oct: 8 developments20 Oct: 8 developments
Stage: Coverage

Sources

  1. CodeHealth Predicts the Token Cost of Agentic Code Review: A Pre-Registered Study of 465 Agent-Authored Pull RequestsarXiv

Status history

  • 2026-10-16 Flagged as buildable