agentleFS
fiveonecodefiveonecode/agent-skills/AGENTS.md

agent-skills

AGENTS.md20 starsChanged 2 months agoMITView on GitHub

This repository is a direct package of 51Code-owned skills. Each top-level skill directory contains a SKILL.md; the front matter is the source of truth for its name and description. - Edit skill source here, never in installed consumer copies. - Keep bootstrap.sh pinned to skills@1.5.14 and explicit skill names. Use #ref for reviewed tags; when upstream has no stable tag and the manager cannot resolve a raw commit, fetch and verify that exact commit before passing its local checkout to…

The file

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

5 rules. About 1 is common, 1 is distinctive, and 3 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.

  • 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:

    Keep bootstrap.sh pinned to skills@1.5.14 and explicit skill names.

    line 8
  2. Distinctive:

    Do not add a registry, generated catalog, lock generator, sync planner, or backward-compatibility layer.

    line 12
  3. Very specific:

    Keep WORKFLOW.md and scripts/verify.sh as the small, non-mutating Autopilot and Symphony integration boundary.

    line 14
  4. Very specific:

    When a skill is added or removed, update the owned list in bootstrap.sh and README.md in the same change.

    line 16
  5. Common:

    Keep public changes generic.

    line 18

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

This repository is a direct package of 51Code-owned skills. Each top-level skill directory contains a SKILL.md; the front matter is the source of truth for its name and description.

  • Edit skill source here, never in installed consumer copies.
  • Keep bootstrap.sh pinned to skills@1.5.14 and explicit skill names. Use #ref for reviewed tags; when upstream has no stable tag and the manager cannot resolve a raw commit, fetch and verify that exact commit before passing its local checkout to the manager.
  • Do not add a registry, generated catalog, lock generator, sync planner, or backward-compatibility layer.
  • Keep WORKFLOW.md and scripts/verify.sh as the small, non-mutating Autopilot and Symphony integration boundary.
  • When a skill is added or removed, update the owned list in bootstrap.sh and README.md in the same change.
  • Keep public changes generic. Do not commit credentials, machine paths, internal task links, private context, or company-only notes.

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.