agentleFS
b1tankb1tank/skills/AGENTS.md

skills

AGENTS.md1 starsChanged 8 months agoMITView on GitHub

This repository is the source of truth for the owner's cross-agent customizations. When asked to set up, repair, synchronize, or explain agent customizations: Do not edit generated files under .generated/; regenerate them with ./setup.sh generate.

The file

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

4 rules. About 1 is common, 1 is distinctive, and 2 are very specific to this project.

  • ≈1

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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
  • could be automatic: a setting could enforce it
  1. Distinctive:

    When asked to set up, repair, synchronize, or explain agent customizations:

    line 5
  2. Very specific:

    Run ./setup.sh bootstrap only when the user asks to apply the setup.

    line 9
  3. Common:

    Never commit credentials. MCP credentials belong in environment variables or each client's OAuth store.

    line 11
  4. Very specific:

    Do not edit generated files under .generated/.

    line 13

≈ “Common” is an estimate: at least 1 in 5 of the 42,283 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

Skills bootstrap

This repository is the source of truth for the owner's cross-agent customizations.

When asked to set up, repair, synchronize, or explain agent customizations:

  1. Read BOOTSTRAP.md.
  2. Preview with ./setup.sh status and ./setup.sh bootstrap --dry-run.
  3. Run ./setup.sh bootstrap only when the user asks to apply the setup.
  4. Run ./setup.sh validate afterward.
  5. Never commit credentials. MCP credentials belong in environment variables or each client's OAuth store.

Do not edit generated files under .generated/; regenerate them with ./setup.sh generate.

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.