Can an AI agent actually work in your repo?

When Claude Code or Cursor flails in a codebase, everyone blames the model. Usually it is the repository.

Try it on the repo you have open right now. Nothing installed, no code executed.

Median agent-readiness by language

865 most-starred software repos on GitHub

TypeScript 72

Go 70

Rust 63

Python 60

JavaScript 60

Shell 49

Java 44

C++ 42

Jupyter Notebook 41

C 38

Higher is better. Curated lists and tutorials excluded.

What we found across 865 repositories

median mark out of a hundred

38%

have no test command an agent can find

32%

ship an AGENTS.md

See the whole class list

Five things decide whether an agent succeeds

Instructions

An AGENTS.md that names the real commands

Setup

A lockfile, declared commands, a documented environment

Verification loop

Tests an agent can find and run to check itself

Context economy

No 400KB files, no committed build output

Navigability

Documentation, a description, a licence

bash — ~/code

$ curl agentreadme.com/honojs/hono.txt

# honojs/hono — 72/100 · B+

✗ Instructions              3/27   F
  None found. Every agent that opens
  this repo starts from zero.
✓ Setup                    14/14   A+
✓ Verification loop        24/25   A+
✓ Context economy          18/20   A
✓ Navigability             10/10   A+

# fix first
+ Add an AGENTS.md at the root: what the
  project is, how to install, how to run,
  how to test, and the conventions a
  newcomer always gets wrong.
+ Instructions earn their keep by naming
  exact commands.

# full report: agentreadme.com/honojs/hono

$

Recently marked

freeCodeCamp/freeCodeCamp 69 B openclaw/openclaw 68 B nilbuild/developer-roadmap 45 C vinta/awesome-python 81 A- obra/superpowers 68 B 996icu/996.ICU 24 F react/react 71 B+ torvalds/linux 31 D

Try it on the repo you have open right now.

Two API calls. Nothing cloned, nothing executed, no account. The marking scheme is published in full and every deduction cites its file.