agentreadme

Report · marked 25 Aug 2026

bmad-code-org/BMAD-METHOD

Ready for an agent to work in without hand-holding.

JavaScript · 52,269 stars · 603 files · branch main

86 /100 A
Instructions 24/27Whether the repo tells an agent how to behave before it starts guessing. Losing marks on instruction quality and readme as an entry point.Setup 14/14Whether an agent can install the project and get it running without a human. Full marks.Verification loop 22/25Whether an agent can check its own work. This is the category that most decides whether agent output is trustworthy. Losing marks on static type checking.Context economy 17/20Whether the repo fits in a context window, or fights it. Losing marks on file sizes fit in context and repository weight.Navigability 6/10How quickly anything new can orient itself. Losing marks on repository description and license.

Higher is better. Accent marks what is costing you most.

Fix these first

01
Static type checking
A type checker gives an agent an error message instead of a runtime surprise. It's the second-fastest feedback loop after the compiler.
02
License
Without a license nobody can safely reuse this, and some tools will refuse to work with it at all.
03
File sizes fit in context
A single file that fills the context window forces an agent to work from fragments, and it will confidently edit code it never saw. Splitting the worst offenders pays for itself immediately.

The full marking

Every deduction below names the file or setting it came from.

Instructions 24/27 A

Whether the repo tells an agent how to behave before it starts guessing.

✓Agent instruction file 12/12
AGENTS.md is present, which is the format the most tools read.
✗Instruction quality 10/12
Specific enough that an agent can act on it.
Worth fixing: has no code blocks.
464 characters, a workable length
names the actual commands to run
uses headings, so an agent can skim it
✗README as an entry point 2/3
README exists but never explains how to get the thing running.
Give the README an Install and a Usage heading with real commands under each. Agents pattern-match on those headings.
Setup 14/14 A+

Whether an agent can install the project and get it running without a human.

✓Deterministic install 6/6
package-lock.json pins the dependency tree.
Found package-lock.json
✓Discoverable commands 6/6
Commands are declared where an agent will look for them.
package.json scripts (bmad:install, bmad:uninstall, docs:build, docs:dev, docs:fix-links, docs:preview…)
–Environment config n/a
Not applicable — this reads as a library, with no environment to configure.
✓Pinned runtime version 2/2
The language runtime version is pinned.
Found .nvmrc
–Reproducible environment n/a
Not applicable — a library doesn't need a container to be worked on.
Verification loop 22/25 A

Whether an agent can check its own work. This is the category that most decides whether agent output is trustworthy.

✓Tests exist 8/8
42 test files against 106 source files.
e.g. src/bmm-skills/plan/bmad-architecture/scripts/tests/test_lint_spine.py, src/bmm-skills/plan/bmad-sprint-planning/scripts/tests/test_sprint_plan.py, src/bmm-skills/plan/bmad-ux/references/design-md-spec.md
✓Test command is discoverable 7/7
An agent can find and run `npm run test`.
✓Continuous integration 4/4
5 GitHub Actions workflows define what "passing" means.
✓Lint and format rules 3/3
eslint.config.mjs encodes the house style.
✗Static type checking 0/3
No static type checking.
A type checker gives an agent an error message instead of a runtime surprise. It's the second-fastest feedback loop after the compiler.
Context economy 17/20 A

Whether the repo fits in a context window, or fights it.

✓No committed build output 6/6
No generated directories committed.
✓.gitignore hygiene 3/3
.gitignore covers 61 patterns.
✗File sizes fit in context 4/6
1 source file is over 100KB.
A single file that fills the context window forces an agent to work from fragments, and it will confidently edit code it never saw. Splitting the worst offenders pays for itself immediately.
test/test-installation-components.js — 195KB
✗Repository weight 4/5
About 52.1MB checked out, which is comfortable.

Here is your AGENTS.md

Drafted from what is actually in this repository: the install command from your lockfile, the commands you already declare, your real directory layout. Anything marked TODO needs a person. Save it at the root as AGENTS.md.

AGENTS.md — drafted for bmad-code-org/BMAD-METHOD 
undefined

Open the raw markdown  or  curl -o AGENTS.md agentreadme.com/draft/bmad-code-org/BMAD-METHOD.md

Show the mark

The badge re-checks daily, so it keeps up as the repository changes. Use mark again to force it now.

agent ready 86 out of 100

[![agent ready](https://agentreadme.com/badge/bmad-code-org/BMAD-METHOD.svg)](https://agentreadme.com/bmad-code-org/BMAD-METHOD)

Other JavaScript repositories, marked

react/react 71 B+ affaan-m/ECC 90 A trekhleb/javascript-algorithms 69 B Snailclimb/JavaGuide 53 C+ airbnb/javascript 54 C+ vercel/next.js 77 B+

All JavaScript repositories

Think this mark is wrong?

Every deduction above names the file it came from, so this can be settled by looking. If a check missed something, that is a rule worth fixing.

Open an issue, already filled in