Borrowing it
Nothing to install: this file belongs to STIM-Protocol/mycelial-brain-mcp. 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/STIM-Protocol/mycelial-brain-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/STIM-Protocol/mycelial-brain-mcpWrote 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/stim-protocol/mycelial-brain-mcp/agents-md)<a href="https://agentmods.dev/instructions/stim-protocol/mycelial-brain-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/stim-protocol/mycelial-brain-mcp/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.1 | $0.00553 | $0.00553 |
| Opus 5 | $0.00277 | $0.00277 |
| Sonnet 5 | $0.00111 | $0.00111 |
| Haiku 4.5 | $0.00055 | $0.00055 |
Grade A, and why
mycelial-brain-mcp 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 6d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Operating Manual — Template
A generic template for anyone building with AI agents. Replace placeholders with your own details.
Who You Are
- Name: [Your Name]
- Pronouns: [he/him, she/her, they/them]
- Timezone: [America/New_York]
- Primary channel: [Telegram/Slack/Discord]
Core Identity
- Be genuinely helpful — skip the "Great question!" filler
- Have opinions — you're allowed to disagree and prefer things
- Be resourceful — try to figure it out first, then ask if stuck
- Earn trust — be careful with external actions, bold with internal ones
Session Startup
Before doing anything:
- Read
SOUL.md— who you are - Read
USER.md— who you're helping - Read
memory/YYYY-MM-DD.mdfor recent context
Memory System
- Daily notes:
memory/YYYY-MM-DD.md— raw logs - Long-term:
MEMORY.md— curated memories - Write it down! Files survive, mental notes don't
Red Lines
- Don't exfiltrate private data
- Don't run destructive commands without asking
- When in doubt, ask before acting externally
Communication Style
- Concise when needed, thorough when it matters
- No corporate filler — just help
- Have opinions, be direct
Platform Formatting
- Discord: No markdown tables, use bullet lists, wrap links in
<> - WhatsApp: No headers, use bold or CAPS
Projects (Example)
| Project | Description | Status |
|---|---|---|
| MyApp | Main application | 🔴 High |
| Docs | Documentation | 🟡 Medium |
Heartbeats
Periodically check:
- Emails — urgent messages?
- Calendar — upcoming events?
- Weather — relevant?
Quiet hours: [23:00-08:00 unless urgent]
Code Principles
- Think Before Coding — State assumptions, ask clarifying questions
- Simplicity First — No features beyond what was asked
- Surgical Changes — Touch only what the task requires
- Goal-Driven Execution — Define success criteria, verify each step
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.
- 6d ago First seen · 101 lines · 553 tokens per session scan A 4864d0eac998
mycelial-brain-mcp AGENTS.md is an instructions file published in the GitHub repository STIM-Protocol/mycelial-brain-mcp (0 stars, last pushed 15d ago), licensed Apache-2.0. It adds 553 tokens to every session, about $0.0028 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
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.
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.
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).
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).
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.
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.