agentleFS
marcopesanimarcopesani/swarm-skill/AGENTS.md

swarm-skill

AGENTS.md0 starsChanged 5 days agoMITView on GitHub

This repo ships one Agent Skill, skills/swarm/, to every host: Claude Code, Codex/ChatGPT, pi, npx skills, and claude.ai. Read CONTRIBUTING.md. The rules that matter most: - skills/swarm/ is the only copy of the skill. Never copy it into .claude/skills, .agents/skills or plugins/ here. - Never edit the generated manifests (plugin.json, .claude-plugin/*, .codex-plugin/*, .agents/plugins/*) by hand. Edit tools/manifests.mjs or package.json, then run npm run sync. - SKILL.md frontmatter holds the six Agent Skills fields plus disable-model-invocation. Quote every metadata value. Don't…

  • 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,439 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 repository2 other files it gives its agents.

The file

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

3 rules. About 0 are common, 0 are distinctive, and 3 are 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.

  • 3

    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. Very specific:

    Never edit the generated manifests (plugin.json, .claude-plugin/*, .codex-plugin/*, .agents/plugins/*) by hand.

    line 8
  2. Very specific:

    Add a line under ## [Unreleased] in CHANGELOG.md for every user-visible change.

    line 14
  3. Very specific:

    Before you commit, npm run check must pass (and claude plugin validate .

    line 15

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

Working on this repository

This repo ships one Agent Skill, skills/swarm/, to every host: Claude Code, Codex/ChatGPT, pi, npx skills, and claude.ai. Read CONTRIBUTING.md. The rules that matter most:

  • skills/swarm/ is the only copy of the skill. Never copy it into .claude/skills, .agents/skills or plugins/ here.
  • Never edit the generated manifests (plugin.json, .claude-plugin/*, .codex-plugin/*, .agents/plugins/*) by hand. Edit tools/manifests.mjs or package.json, then run npm run sync.
  • SKILL.md frontmatter holds the six Agent Skills fields plus disable-model-invocation. Quote every metadata value. Don't set versions by hand: the release workflow does it.
  • skills/swarm/scripts/swarm.mjs guards money, credentials and safety. Every change needs a test in tests/. Keep it dependency-free.
  • Add a line under ## [Unreleased] in CHANGELOG.md for every user-visible change.
  • Before you commit, npm run check must pass (and claude plugin validate . when Claude Code is installed).

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.