Skip to main content
New aislop v0.9.4: four new Python rules from the SlopCodeBench paper, plus a CLI star prompt and GitHub Discussions. Read more →

What is AI slop costing you?

Drag the inputs to your team's reality and see a directional estimate of the engineer-hours spent untangling AI-generated code. Every number below is computed from your inputs in the browser. Nothing is sent anywhere.

Engineers shipping code into the same repos.

Rough share of merged lines that an agent drafted.

Across the whole team, not per developer.

Time spent rewriting, untangling, or re-reviewing agent output.

An estimate based on your inputs
0 hrs / week

Engineer-hours your team spends cleaning up AI slop each week.

0 hrs

per month

0 hrs

per year

This is a directional estimate, not a measured fact. It scales the inputs you provided and uses no external benchmark figures.

No hidden math.

The estimate is a plain multiplication of your inputs. The AI share scales how many PRs carry agent-written code, the per-PR minutes scale the cleanup tax, and the rest is unit conversion.

  1. 01 weekly cleanup hours = PRs per week × (AI share ÷ 100) × cleanup minutes per PR ÷ 60
  2. 02 monthly hours = weekly hours × 4.33 (average weeks per month)
  3. 03 annual hours = weekly hours × 52

Stop estimating. Measure it.

aislop scores your repo against the same deterministic rules on every keystroke and every PR. Run it free and replace this estimate with a real number.

npx aislop scan
Scan your repo free →