Repository purpose
Explains what the project does so the agent can make relevant choices.
Free · private · instant
AGENTS.md checker
Paste an AGENTS.md, CLAUDE.md, or Copilot instruction file. Get a practical audit of the context, commands, guardrails, and validation steps your coding agent is missing.
Step 1
Paste or load your file
Analyzed entirely in your browser. The file is never uploaded.
Step 2
Instruction health
52/100
Needs context
AGENTS.md52/100
The badge links back to this score summary. It contains no file contents and badge impressions are never counted as users.
Stack and runtime
Names the language, framework, runtime, or package manager.
Runnable commands
Provides copyable setup, build, test, lint, or development commands.
Architecture map
Points to important directories, boundaries, or established patterns.
Validation loop
States which checks must run before work is considered complete.
Change boundaries
Prevents broad rewrites and keeps work aligned with the request.
Safety guardrails
Protects secrets, user changes, migrations, and destructive operations.
Definition of done
Makes the final evidence and handoff explicit.
Focused length
Keeps the root file readable and avoids burying critical rules.
Copy a repair block
Add these missing sections, then replace the placeholders with repository-specific facts.
What gets checked
The facts an unfamiliar agent needs.
A useful root instruction file is not a style guide. It is a compact operating contract: what the repository is, how to navigate it, how to validate work, and which mistakes are expensive.
Executable context
Purpose, stack, architecture, and copyable commands reduce avoidable exploration and command failures.
Repository guardrails
Scope limits, secrets, migrations, and destructive-action rules protect the work already in progress.
Completion evidence
Tests, builds, and a concrete handoff make “done” observable instead of subjective.