codomyrmex / projects
AGENTS.md10 starsChanged 38 days agoMITView on GitHub
Preserve ownership and Git boundaries for integration and example workspaces. - Detect nested .git directories or gitfiles before editing. - Treat every nested repository as an independent worktree with its own status, history, remotes, and agent instructions. - Never fold nested changes into root formatting, cleanup, documentation generation, or release claims. - Run commands from the owning workspace only after reading its README, AGENTS, and package metadata. - Keep root documentation limited to workspace ownership and integration boundaries; detailed behavior…
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 31,700 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 repository47 other files it gives its agents.
- .agent/AGENTS.mdAGENTS.md
- .agents/AGENTS.mdAGENTS.md
- AGENTS.mdAGENTS.md
- .agents/skills/agent-interop/AGENTS.mdAGENTS.md
- .agents/skills/AGENTS.mdAGENTS.md
- .agents/skills/first-principles/AGENTS.mdAGENTS.md
- .agents/skills/mcp-tool-use/AGENTS.mdAGENTS.md
- .agents/skills/red-team/AGENTS.mdAGENTS.md
- .agents/skills/systems-thinking/AGENTS.mdAGENTS.md
- .codex/AGENTS.mdAGENTS.md
- config/AGENTS.mdAGENTS.md
- .cursor/skills/AGENTS.mdAGENTS.md
- .cursor/skills/codomyrmex/AGENTS.mdAGENTS.md
- .cursor/skills/desloppify/AGENTS.mdAGENTS.md
- .cursor/skills/fractals/AGENTS.mdAGENTS.md
- data/AGENTS.mdAGENTS.md
- .devcontainer/AGENTS.mdAGENTS.md
- docs/AGENTS.mdAGENTS.md
- evaluations/AGENTS.mdAGENTS.md
- examples/AGENTS.mdAGENTS.md
- .github/AGENTS.mdAGENTS.md
- .github/commands/AGENTS.mdAGENTS.md
- .github/ISSUE_TEMPLATE/AGENTS.mdAGENTS.md
- .github/scripts/AGENTS.mdAGENTS.md
- .github/workflows/AGENTS.mdAGENTS.md
- .jules/AGENTS.mdAGENTS.md
- .pipelines/AGENTS.mdAGENTS.md
- scripts/AGENTS.mdAGENTS.md
- src/AGENTS.mdAGENTS.md
- tests/AGENTS.mdAGENTS.md
- .workflows/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- agent-interopSkill
- first-principlesSkill
- mcp-tool-useSkill
- red-teamSkill
- systems-thinkingSkill
- agent-interopSkill
- first-principlesSkill
- mcp-tool-useSkill
- qmdSkill
- red-teamSkill
- systems-thinkingSkill
- CodomyrmexSkill
- desloppifySkill
- Fractals orchestratorSkill
- CodomyrmexSkill
The file
We split this AGENTS.md into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
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
- Distinctive: line 12
Treat every nested repository as an independent worktree with its own status, history, remotes, and agent instructions.
- Distinctive: line 14
Never fold nested changes into root formatting, cleanup, documentation generation, or release claims.
- Distinctive: line 16
Run commands from the owning workspace only after reading its README, AGENTS, and package metadata.
- Distinctive: line 18
Keep root documentation limited to workspace ownership and integration boundaries.
- Distinctive: line 20
Do not infer that a historically documented workspace still exists.
≈ “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.
Files
<!-- agents: curated -->Agent guidance for project workspaces
Purpose
Preserve ownership and Git boundaries for integration and example workspaces.
Development Guidelines
- Detect nested
.gitdirectories or gitfiles before editing. - Treat every nested repository as an independent worktree with its own status, history, remotes, and agent instructions.
- Never fold nested changes into root formatting, cleanup, documentation generation, or release claims.
- Run commands from the owning workspace only after reading its README, AGENTS, and package metadata.
- Keep root documentation limited to workspace ownership and integration boundaries; detailed behavior belongs with the workspace.
- Do not infer that a historically documented workspace still exists.
Key Files
- README.md — current workspace inventory and safety boundary
- SPEC.md — workspace specification
test_project/— current standalone nested worktree
Current scope
The current checkout contains projects/test_project/ as a nested Git
worktree. Recheck this fact live before acting.
Navigation
- Human overview
- Workspace specification
- Repository agent contract
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
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.

