codomyrmex / src
AGENTS.md10 starsChanged 38 days agoMITView on GitHub
src/codomyrmex/ is the installable package. Source changes must preserve module boundaries, public exports, MCP discovery, typing, tests, and source-adjacent documentation. - Read the nearest module AGENTS.md before editing. - Run GitNexus impact analysis before changing any function, class, or method. - Keep public API changes aligned with __init__.py, API_SPECIFICATION.md, MCP_TOOL_SPECIFICATION.md, PAI, security, tests, and changelog surfaces. - Use centralized logging and typed exceptions for shared runtime behavior. - Preserve MCP metadata and tool registration when refactoring handlers. - Use real…
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
- projects/AGENTS.mdAGENTS.md
- scripts/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
8 rules. About 0 are common, 7 are distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Read the nearest module AGENTS.md before editing.
- Distinctive: line 14
Run GitNexus impact analysis before changing any function, class, or method.
- Very specific: line 15
Keep public API changes aligned with __init__.py, API_SPECIFICATION.md, MCP_TOOL_SPECIFICATION.md, PAI, security, tests, and changelog …
- Distinctive: line 17
Use centralized logging and typed exceptions for shared runtime behavior.
- Distinctive: line 19
Use real components and temporary resources in tests.
- Distinctive: line 21
Do not treat optional dependency discovery as permission to import expensive or conflicting native backends.
- Distinctive: line 23
Do not run broad source-documentation generators during the active hand-pass freeze.
- Distinctive: line 25
Keep submodule worktrees outside package-wide formatting or rewriting.
≈ “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 the source tree
Purpose
src/codomyrmex/ is the installable package. Source changes must preserve
module boundaries, public exports, MCP discovery, typing, tests, and
source-adjacent documentation.
Development Guidelines
- Read the nearest module
AGENTS.mdbefore editing. - Run GitNexus impact analysis before changing any function, class, or method.
- Keep public API changes aligned with
__init__.py,API_SPECIFICATION.md,MCP_TOOL_SPECIFICATION.md, PAI, security, tests, and changelog surfaces. - Use centralized logging and typed exceptions for shared runtime behavior.
- Preserve MCP metadata and tool registration when refactoring handlers.
- Use real components and temporary resources in tests; follow the root zero-mock policy.
- Do not treat optional dependency discovery as permission to import expensive or conflicting native backends.
- Do not run broad source-documentation generators during the active hand-pass freeze.
- Keep submodule worktrees outside package-wide formatting or rewriting.
Key Files
- README.md — source-tree overview
- SPEC.md — source-surface specification
codomyrmex/__init__.py— package exports and metadatacodomyrmex/AGENTS.md— package-level agent guidance
Validation
Select checks proportionate to the change, then run the package gate before handoff:
uv run --locked ruff check src tests
uv run --locked ruff format --check src tests
uv run --locked ty check --output-format concise src tests
uv run --locked pytest -q <relevant-test-path>
make testmake test enforces the configured 60% coverage floor. Plain pytest is the
faster diagnostic path and does not prove coverage compliance.
Navigation
- Source overview
- Package overview
- Package agent guidance
- Repository architecture
- 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.

