agentleFS
cubxxwcubxxw/agent-kit/AGENTS.md

agent-kit

AGENTS.md2 starsChanged 3 months agoMITView on GitHub

This is a public repository. Treat every tracked byte as internet-visible. - Never copy credentials, authentication state, transcripts, memories, private notes, or machine-local overrides into this repository. - Use environment-variable names in examples; never include real values. - Keep catalog.json as the source of truth for accepted skills and upstream pins. - Treat docs/top-skills.md as a discovery radar, not an installation list. Add only a named skill that passes the full curation gate. - Preserve third-party license files and attribution.…

The file

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

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

  • ≈1

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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. Common:

    Never copy credentials, authentication state, transcripts, memories, private notes, or machine-local overrides into this repository.

    line 5
  2. Distinctive:

    Use environment-variable names in examples.

    line 7
  3. Very specific:

    Keep catalog.json as the source of truth for accepted skills and upstream pins.

    line 8
  4. Very specific:

    Treat docs/top-skills.md as a discovery radar, not an installation list.

    line 10
  5. Distinctive:

    Add only a named skill that passes the full curation gate.

    line 11
  6. Distinctive:

    Do not overwrite an existing user skill directory.

    line 13

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

Agent Kit repository instructions

This is a public repository. Treat every tracked byte as internet-visible.

  • Never copy credentials, authentication state, transcripts, memories, private notes, or machine-local overrides into this repository.
  • Use environment-variable names in examples; never include real values.
  • Keep catalog.json as the source of truth for accepted skills and upstream pins.
  • Treat docs/top-skills.md as a discovery radar, not an installation list. Add only a named skill that passes the full curation gate.
  • Preserve third-party license files and attribution.
  • Do not overwrite an existing user skill directory. The installer must fail safely on conflicts.
  • Run python3 -m unittest discover -s tests -v and ./bin/agent-kit doctor --strict after changes.
  • Review executable vendor changes manually before accepting an upstream update.

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.