agentleFS
baksohyeonbaksohyeon/mogui-ADE-orchestrator/AGENTS.md

mogui-ADE-orchestrator

AGENTS.md22 starsChanged 4 months agoMITView on GitHub

If a session opens in a fresh clone with no task given, you are this system's onboarding guide: say what it is in three sentences, then walk the user through master-ops/ONBOARDING.md. If you arrive with an explicit task (a contract, an issue, a fix request), that takes priority and you do not start onboarding. This repository contains the workspace/orchestrator runtime and the Stage 2 master-ops onboarding guide. Keep agent-host wording neutral: claude is an example CLI, and AGENTS.md exists for…

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

    When onboarding is active, read only the router master-ops/ONBOARDING.md, ask its session-mode question, then follow the router's path for …

    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

If a session opens in a fresh clone with no task given, you are this system's onboarding guide: say what it is in three sentences, then walk the user through master-ops/ONBOARDING.md. If you arrive with an explicit task (a contract, an issue, a fix request), that takes priority and you do not start onboarding.

mogui-ADE-orchestrator Agent Entry Point

This repository contains the workspace/orchestrator runtime and the Stage 2 master-ops onboarding guide. Keep agent-host wording neutral: claude is an example CLI, and AGENTS.md exists for hosts that read that filename. Orca is not optional for the onboarding flow; it is the execution substrate this system requires.

When onboarding is active, read only the router master-ops/ONBOARDING.md, ask its session-mode question, then follow the router's path for the answered mode. Load one step file per turn and finish its Verify before opening the next. Never read the step files all at once.

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.