Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/docxology/codomyrmex/claude-mdgit clone --depth 1 https://github.com/docxology/codomyrmexWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/docxology/codomyrmex/claude-md)<a href="https://agentmods.dev/instructions/docxology/codomyrmex/claude-md"><img src="https://agentmods.dev/badge/instructions/docxology/codomyrmex/claude-md.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.04570 | $0.04570 |
| Opus 5 | $0.02285 | $0.02285 |
| Sonnet 5 | $0.00914 | $0.00914 |
| Haiku 4.5 | $0.00457 | $0.00457 |
Grade A, and why
codomyrmex CLAUDE.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 382 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Version: v1.3.0 | Last Updated: March 2026
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Build & Development Commands
# Install dependencies (uv recommended)
uv sync
# Set up git submodules (run once after cloning, or after submodule updates)
# Initializes all 5 submodules and installs hermes/evolution Python deps
bash scripts/setup_submodules.sh
# Or via Makefile:
make submodules # submodules only
make setup # install + submodules together
# NOTE: Never run `uv sync` inside src/codomyrmex/agents/hermes/evolution/ —
# its `darwinian` optional extra requires a non-PyPI package and will fail locking.
# The setup script handles this correctly via `uv venv --seed` + pip.
# Install with optional module dependencies
uv sync --extra <module-name> # e.g., uv sync --extra spatial
uv sync --all-extras # Install all optional dependencies
# Run all tests (no coverage — fast default)
uv run pytest
# Run tests with coverage and the 60% gate (same idea as `make test`).
# Makefile exports HYPOTHESIS_NO_NPY=1; for raw pytest, prefix the command so Hypothesis
# initializes before conftest (see tests/RUNNING_TESTS.md).
HYPOTHESIS_NO_NPY=1 uv run pytest --cov=src/codomyrmex --cov-report=html --cov-fail-under=60
# Pre-tag / release checklist: ruff + ty + full test tree with 60% coverage floor
make verify-release
# Run specific test file or module
uv run pytest tests/unit/<module>/test_<module>.py
uv run pytest -k "test_name" # Run tests matching pattern
# Code formatting and linting
uv run ruff format src/
uv run ruff check src/
uv run ty check src/
# CLI usage
codomyrmex --help
codomyrmex check # Verify environment setup
codomyrmex modules # List available modules
codomyrmex status # System status dashboard
codomyrmex shell # Interactive shell
codomyrmex workflow list # List workflows
codomyrmex project list # List projects
codomyrmex ai generate # AI code generation
codomyrmex analyze <path> # Code analysis
codomyrmex build <path> # Project build
codomyrmex test <module> # Run module tests
codomyrmex fpf fetch <url> # FPF fetch/parse/export
codomyrmex skills list # Skill management
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 5d ago First seen · 382 lines · 4,570 tokens per session scan A 0f91e1e767cb
codomyrmex CLAUDE.md is an instructions file published in the GitHub repository docxology/codomyrmex (11 stars, last pushed today), licensed MIT. It adds 4,570 tokens to every session, about $0.0229 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
ai-dial-core CLAUDE.md
Claude Code instructions for epam/ai-dial-core, covering claude.md, build & run, set credentials via environment variables, build (skip tests) and run all tests.
ai AGENTS.md
AGENTS.md instructions for vercel/ai, covering agents.md, project overview, repository structure, key directories and core package dependencies.
blockrun-mcp AGENTS.md
AGENTS.md instructions for BlockRunAI/blockrun-mcp, covering blockrun mcp, commands, project structure, key dependencies and install in codex.
InvestSkill GEMINI.md
Gemini CLI instructions for yennanliu/InvestSkill, covering investskill — gemini cli setup & usage guide, installation & setup, quick start, navigate to the investskill directory and start gemini cli (loads gemini.md automatically).
technocore-chat AGENTS.md
AGENTS.md instructions for flop-labs/technocore-chat: CI runs exactly these — run them before pushing.
openrouter-mcp-multimodal AGENTS.md
AGENTS.md instructions for stabgan/openrouter-mcp-multimodal, covering agent instructions, before you ship, releasing (read this before publishing), short version and version files (must all match package.json).