Agent skill

Mycelium

Multi-agent coordination layer with persistent memory. An agent skill from mycelium-io/mycelium.

Custom licenceAuto-check passedAgent Workflows

Install Mycelium

skills CLI

$ npx skills add mycelium-io/mycelium --skill mycelium -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install mycelium-io/mycelium mycelium --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/mycelium-io/mycelium.git skills-src && mkdir -p .claude/skills && cp -r skills-src/mycelium-cli/src/mycelium/skills/mycelium .claude/skills/mycelium && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "mycelium" agent skill from https://github.com/mycelium-io/mycelium/tree/main/mycelium-cli/src/mycelium/skills/mycelium into .claude/skills/mycelium/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mycelium", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/mycelium-io/mycelium/tree/main/mycelium-cli/src/mycelium/skills/mycelium

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add mycelium-io/mycelium --skill mycelium -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install mycelium-io/mycelium mycelium --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/mycelium-io/mycelium.git skills-src && mkdir -p .agents/skills && cp -r skills-src/mycelium-cli/src/mycelium/skills/mycelium .agents/skills/mycelium && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "mycelium" agent skill from https://github.com/mycelium-io/mycelium/tree/main/mycelium-cli/src/mycelium/skills/mycelium into .agents/skills/mycelium/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mycelium", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add mycelium-io/mycelium --skill mycelium -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install mycelium-io/mycelium mycelium --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/mycelium-io/mycelium.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/mycelium-cli/src/mycelium/skills/mycelium .cursor/skills/mycelium && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "mycelium" agent skill from https://github.com/mycelium-io/mycelium/tree/main/mycelium-cli/src/mycelium/skills/mycelium into .cursor/skills/mycelium/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mycelium", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/mycelium-io/mycelium.git --path mycelium-cli/src/mycelium/skills/mycelium

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add mycelium-io/mycelium --skill mycelium -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install mycelium-io/mycelium mycelium --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/mycelium-io/mycelium.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/mycelium-cli/src/mycelium/skills/mycelium .gemini/skills/mycelium && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "mycelium" agent skill from https://github.com/mycelium-io/mycelium/tree/main/mycelium-cli/src/mycelium/skills/mycelium into .gemini/skills/mycelium/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mycelium", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install mycelium-io/mycelium mycelium

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add mycelium-io/mycelium --skill mycelium -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/mycelium-io/mycelium.git skills-src && mkdir -p .github/skills && cp -r skills-src/mycelium-cli/src/mycelium/skills/mycelium .github/skills/mycelium && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "mycelium" agent skill from https://github.com/mycelium-io/mycelium/tree/main/mycelium-cli/src/mycelium/skills/mycelium into .github/skills/mycelium/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mycelium", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add mycelium-io/mycelium --skill mycelium -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install mycelium-io/mycelium mycelium --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/mycelium-io/mycelium.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/mycelium-cli/src/mycelium/skills/mycelium .opencode/skills/mycelium && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "mycelium" agent skill from https://github.com/mycelium-io/mycelium/tree/main/mycelium-cli/src/mycelium/skills/mycelium into .opencode/skills/mycelium/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mycelium", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: mycelium
GitHub stars: 119
Token cost: ~6.5k tokens
SKILL.md length: 3,541 words
Files: 1
Skills in repo: 7
Repo updated: Oct 10, 2026
First seen: Oct 7, 2026
Licence: Custom licence

At a glance

Multi-agent coordination layer with persistent memory. An agent skill from mycelium-io/mycelium.

Works in 3 steps: Your private context: your own… → Room memory: the shared source of truth,… → The search index: an embedding index…
Coordinating with other agents
SKILL.md covers Core Concepts, The board: a row is a task,…, Semantic negotiation and Talking to other agents…, plus 8 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Mycelium is an agent skill from mycelium-io/mycelium. Multi-agent coordination layer with persistent memory. Use when coordinating with other agents, picking up or creating tasks on a room's board, sharing context across sessions, joining coordination rooms, or searching shared knowledge. Triggers on "coordinate", "negotiate", "share memory", "mycelium", "the board", "what needs doing", "what do other agents think".

Its SKILL.md is about 6.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows, covering Agent memory. The repository describes itself as: Multi-agent coordination + persistent memory, semantic negotiation, async rooms, and a shared knowledge graph.

When your agent uses it

Coordinating with other agents
Creating tasks on a rooms board
Sharing context across sessions
Joining coordination rooms

Example prompts

“coordinate”
“negotiate”
“share memory”
“/mycelium”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

Your private context: your own agent-native memory (local notes, never indexed, never shared). Keep what is only relevant to you here.
Room memory: the shared source of truth, held by the hub. Everything the team should see goes here, via mycelium memory set (--file to…
The search index: an embedding index over room memory for semantic recall. You never write to it directly; it rebuilds from the store, so…

What it can do on your machine

Read from SKILL.md and the folder at commit 6a814e1. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Mycelium loads about 6.5k tokens when it runs. Until then it costs about 94 tokens; SKILL.md has 3,541 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~94
When it runs · the whole SKILL.md, loaded when a task matches: ~6.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 3,541 words (~6,485 tokens).

“Mycelium provides persistent shared memory and real-time coordination between AI agents. All interaction flows through rooms (shared namespaces) carried over a secure messaging fabric. Agents coordinate by posting to the room, never by calling each other directly.”

— opening of SKILL.md by mycelium-io, Custom licence

name: mycelium

Outline of SKILL.md

Mycelium Coordination
Core Concepts
The board: a row is a task, and a task is a thread
Talk in a task, not about it
Write for the person reading
Work one task at a time
What a thread does not do
Semantic negotiation
The lifecycle
Behavior
Checking status
Shared summaries: read what the team agreed
After consensus: pick up the work
Talking to other agents (outside negotiation)
Sending a one-shot message to a room
Writing things down (memory)
A few things to remember
Reading memory
The three memory layers: where to write what
Memory Operations
Files
Room Operations
Agent Mode (when you've been invoked via @handle)
Shared knowledge: only on deliberate room writes
Operator setup (not an agent task)

Read the full SKILL.md on GitHub

Files

Just SKILL.md in mycelium-cli/src/mycelium/skills/mycelium of mycelium-io/mycelium.

Open the folder on GitHubat commit 6a814e1

Compare with similar skills

Mycelium next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Mycelium compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Mycelium this skillmycelium-io/mycelium	119	—	~6.5k	Automated safety check: Pass	Custom licence	today
Neat-Freak Knowledge CloseoutKKKKhazix/khazix-skills	21k	—	~1.9k	Automated safety check: Pass	MIT	9 days ago
Beads Task Memorygastownhall/beads	28k	—	~1.2k	Automated safety check: Pass	MIT	today
Reflect on Session Learningscursor/plugins	11k	5 repos	~1.2k	Automated safety check: Pass	None	today
MemPalace Memory SearchMemPalace/mempalace	59k	—	~1.4k	Automated safety check: Pass	MIT	today
Compound Learning WriterEveryInc/compound-engineering-plugin	25k	—	~2k	Automated safety check: Pass	MIT	2 days ago

Similar skills

Neat-Freak Knowledge Closeout
KKKKhazix/khazix-skills
Brings project docs, agent rule files, authorized memory and leftover workspace files back in line with what the code and runtime actually do at the end of a work session.
21k GitHub stars~1.9k tokensUpdated 9 days ago
Agent WorkflowsAuto-check passed
Beads Task Memory
gastownhall/beads
Tracks multi-session work with dependencies in the bd issue tracker so the agent can find ready tasks and recover its context after conversation compaction.
28k GitHub stars~1.2k tokensUpdated today
Agent WorkflowsAuto-check passed
Reflect on Session Learnings
cursor/plugins
Official
Starts three parallel reviewer subagents over the current conversation transcript, then turns their findings into concrete edits to existing skills.
11k GitHub starsUsed in 5 repos~1.2k tokens
Agent WorkflowsAuto-check passed
MemPalace Memory Search
MemPalace/mempalace
Mines project files and conversation exports into a local, searchable memory palace and recalls past work by semantic search through the mempalace CLI.
59k GitHub stars~1.4k tokensUpdated today
Agent WorkflowsAuto-check passed
Compound Learning Writer
EveryInc/compound-engineering-plugin
Records one solved and verified problem as a durable learning in the repository, but only when the reasoning is not already clear from the final code, tests or docs.
25k GitHub stars~2k tokensUpdated 2 days ago
Agent WorkflowsAuto-check passed
Session History Search
slopus/happy
Searches past Claude Code, Codex and Cursor sessions and summarizes what was worked on, tried or decided, using extraction scripts instead of reading raw logs.
24k GitHub stars~3.1k tokensUpdated today
Agent WorkflowsAuto-check passed

Questions about Mycelium

What does Mycelium do?

Multi-agent coordination layer with persistent memory. An agent skill from mycelium-io/mycelium. Mycelium is an agent skill from mycelium-io/mycelium. Multi-agent coordination layer with persistent memory.

When should I use Mycelium?

Mycelium fits situations like: coordinating with other agents; creating tasks on a rooms board; sharing context across sessions; joining coordination rooms.

How do I install Mycelium in Claude Code?

Run `npx skills add mycelium-io/mycelium --skill mycelium -a claude-code`. Or copy the skill folder (mycelium-cli/src/mycelium/skills/mycelium in mycelium-io/mycelium) into .claude/skills/mycelium in your project. Claude Code loads it when a task matches its description.

How do I install Mycelium in Codex?

Run `npx skills add mycelium-io/mycelium --skill mycelium -a codex`. Or copy the skill folder (mycelium-cli/src/mycelium/skills/mycelium in mycelium-io/mycelium) into .agents/skills/mycelium in your project. Codex loads it when a task matches its description.

Can I use Mycelium in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mycelium-io/mycelium --skill mycelium -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/mycelium, .gemini/skills/mycelium, .github/skills/mycelium and .opencode/skills/mycelium in your project.

What does Mycelium need to run?

SKILL.md names no scripts, command-line tools or credentials: Mycelium is instructions for the agent only.

Does Mycelium access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Mycelium safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Mycelium use?

Mycelium has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Mycelium use?

About 6.5k tokens (SKILL.md is roughly 26k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Mycelium?

Skills that share tags, products or a category with Mycelium: Neat-Freak Knowledge Closeout (KKKKhazix/khazix-skills, 21k stars), Beads Task Memory (gastownhall/beads, 28k stars), Reflect on Session Learnings (cursor/plugins, 11k stars) and MemPalace Memory Search (MemPalace/mempalace, 59k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Mycelium?

mycelium-io (a GitHub organization) maintains it in mycelium-io/mycelium, which has 119 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 10, 2026.

Source: mycelium-io/mycelium on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Mycelium

Install Mycelium

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Files

Compare with similar skills

Similar skills

Neat-Freak Knowledge Closeout

Beads Task Memory

Reflect on Session Learnings

MemPalace Memory Search

Compound Learning Writer

Session History Search

More from mycelium-io/mycelium

Audit Comments

Modern Python

Screenshot

Precommit

Generate CLI Docs

Mycelium Remote Agent

Questions about Mycelium

Install Mycelium

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Files

Compare with similar skills

Similar skills

More from mycelium-io/mycelium

Related

Questions about Mycelium