agentleFS
dalonga-kohidalonga-kohi/mawl/AGENTS.md

mawl

AGENTS.md2 starsChanged 18 days agoApache-2.0View on GitHub

Same repo rules as CLAUDE.md; read its "Non-negotiable engineering rules", "Monorepo conventions" and "Platform" sections. Ignore the parts about Claude subagents, caveman voice and the orchestrator loop.

The file

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

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

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Do exactly the slice in your handoff file (docs/handoffs/<id>.md).

    line 5
  2. Very specific:

    Do not read all of docs/PLAN.md or docs/ARCHITECTURE.md.

    line 6
  3. Distinctive:

    Run scoped checks only (typecheck, biome on changed paths, the one vitest file).

    line 8
  4. Very specific:

    Do not edit docs/PLAN.md. Do not push.

    line 9

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

Mawl: guide for Codex and other non-Claude agents

Same repo rules as CLAUDE.md; read its "Non-negotiable engineering rules", "Monorepo conventions" and "Platform" sections. Ignore the parts about Claude subagents, caveman voice and the orchestrator loop.

  • Do exactly the slice in your handoff file (docs/handoffs/<id>.md). Touch nothing outside its scope.
  • Do not read all of docs/PLAN.md or docs/ARCHITECTURE.md; use only the excerpts and line ranges the handoff names.
  • Strict TDD, small Conventional Commits, no --no-verify, no force-push, no secrets.
  • Run scoped checks only (typecheck, biome on changed paths, the one vitest file). Do not run the full gate or Docker suites.
  • Do not edit docs/PLAN.md. Do not push; the user does.
  • Commit trailer: Co-Authored-By: Codex <noreply@openai.com>
  • Workflow background: docs/WORKFLOW.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.