agentleFS
Sign inStart free
docxologydocxology/codomyrmex/examples/AGENTS.md

codomyrmex / examples

AGENTS.md10 starsChanged 38 days agoMITView on GitHub

Version: v1.3.0 | Status: Active | Last Updated: August 2026

The file

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

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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
  1. Distinctive:

    Ensure Model Context Protocol interfaces remain available for sibling agents.

    line 15
  2. Distinctive:

    Follow the universal agent protocols defined in the root AGENTS.md.

    line 28
  3. Distinctive:

    Ensure all new features are accompanied by corresponding tests (zero-mock policy).

    line 30

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

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

Codomyrmex Agents — examples

Version: v1.3.0 | Status: Active | Last Updated: August 2026

Purpose

Example implementations and demonstrations.

Active Components

  • README.md – Project file
  • invalid_prompt_demo.py – Project file
  • sample_api.py – FastAPI sample (uv run python examples/sample_api.py with fastapi and uvicorn; not collected by default pytest)

Operating Contracts

  • Maintain alignment between code, documentation, and configured workflows.
  • Ensure Model Context Protocol interfaces remain available for sibling agents.
  • Record outcomes in shared telemetry and update TODO queues when necessary.

Key Files

  • AGENTS.md - Agent coordination and navigation
  • README.md - Directory overview
  • README.md
  • invalid_prompt_demo.py

Dependencies

  • Inherits dependencies from the parent module. See pyproject.toml or package.json for global dependencies.

Development Guidelines

  • Follow the universal agent protocols defined in the root AGENTS.md.
  • Adhere to the Python PEP 8 style guide and project-specific linting rules.
  • Ensure all new features are accompanied by corresponding tests (zero-mock policy).

Navigation Links

  • 🏠 Project Root: ../README.md - Main project documentation

Related Documents

  • Spec: SPEC.md is inherited from the nearest parent scope.

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.

Check your setup, free