agentleFS
AN0099AN0099/toothpaste-kit/AGENTS.md

toothpaste-kit

AGENTS.md1 starsChanged 19 days agoApache-2.0View on GitHub

Instructions for a coding agent working in this repository. They point at the files that hold the rules; nothing here adds one. - Rules for every change: CONTRIBUTING.md, which a change made by an agent follows like any other. - Terms of art: docs/glossary.md, each term with the file that defines it. - Checks: ./scripts/gates.sh --selftest, the same command CI runs, also run by tests/run. Its header states what each gate covers. Checks that need an installed tool, REUSE among…

The file

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

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Skills: read skills/skill-creation/SKILL.md before changing one.

    line 11

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

Agents

Instructions for a coding agent working in this repository. They point at the files that hold the rules; nothing here adds one.

  • Rules for every change: CONTRIBUTING.md, which a change made by an agent follows like any other.
  • Terms of art: docs/glossary.md, each term with the file that defines it.
  • Checks: ./scripts/gates.sh --selftest, the same command CI runs, also run by tests/run. Its header states what each gate covers. Checks that need an installed tool, REUSE among them, are ./scripts/compliance.sh --selftest.
  • Skills: read skills/skill-creation/SKILL.md before changing one.
  • Branch names: CONTRIBUTING.md, "Branch and tag names", checked by scripts/check-branch-name.
  • Commits: CONTRIBUTING.md, "Commits and pull requests": provenance as Assisted-by: and Agent-Effort: trailers with values read from the tool, never a co-author line, session link or footer. The Signed-off-by: line is the human's; an agent never adds one for them.
  • Pull requests: .github/pull_request_template.md lists what a reviewer expects.
<!-- SPDX-FileCopyrightText: 2026 Aidan Naveja SPDX-License-Identifier: Apache-2.0 -->

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.