Scans a repository and scores its agentic-coding readiness — whether the repo has what an AI coding agent needs to work well unaided — across six categories:
- Documentation,
- Architecture,
- Testing,
- Automation Guard Rails,
- AI Context, and
- Maintainability.
See docs/METRICS.md for the full metric reference — every metric's description, fix instruction, and remediation explanation in one table.
Use agenticgrade on any codebase without installing it as a dependency. Run this from the root of your project:
npx agenticgrade scan . --detailed --htmlThe scan also detects which agentic-tooling provider convention a repo uses
(openspec, claude, a generic AGENTS.md-based universal setup, or none) and applies provider-specific bonus metrics on top of the base catalog.
npx agenticgrade scan [path] # human-readable report, defaults to the current directory
npx agenticgrade scan [path] --json # structured JSON output
npx agenticgrade scan [path] --summary # condensed report: overall, top improvements, providers, category totals — no per-metric detail
npx agenticgrade scan [path] --detailed # expanded report: each failing metric is followed by a remediation explanation
npx agenticgrade scan [path] --html # renders a self-contained HTML report and opens it in your browserA simple scan
Screen.Recording.2026-07-09.at.17.38.43.mov
Detailed HTML report
Screen.Recording.2026-07-09.at.17.42.03-1.mov
The human-readable report prints, top to bottom: detected providers, the category/metric breakdown, a divider, then the overall score/grade and Top Improvements — the summary comes last so it's still on screen after a long breakdown, without scrolling.
--summary can be combined with --json or --html to trim per-metric detail the same way: each category omits its individual metric rows/metrics array.
--detailed can be combined with --json or --html to include each failing metric's remediation text (a remediation field in JSON; an indented explanation in the text/HTML report). Without --detailed, JSON metric results have no remediation field. --detailed has no effect when --summary is also set, since --summary already omits per-metric output entirely.
npx agenticgrade scan [path] --html # writes a temp HTML file and opens it in your default browser
npx agenticgrade scan [path] --html --output report.html # writes the HTML report to the given path instead
npx agenticgrade scan [path] --json --output report.json # writes the JSON report to the given path instead of stdout--html renders the scan as a self-contained HTML document (inline styles, no external assets) — handy for sharing or printing as a PDF via your browser's print dialog. Its section order is Overall → Top Improvements → providers → categories (unlike the terminal report, an HTML/PDF document has no scrollback problem, so the summary stays at the top).
--output <path> redirects --html or --json output to a file (creating any missing parent directories) instead of opening a browser or printing to stdout, and prints a confirmation naming the file. If both --html and --json are passed, --html takes precedence and --output writes the HTML. --output has no effect unless --html or --json is also passed.
npm install
npm run buildDuring development, run directly against source without building:
npm run dev -- scan [path]Run from the build:
npm run build
node dist/cli.js scan [path] # e.g. node dist/cli.js scan . to score this repo
node dist/cli.js scan [path] --jsonnpm test