NodeMemoryGraph
AGENTS.md0 starsChanged 7 days agoMITView on GitHub
This entry owns the stable discovery protocol. Keep module inventories, commands, implementation status, and environment-specific setup at their current owners. 1. Search for the task's terms, symbols, or error text in a narrow relevant scope. Use the current directory tree and manifests to locate code; expand the search only when that scope does not answer the question. 2. Read applicable instructions along the target path and the nearest relevant README. Find repository Skills by their names and descriptions; follow the…
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,774 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.
- docs/AGENTS.mdAGENTS.md
- complexity-reductionSkill
- doc-maintenanceSkill
- nmg-memorySkill
- repo-developmentSkill
- script-reuseSkill
- verification-traceabilitySkill
- working-state-maintenanceSkill
The file
We split this AGENTS.md into the rules it gives an agent
7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
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 8
Search for the task's terms, symbols, or error text in a narrow relevant scope.
- Distinctive: line 9
Use the current directory tree and manifests to locate code.
- Distinctive: line 11
Read applicable instructions along the target path and the nearest relevant README.
- Distinctive: line 15
Read the relevant contract section and the exact code or test involved.
- Distinctive: line 19
Stop expanding when the next action, its constraints, and its verification are clear.
- Distinctive: line 24
Use current code and owning documents to establish facts.
- Distinctive: line 28
Do not place necessary files in cache folders, including TEMP and tmp.
≈ “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
NMG Agent bootstrap
This entry owns the stable discovery protocol. Keep module inventories, commands, implementation status, and environment-specific setup at their current owners.
Find the context for the next action
- Search for the task's terms, symbols, or error text in a narrow relevant scope. Use the current directory tree and manifests to locate code; expand the search only when that scope does not answer the question.
- Read applicable instructions along the target path and the nearest relevant README. Find repository Skills by their names and descriptions; follow the development workflow before editing and the specialized workflow when its stated condition applies.
- Read the relevant contract section and the exact code or test involved. Keep its definitions, conditions, and exceptions together. Follow a reference when it supplies a missing definition, an affected dependency, or an applicable obligation; a background link alone is not a requirement to read another file.
- Stop expanding when the next action, its constraints, and its verification are clear. Reopen discovery when evidence conflicts or the task crosses a boundary.
Maintain shared knowledge
Use current code and owning documents to establish facts; experiments and past decisions supply evidence and rationale. Update the existing owner with a behavior change rather than adding another summary. Preserve unrelated working-tree edits.
Do not place necessary files in cache folders, including TEMP and tmp. Please follow Git best practices when using Git.
It is essential to write code that is readable, maintainable, and extensible. You
can employ appropriate design patterns to achieve this, but avoid using patterns
simply for the sake of using them. If a problem can be solved with a simple
if-else statement, there is no need to implement a combination of Strategy,
Factory, and Chain of Responsibility patterns. Cramming too many patterns into a
single class often results in over-engineering.
Required knowledge must be recoverable from the shared repository or an explicit shared task reference. Local memory, indexes, and prior Agent sessions are optional accelerators, never the only source needed to continue work.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

