We split this AGENTS.md into the rules it gives an agent

8 rules. About 0 are common, 5 are distinctive, and 3 are very specific to this project.

• ≈0

  Common · estimate

  Many files like this have a rule of this kind.

• ≈5

  Distinctive · estimate

  This author's own choices. Worth a look.

• 3

  Very specific

  Tied to their project's names, files or tools. Probably skip.

• Common
• Distinctive
• Very specific

1. Very specific:

   Keep canonical portable skills in skills/<name>/SKILL.md.

   line 6
2. Distinctive:

   Keep provider-specific behavior thin.

   line 7
3. Distinctive:

   Treat token/context efficiency as a feature.

   line 8
4. Distinctive:

   Never claim architectural, planning, structural, fire, accessibility, legal, or construction compliance without authoritative evidence and …

   line 10
5. Distinctive:

   Verify provider formats against current official documentation before changing manifests, install locations, or agent schemas.

   line 11
6. Very specific:

   Keep Claude plugin skill copies synchronized with canonical skills/.

   line 12
7. Distinctive:

   Prefer additive, backward-compatible changes.

   line 13
8. Very specific:

   Run python3 tests/check_repo.py and python3 -m unittest discover -s tests -v before committing repository changes.

   line 14

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.