Borrowing it
Nothing to install: this file belongs to krapie/mycelium. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/krapie/mycelium/main/AGENTS.mdgit clone --depth 1 https://github.com/krapie/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/krapie/mycelium/agents-md)<a href="https://agentmods.dev/instructions/krapie/mycelium/agents-md"><img src="https://agentmods.dev/badge/instructions/krapie/mycelium/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/krapie/mycelium/agents-md"><img src="https://agentmods.dev/badge/instructions/krapie/mycelium/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.04934 | $0.04934 |
| Opus 5.5 | $0.01974 | $0.01974 |
| Sonnet 5.5 | $0.00987 | $0.00987 |
| Haiku 4.5 | $0.00493 | $0.00493 |
Grade C, and why
mycelium AGENTS.md scanned grade C 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 4d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
4. Never run a destructive `mycelium cleanup reset`/`rm -rf ~/.mycelium` type command against the real store while verifying a change — use `mycelium demo` (isolated `~/.mycelium-demo`) or a temp `MYCELIUM_HOME` instead. How it starts
The opening of the file, as written. The whole thing — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Orientation for an AI coding agent (Claude Code, Codex, Cursor, or similar) working in this repository. If you're a human, README.md and docs/ are the better starting point — this file is dense and reference-oriented on purpose.
This follows the AGENTS.md standard — read natively by Codex and other AGENTS.md-aware tools. Claude Code does not read AGENTS.md on its own (confirmed against Anthropic's own docs — it only ever auto-loads CLAUDE.md), so CLAUDE.md in this repo's root just imports this file via @AGENTS.md. That's also exactly the gap src/reuse.js's injectAgentsMd() needs to account for when writing to a target project — see that file's own doc comment.
What this tool is
Mycelium is a local-first Context Lifecycle TUI for AI coding-agent sessions. It manages context produced by AI collaboration through four stages — Capture → Organize → Learn → Reuse — implemented as a terminal UI (neo-blessed) plus a CLI, both reading/writing a plain-file store under ~/.mycelium/.
Why it exists
AI coding sessions (Claude Code, Codex, Kiro, OpenCode, ...) accumulate fast and lose context across three axes:
- Model boundaries — switching agents mid-task loses everything the previous agent knew (see Handoff below).
- Time — a session from three weeks ago is unfindable without search/organization.
- Space — nothing links related sessions across a project's lifetime unless something builds that structure.
Mycelium's answer: capture every session losslessly into a neutral schema, organize it (LLM-assisted, human-confirmed) into folders, learn from finished sessions (auto-summarize, extract project knowledge), and reuse that knowledge — injected into AGENTS.md for the next agent, or composed into a handoff prompt when switching agents mid-task. See docs/features.md for the full capability catalog and docs/architecture.md for design principles (local-only, model-agnostic, human-first, minimal dependencies).
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.
- 4d ago Changed · +3 lines · +110 tokens per session c1635f1b68ed
- 8d ago Changed · +1 lines · +59 tokens per session 883e689a1a60
- 13d ago Changed · +1 lines · +73 tokens per session 36e3cde8e378
- 16d ago Changed · +2 lines · +61 tokens per session 080999a083ef
- 1mo ago Changed · +2 lines · +63 tokens per session c191265c99a5
- 1mo ago First seen · 123 lines · 4,568 tokens per session scan C 7d99ea50158f
mycelium AGENTS.md is an instructions file published in the GitHub repository krapie/mycelium (42 stars, last pushed 2d ago), licensed MIT. It adds 4,934 tokens to every session, about $0.0197 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
vscode model-prompts.instructions.md
Model-specific prompt authoring and registry guidelines.