agentleFS
eai-orgeai-org/agent-toolkit/AGENTS.md

agent-toolkit

AGENTS.md85 starsChanged 21 days agoMITView on GitHub

A collection of reusable skills and rules for AI agents (Claude Code and similar). Everything must be self-contained and generic — reusable in any project — so avoid project-specific logic or assumptions. Rules are opt-in: a skill must work correctly with no rules installed, so never fix or extend a skill by adding a rule it depends on. Test harnesses, for a skill or an install script, live in test/<name>/ — repo-internal, never installed; their runs/ output dirs are gitignored.…

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:

    Test harnesses, for a skill or an install script, live in test/<name>/ — repo-internal, never installed.

    line 8

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

A collection of reusable skills and rules for AI agents (Claude Code and similar). Everything must be self-contained and generic — reusable in any project — so avoid project-specific logic or assumptions. Rules are opt-in: a skill must work correctly with no rules installed, so never fix or extend a skill by adding a rule it depends on.

Test harnesses, for a skill or an install script, live in test/<name>/ — repo-internal, never installed; their runs/ output dirs are gitignored. Planning documents go in .agents/plans/ (gitignored).

Docs

  • docs/authoring-conventions.md — read before editing any skill, rule, doc, manifest or install script.
  • docs/core-philosophy.md — the five pillars and their litmus test; read before creating or redesigning a skill, or when brainstorming toolkit direction.
  • docs/contributor-setup.md — how this repo is wired for agents; read when hooking a new agent up to it.

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.