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/cherninlab/ennodia/agents-mdgit clone --depth 1 https://github.com/cherninlab/ennodiaWhat 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.00149 | $0.00149 |
| Opus 5 | $0.00075 | $0.00075 |
| Sonnet 5 | $0.00030 | $0.00030 |
| Haiku 4.5 | $0.00015 | $0.00015 |
Grade A, and why
ennodia AGENTS.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 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.
What it actually says
Ennodia
This repo is Bun-first: use bun install for dependencies and
bun run verify before handing off changes. Project rules — thin adapters,
no permission-bypass flags, no provider-private APIs — are in
CONTRIBUTING.md; follow them here too.
Keep progress updates compact and factual. Prefer short bullets; do not
repeat full task details on every poll/tick unless the state changed. A good
update is like: * Working tree is clean. or * Harnesses are available: Gemini -> Antigravity; Kimi/Minimax/GLM -> OpenCode; Opus -> Claude Code; GPT -> Codex.
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 · 13 lines · 149 tokens per session scan A d40bf6382139
ennodia AGENTS.md is an instructions file published in the GitHub repository cherninlab/ennodia (5 stars, last pushed 5d ago), licensed MIT. It adds 149 tokens to every session, about $0.0007 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-31.
Other instructions, from other repositories
helmor AGENTS.md
Instructions for dohooo/helmor, covering agents.md, what is helmor, commands, architecture and three-process model.
zeroshot AGENTS.md
AGENTS.md instructions for the-open-engine/zeroshot, covering zeroshot: multi-agent coordination engine, critical rules, where to look, cluster worker contracts and cli quick reference.
agents CLAUDE.md
Instructions for eloylp/agents, covering claude.md, project overview, directory structure, config model and build & run.
agiwo AGENTS.md
Instructions for xhwSkhizein/agiwo, covering agents.md, how to use this file, truth source order (adr 0048 / 0049), logging and config hot reload.
Agent-Harness-Kit AGENTS.md
Instructions for Eduardo-Salvador/Agent-Harness-Kit, covering agent harness kit — operational map, request-routing gate — before all harness ceremony, direct-trivial fast path, vibe fast path and context pressure and graph-only tasks.
ideate AGENTS.md
Instructions for paultyng/ideate, covering agents.md, build features as mcp tools first, ui second, when to add ui and pattern.