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/haabe/mycelium/claude-mdgit clone --depth 1 https://github.com/haabe/myceliumWrote 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/haabe/mycelium/claude-md)<a href="https://agentmods.dev/instructions/haabe/mycelium/claude-md"><img src="https://agentmods.dev/badge/instructions/haabe/mycelium/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.03725 | $0.03725 |
| Opus 5 | $0.01862 | $0.01862 |
| Sonnet 5 | $0.00745 | $0.00745 |
| Haiku 4.5 | $0.00373 | $0.00373 |
Grade B, and why
mycelium CLAUDE.md scanned grade B with 1 finding 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 today.
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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
**Canvas writes — Read before Write (HARD RULE).** Canvas files ship pre-populated, so every `.claude/canvas/*.yml` exists on a fresh project. `Write`/`Edit` require a prior **`Read` tool** call (same session); **`cat`/` How it starts
The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mycelium: Theory-Guided Agentic Product Development
Version 0.175.2 -- Attribution label: readme-pie-palette-meets-wcag-on-both-surfaces-2026-09-03 (PATCH). The README pie shipped in near-black fills that all but vanished on GitHub's dark canvas. Re-picked from the validated categorical palette and checked computationally rather than by eye: #3987e5 / #d95926 / #199e70 clear WCAG 1.4.11 (3:1 non-text) against both #ffffff and #0d1117, carry black section labels at 5.4-6.2:1 (clearing 1.4.3's 4.5:1), and pass the dataviz validator's CVD gate in both modes (worst all-pairs deutan Delta E 9.4, normal-vision 20.9). Slice borders are white at 2px, which reads as a separator gap on the light surface and a crisp ring on the dark one, plus a #8b949e outer ring that clears 3:1 on both. Title and legend colors are deliberately NOT pinned, so GitHub's per-mode theme still supplies them. Prior: 0.175.1 -- Attribution label: readme-backs-discovery-claim-with-a-count-2026-09-03 (PATCH). The README's claim that nobody thinks discovery is optional rested on one person's word for it. Added a hand-read count instead: 46 shipped-to-no-traction posts across r/microsaas, r/SideProject and r/vibecoding, 37 of 46 never mentioning contact with anyone who had the problem. New receipts case docs/receipts/cases/2026-08-16-l1-population-read.md carries the method and the limits (floor not a rate, timing not coded). A craft audit found and fixed the three weakest sections of the README in the same pass, judged by voice against the rest of the file rather than by keyword.
Full version history: docs/changelog.md.
Mycelium is a harnessing system for AI-assisted product development. It connects theories, shares learning, adapts to conditions, and makes the whole ecosystem stronger.
You are an agent operating within Mycelium. Every action you take must be guided by the frameworks below, harnessed by the guardrails, and logged in the decision system.
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.
- today Changed · +140 tokens per session d0f6fb648c65
- today Changed · -66 tokens per session a594546afadb
- 4d ago First seen · 129 lines · 3,651 tokens per session scan B efe9378df8dd
mycelium CLAUDE.md is an instructions file published in the GitHub repository haabe/mycelium (45 stars, last pushed today), licensed MIT. It adds 3,725 tokens to every session, about $0.0186 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
openevolve sidebar-node-logic.instructions.md
Instructions for algorithmicsuperintelligence/openevolve, a project described as: Open-source implementation of AlphaEvolve.
index AGENTS.md
AGENTS.md instructions for indexnetwork/index, covering agents.md, how we build, repository map and boundaries, api layering (services/api/src) and protocol package (packages/protocol).
index CLAUDE.md
Claude Code instructions for indexnetwork/index, covering claude.md, how we build: startup rules, where things live, protocol package rules (packages/protocol) and tests.
ottonomous CLAUDE.md
Instructions for brsbl/ottonomous, covering ottonomous repository guide, product contract, skill behavior, spec and review.
salva CLAUDE.md
Instructions for 0xRyanlee/salva, covering salva runtime — project context for claude code, what this project is, core product philosophy, event-triggered, not schedule-driven and api-first, agent-native.
mcp-yandex-dostavka CLAUDE.md
Claude Code instructions for A1-x-Tech/mcp-yandex-dostavka, covering claude.md — mcp-yandex-dostavka, commands, architecture, conventions (do not break) and adding a tool.