AAgentFile Check

REPOSITORY INSTRUCTIONS · STATIC REVIEW

Your AGENTS.md should be operational, not inspirational.

Paste repository instructions and get an explainable quality report: commands, scope, testing, safety, contradictions, context cost, and concrete language.

No uploadActionabilityConflict checksToken estimate

INSTRUCTION AUDIT

AGENTS.md linter

AGENTS.md0 words · ~0 tokens

Checks structure, commands, testing, boundaries, ambiguity, conflicts, secret patterns, and instruction density.

01

Can an agent act?

Finds concrete install, build, lint, test, and verification commands instead of generic advice.

02

Where does it apply?

Looks for repository scope, nested-file precedence, generated files, and protected paths.

03

Can rules conflict?

Flags unconditional absolutes and opposing directions that make compliance impossible.

04

Is it safe to share?

Detects credential-like strings and risky destructive or bypass commands inside examples.

QUALITY MODEL

Good context reduces agent guesswork.

AGENTS.md is intentionally plain Markdown. That means quality cannot be reduced to schema validation. The useful question is whether an unfamiliar coding agent can identify the workspace, make a scoped change, run the right checks, and know when it is done.

High-value content

  • Exact setup and verification commands
  • Repository layout and ownership boundaries
  • Generated-file and migration rules
  • Test expectations proportional to changes
  • PR and handoff requirements

Common smells

  • “Follow best practices” without examples
  • Huge pasted architecture documentation
  • Contradictory always/never rules
  • Commands that bypass safety checks
  • Tool-specific rules presented as universal

PURPOSE & METHODOLOGY

A focused tool, with the context to use it well

Agents Lint was created to lint, generate, and improve AGENTS.md instructions for coding agents. It is intended for software teams maintaining repository guidance for AI coding agents. The tool is free, requires no account, and is paired with original explanations so you can understand the result rather than copy an unexplained output.

How to use the result

Start with a sample or a non-sensitive copy of your data, run the check, and review every finding before changing a production project. Lint rules focus on clarity, testability, scope, and conflicting instructions. Supporting guides compare common instruction-file formats and explain the reasoning behind recommendations. Specifications and software evolve, so confirm high-impact decisions against the linked primary documentation.

Privacy and limitations

AGENTS.md or related instruction text is processed in your browser wherever the tool page states that local processing is used. Avoid entering passwords, access tokens, personal data, or confidential material. Automated output may be incomplete because it cannot know your entire deployment, threat model, or organizational policy.

Independent and transparent

This is an independent developer resource, not an official certification service. Source code and issue tracking are available on GitHub. Read more about the project, review the privacy policy, or report an error.