agentleFS
Sign inStart free
fsgrecofsgreco/ai-agent-plugins/AGENTS.md

ai-agent-plugins

AGENTS.md0 starsChanged 5 months agoMITView on GitHub

This is a Claude Code plugin marketplace. Each top-level directory (except .claude-plugin/) is a plugin.

  • 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,774 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 repositoryOne other file it gives its agents.

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:

    When adding a new plugin, update .claude-plugin/marketplace.json with a new entry.

    line 22

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

AI Agent Plugins

Project structure

This is a Claude Code plugin marketplace. Each top-level directory (except .claude-plugin/) is a plugin.

.claude-plugin/marketplace.json   ← marketplace catalog
<plugin-name>/
├── .claude-plugin/plugin.json    ← plugin manifest (name, version, description)
└── skills/<skill-name>/
    ├── SKILL.md                  ← skill instructions (markdown + frontmatter)
    └── scripts/                  ← shell scripts used by the skill

Guidelines

  • Skills are natural language instructions in markdown — keep them lean and imperative.
  • Shell scripts go in scripts/ and are invoked via ! backtick syntax at skill load time. The ! backtick does not support command substitution ($(...)) — use wrapper scripts for that.
  • allowed-tools in SKILL.md frontmatter pre-authorizes tool patterns so the skill doesn't prompt for permission.
  • $ARGUMENTS captures user input after the slash command. Route behavior based on its value.
  • When adding a new plugin, update .claude-plugin/marketplace.json with a new entry.
  • Bump version in the plugin's plugin.json when making changes.

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