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/transmitt0r/mycelium/agents-mdgit clone --depth 1 https://github.com/Transmitt0r/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/transmitt0r/mycelium/agents-md)<a href="https://agentmods.dev/instructions/transmitt0r/mycelium/agents-md"><img src="https://agentmods.dev/badge/instructions/transmitt0r/mycelium/agents-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.01465 | $0.01465 |
| Opus 5 | $0.00732 | $0.00732 |
| Sonnet 5 | $0.00293 | $0.00293 |
| Haiku 4.5 | $0.00146 | $0.00146 |
Grade A, and why
mycelium 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 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.
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 — 27 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
@README.md has what this monorepo is and how the packages fit together.
Layout
Three top-level categories, all pnpm workspace packages:
core/{embed,index,mcp}— the published@transmitt0r/mycelium-*feature packages. Roottsconfig.json's project references cover only these three; everything else builds independently (plaintsc).core/mcp(@transmitt0r/mycelium-mcp) builds on the official high-levelMcpServerfrom@modelcontextprotocol/sdk(≥^1.30.0, whoseStreamableHTTPServerTransportsupports stateless mode viasessionIdGenerator: undefined) and serves stateless Streamable HTTP (2026-07-28 MCP spec revision): no protocol-level session, one fresh Server + transport per request. Tools are registered at the protocol layer rather thanMcpServer.registerToolso arbitrary TypeBox JSON Schema & annotations pass through unchanged (registerToolis Zod-only).
tools/{tooling-config,openapi-codegen}— published, but internal enablers rather than features: shared biome/tsconfig presets, and shared OpenAPI-schema-to-types codegen logic (consumed by the apps' ownscripts/generate-types.ts, which stay thin wrappers supplying just their own schema-fetching logic).apps/{paperless-ngx,trilium,onepassword}— the OpenClaw plugins this toolkit was extracted from, merged into this repo viagit subtree(full history preserved) so they can consume@transmitt0r/mycelium-*asworkspace:*dependencies instead of a publish round-trip. Each still publishes to npm independently under its own name (@transmitt0r/openclaw-plugin-*), released viasemantic-release+ Conventional Commits — separate from this repo's Changesets flow, but (unlike before the merge) run from a single root-level matrix workflow (.github/workflows/release-apps.yml), not a per-app one: GitHub Actions only discovers workflows under the repo root's.github/workflows/, so a nestedapps/*/.github/workflows/*.ymlsilently never runs.semantic-release-monorepo(each app's.releaserc.json) scopes commit analysis and the release tag to that app's own directory, since all three apps now share one git history.
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 First seen · 27 lines · 1,465 tokens per session scan A 9b2c9f02713f
mycelium AGENTS.md is an instructions file published in the GitHub repository Transmitt0r/mycelium (1 stars, last pushed 28d ago), licensed MIT. It adds 1,465 tokens to every session, about $0.0073 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
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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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 oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.