agentleFS
Sign inStart free
Azd325Azd325/skills/AGENTS.md

skills

AGENTS.md1 starsChanged 40 days agoMITView on GitHub

This repository is the azd325/skills collection. Each folder in plugins/ (code: hooks, extensions) or skills/ (prompt-only SKILL.md) is one package that installs on its own. Keep this file for knowledge useful to almost every future agent session in this repository. Do not repeat what the code already shows; point to the authoritative file or command instead. Prefer rewriting or pruning existing entries over appending new ones.

  • Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.

    Of the AGENTS.md files we read, the 31,700 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository9 other files it gives its agents.

The file

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

6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Before you change a package, read its VISION.md.

    line 9
  2. Very specific:

    When a change fails that test, stop and tell the author.

    line 10
  3. Distinctive:

    Every rule has a test that goes red without it.

    line 18
  4. Distinctive:

    Keep this file for knowledge useful to almost every future agent session in this repository.

    line 25
  5. Distinctive:

    Do not repeat what the code already shows.

    line 26
  6. Distinctive:

    Prefer rewriting or pruning existing entries over appending new ones.

    line 27

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

This repository is the azd325/skills collection. Each folder in plugins/ (code: hooks, extensions) or skills/ (prompt-only SKILL.md) is one package that installs on its own.

Orientation

  • Each package's VISION.md is its acceptance policy and covers only that package.
  • Before you change a package, read its VISION.md. Run its closing accept/resist test against VISION.md alone.
  • When a change fails that test, stop and tell the author. Do not edit VISION.md to make the change pass.
  • A package may have its own AGENTS.md. Read it before you change the package.
  • README.md at the root lists the packages; each package README.md holds its layout and commands.

Rules for every package

  • Rules that apply to every package live in this file, not in a package vision.
  • A prompt skill never claims enforcement; enforcement is code with tests.
  • Every rule has a test that goes red without it. Remove the rule, see the test fail, then restore the rule.
  • A package installs without the author's dotfiles.
  • Each package keeps its own CHANGELOG.md. Add every user-facing change under ## [Unreleased] in the same commit.
  • A new package needs its own VISION.md, README.md, CHANGELOG.md and LICENSE, a row in the root README.md, and, for a plugin, an entry in .claude-plugin/marketplace.json. Its own AGENTS.md is optional.

Maintaining this file

Keep this file for knowledge useful to almost every future agent session in this repository. Do not repeat what the code already shows; point to the authoritative file or command instead. Prefer rewriting or pruning existing entries over appending new ones.

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.

Check your setup, free