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 agents/docxology/codomyrmex/indexgit clone --depth 1 https://github.com/docxology/codomyrmexWhat 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.00000 | $0.00484 |
| Opus 5 | $0.00000 | $0.00242 |
| Sonnet 5 | $0.00000 | $0.00097 |
| Haiku 4.5 | $0.00000 | $0.00048 |
Grade A, and why
index 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 2d 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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agents Module - Documentation
Welcome to the detailed documentation for the Agents module.
This documentation provides in-depth information beyond the main README.md for this module. It is intended for developers working on or with this module, and for users seeking a deeper understanding of its capabilities and design.
The main documentation/ module of the Codomyrmex project may compile this content into a central documentation website.
Table of Contents
- Technical Overview
- API Specification
- Usage Examples
- Tutorials
- Contributing Guidelines (Link to contribution guide)
How to Use This Documentation
- Start with the Technical Overview for a high-level understanding of the module's architecture.
- Refer to the API Specification for details on how to interact with the module programmatically.
- Explore the Usage Examples and Tutorials to see the module in action.
Navigation Links
- Parent: Project Overview
- Module Index: All Agents
- Documentation: Reference Guides
- Home: Root README
Detailed Architecture and Implementation
The implementation of this component follows the core principles of the Codomyrmex ecosystem: modularity, performance, and reliability. By adhering to standardized interfaces, this module ensures seamless integration with the broader platform.
Design Principles
- Strict Modularity: Each component is isolated and communicates via well-defined APIs.
- Performance Optimization: Implementation leverages lazy loading and intelligent caching to minimize resource overhead.
- Error Resilience: Robust exception handling ensures system stability even under unexpected conditions.
- Extensibility: The architecture is designed to accommodate future enhancements without breaking existing contracts.
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.
- 2d ago First seen · 44 lines · 0 tokens per session scan A 05fea08e1206
index is an agent published in the GitHub repository docxology/codomyrmex (11 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 484 tokens. 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 agents, from other repositories
docs-writer
Expert technical documentation specialist for creating comprehensive, user-friendly documentation across all project types. Use proactively for API docs, user guides, and technical documentation.
code-explainer
Explains complex code in clear, understandable terms. Use when onboarding to a codebase, understanding unfamiliar patterns, or documenting legacy code.
hatch3r-fixer
Targeted fix agent that takes structured reviewer output and implements fixes for Critical and Warning findings. Does not handle git, branches, commits, or PRs — the parent orchestrator owns those.
content-editor
Writes and edits the portfolio's pages. Reads a brief, follows the style guide, and emits the HTML into public/.
demo-agent
Example agent that handles read and shell tasks. Solo node at boot; gets connected to the rest of the demo fixture during the Live UI step.
AUTONOMOUS_CONTINUATION_PLAN
A unified NodeBench subsystem enabling agents to self-heal from both semantic errors (rollback + lessons) and infrastructure failures (capability-aware model failover + budget gates), so long-running research jobs keep making progress when the user steps away.