agentleFS
MangroveTechnologiesMangroveTechnologies/mangrove-agent/AGENTS.md

mangrove-agent

AGENTS.md8 starsChanged 14 days agoMITView on GitHub

Before responding, read SAGE.md in this repository and follow its startup contract, including the three mandatory rule documents. Resolve their paths from the repository root. SAGE.md is the single shared source for the agent persona, project context, and operating instructions; do not maintain a separate copy here. Grok Build and other clients that discover AGENTS.md use this same entry point. If another native entry point already loaded these sources, do not load them twice. For clients without local file access,…

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

    Before responding, read SAGE.md in this repository and follow its startup contract, including the three mandatory rule documents.

    line 3

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

Mangrove Agent - Codex and compatible clients

Before responding, read SAGE.md in this repository and follow its startup contract, including the three mandatory rule documents. Resolve their paths from the repository root. SAGE.md is the single shared source for the agent persona, project context, and operating instructions; do not maintain a separate copy here. Grok Build and other clients that discover AGENTS.md use this same entry point. If another native entry point already loaded these sources, do not load them twice.

For clients without local file access, use the complete generated bundle at docs/clients/sage-instructions.md, as described in docs/clients.md. A pointer alone does not load its target, and instructions alone do not connect MCP tools.

Grok Bot, which runs this repository on its own box, follows docs/clients/grok-bot.md.

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.