agentleFS
KaidevLabsKaidevLabs/Skills/guidelines/agents.md

Skills / guidelines

AGENTS.md1 starsChanged 34 days agoMITView on GitHub

Sub-agents may explore, gather information, and perform bounded tasks when delegation is available. They must not break a required human-review sequence or independently stage, commit, or close work assigned to an orchestrator. The orchestrator owns the integrated result: review delegated output, resolve conflicts, make or stage the final changes when authorized, record the as-built result, and update the relevant plan or tracker. Give each delegated task a narrow scope, necessary context, expected output, and explicit constraints. Treat returned findings as…

  • 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 32,671 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 repository7 other files it gives its agents.

The file

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

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the environment has no sub-agent mechanism, perform the work directly while preserving the same review boundaries.

    line 7

≈ “Common” is an estimate: at least 1 in 5 of the 41,581 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 delegation

Sub-agents may explore, gather information, and perform bounded tasks when delegation is available. They must not break a required human-review sequence or independently stage, commit, or close work assigned to an orchestrator.

The orchestrator owns the integrated result: review delegated output, resolve conflicts, make or stage the final changes when authorized, record the as-built result, and update the relevant plan or tracker. Give each delegated task a narrow scope, necessary context, expected output, and explicit constraints. Treat returned findings as input that still needs verification.

If the environment has no sub-agent mechanism, perform the work directly while preserving the same review boundaries. Do not claim delegation occurred when it did not.

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.