--- title: "myco" description: "Your project's memory: the sessions that happened, the durable observations drawn from them, and the plans. Skills and tools for reading why the code is the way it is, and for recording what you learn." canonical: https://agentpluginsdirectory.com/plugins/myco last-updated: 2026-10-21 --- # myco Your project's memory: the sessions that happened, the durable observations drawn from them, and the plans. Skills and tools for reading why the code is the way it is, and for recording what you learn. - Slug: myco - Publisher: Goondocks - Repository: https://github.com/goondocks-co/myco - Manifest: plugins/myco/plugin.json - Version: 2.0.0-alpha.10 - License: Apache-2.0 - Category (editorial): other - Skills: 9 (myco-handoff, myco-okf, myco-outcome-tasks, myco-rules, myco-server-debugging, myco-server-provisioning, myco-settings, myco-setup, myco) - MCP servers: 0 - Stars: 14 - Repository created: 2026-03-15 - Repository last pushed: 2026-10-21 - Publisher type: Organization - Listing: https://agentpluginsdirectory.com/plugins/myco - Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json ## What myco does, in the publisher's words Your project's memory: the sessions that happened, the durable observations drawn from them, and the plans. Skills and tools for reading why the code is the way it is, and for recording what you learn. Skills, and one MCP entry pointing at your Myco deployment. That is the whole of it. It carries no binary and no hooks. A hook command is the absolute path of the myco binary on your own machine, resolved when that binary is installed, so a downloadable bundle has neither the binary nor the path it will live at. Sessions are therefore not captured by the plugin alone. - Deployment URL: The base URL of your team's Myco deployment, for example https://myco.example.com - Access key: A project access key from your deployment dashboard. It reaches one project and expires. From the project README, punctuation lightly normalized. Full text: https://raw.githubusercontent.com/goondocks-co/myco/HEAD/plugins/myco/README.md ## Skills - myco-handoff: Carry a session's working intention to another session or another agent. PREPARE compresses why we are here, what we are doing, the gotchas, the dead ends and the decisions already closed into a digest of at most 1500 tokens, saved on a Myco plan. RECEIVE takes that plan id, rehydrates the context,… - myco-okf: Create or maintain an OKF-conformant project wiki, a portable, git-committed markdown knowledge base that lives in the repository rather than in Myco. Turns what Myco holds, the spores and sessions and plans, into human-readable documentation that ships with the code. Any agent can run the procedur… - myco-outcome-tasks: Author and debug the tasks Myco's own agent runs. A task is one prompt with declared expected evidence, dispatched to a runner: no phases, no turn budget, no orchestrator. It declares the gate that admits it, the tools its run may call, its schedule if it has one, and how the server decides afterwa… - myco-rules: Keep AGENTS.md minimal, durable and canonical across every agent that reads it. Adds, trims and audits project rules without letting the rules file decay into a dump of whatever was true last week. - myco-server-debugging: Work out why a Myco deployment refused something, lost something, or stopped doing something. The server answers a caller's own fault as a terminal refusal carrying a named code, and its own faults as a retryable failure, telling those two apart is the first move in every investigation, because onl… - myco-server-provisioning: Provision, update, roll back and destroy the Cloudflare Deployment, the Worker front door, with `myco server --target cloudflare`. One verb, from artifacts the binary carries: no source checkout on the machine that deploys, and no container runtime anywhere. - myco-settings: Change a Myco deployment's settings safely, and add a new setting correctly. Deployment settings are one tier with one writer: every change admits the leaf, authorizes the actor, checks the leaf's own rule, persists it with its actor, and re-arms whatever schedule it moved, in that order, in one mo… - myco-setup: Finish setting Myco up on this machine: install the binary, join a Deployment, connect repositories and verify capture. Also use for a 1.4 cutover, an optional runner, or leaving the wrong Deployment. - myco: Myco is this project's memory: the sessions that happened, the durable observations (spores) drawn from them, and the plans. It holds why the code is the way it is, which the code itself cannot show. Use it before a design decision, when debugging something non-obvious, when a structure looks arbit… Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.