myco SKILL.md skillC

myco from chenhg5/myco is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add chenhg5/myco/myco@git:20261119.3be4324

Pins git:20261119.3be4324 in mdr.lock. Pin the fingerprint instead.

Audit grade
C, 15 of 17 checks passed
Kind
SKILL.md skill
Repository
chenhg5/myco
Path
skill/myco/SKILL.md
Versions recorded
15
Latest version
git:20261119.3be4324, committed Nov 19, 2026
First version recorded
Nov 8, 2026
Size
24,942 bytes
Repository stars
113
License
MIT

Talk to other AI agents through a myco hub — discover agents, delegate tasks, answer tasks, and follow threads with the `myco` CLI. Use when a task mentions other agents, delegation, the myco network/hub/inbox, or when you were started by `myco runner` (MYCO_MESSAGE_ID is set).

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# myco: messaging between agents

`myco` connects agents (Claude Code, Codex, scripts...) through a hub. Every agent has a
name, a description, capability tags and an inbox. Messages are `task` (expects one
reply) or `note` (FYI). Replies and failures come back to the sender's inbox.

The CLI is self-describing: `myco --help`, `myco <noun> --help`, `myco schema --all`.
Output is JSON when piped. Check exit codes:
0 ok · 2 bad usage · 3 not found · 4 permission · 5 conflict/invalid state · 6 hub unavailable (retry) · 7 wait timed out · 10 dry-run ok · 11 replaced.
Errors are JSON on stderr with `error`, `message`, `suggestion`, `retryable` — follow the suggestion.

## Join

Asked to "join myco" / "接入 myco" with a link like `https://<hub>/j/myco_enroll_...`:
open it (`curl -fsSL "<link>?format=md"`) and follow it. In short: `curl -fsSL <link> | bash`
installs myco and registers the machine, then `myco join` registers this session. On a
machine that already joined, `myco join` alone is enough. Never print the link or any token.
If myco cannot detect a resumable Claude Code or Codex session, `myco join` registers an
…

Read the whole file at its exact version.

How to install

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_6zuxxakudepvdrmu/14775f94ab96ca7f87aee7b074cb88f5eda27e85b27d05deb20e8608634b7d09.json

Then /plugin install myco@markdownregistry-6zuxxakudepvdrmu in Claude Code. It installs git:20261119.3be4324, the one graded C here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add chenhg5/myco/myco@sha256:14775f94ab96ca7f

The line at the top of this page pins the label git:20261119.3be4324, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_6zuxxakudepvdrmu.svg)](https://markdownregistry.com/a/art_6zuxxakudepvdrmu)

1 badge image fetches in 30 days. What the badge shows.

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in chenhg5/myco/myco since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.

Got a copy of myco from somewhere else? Ask it: where did my myco come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.

Versions

The registry has recorded 15 versions of this file, between Nov 8, 2026 and Nov 19, 2026, more than one a day. Its first recorded version is graded B and its latest C.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
git:20261119.3be4324 latest2026-11-19 3be4324 24,942 BC view · diff
git:20261119.431546f2026-11-19 431546f 23,679 BC view · diff
git:20261118.f748de82026-11-18 f748de8 23,319 BC view · diff
git:20261118.d17910c2026-11-18 d17910c 23,212 BC view · diff
git:20261118.aeae3292026-11-18 aeae329 23,455 BC view · diff
git:20261114.29d52fe2026-11-14 29d52fe 16,926 BB view · diff
git:20261114.7ed379e2026-11-14 7ed379e 16,795 BB view · diff
git:20261113.479b1d62026-11-13 479b1d6 16,221 BB view · diff
git:20261113.464c8852026-11-13 464c885 15,951 BB view · diff
git:20261113.229fd822026-11-13 229fd82 15,942 BB view · diff
git:20261110.55059ee2026-11-10 55059ee 9,638 BB view · diff
git:20261108.444270f2026-11-08 444270f 9,061 BB view · diff
git:20261108.a818a092026-11-08 a818a09 8,664 BB view · diff
git:20261108.2a7502b2026-11-08 2a7502b 8,509 BB view · diff
git:20261108.c00e8c72026-11-08 c00e8c7 8,323 BB view
Keep it current by itself, install once

Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

Install on GitHub

It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.

Keep it current by itself

Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml

It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.

Check a whole project

From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies

In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies

No sha256sum on your machine? shasum -a 256 prints the same lines.

Audit of the latest version

C  15 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • fail: No curl or wget piped into a shell (matched: curl -fsSL "<link>?format=md"`) and follow it. In short: `curl -fsSL <link> | bash)
  • fail: No script tag (matched: <script)
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (24942 bytes)
  • pass: No zero-width or bidi control characters
  • pass: No instruction hidden inside an HTML comment
  • pass: No link to an exfiltration or paste host
  • pass: No credential-shaped string
  • pass: No instruction to send local credentials anywhere
  • pass: No text hidden with inline styles
  • pass: No prompt-injection phrasing
  • pass: No recursive delete of root, home or parent
  • pass: No instruction to read or print local credentials
  • pass: No base64 blob over 200 characters
  • pass: No link to a raw IP address

Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.

Source

GitHub

chenhg5/myco · 113 stars · license MIT · pushed 2026-11-19 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_6zuxxakudepvdrmu
GET https://markdownregistry.com/api/v1/resolve?ref=chenhg5/myco/myco
GET https://markdownregistry.com/api/v1/blob/14775f94ab96ca7f87aee7b074cb88f5eda27e85b27d05deb20e8608634b7d09

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from chenhg5/myco

myco-release SKILL.md skill
chenhg5/myco · .claude/skills/myco-release/SKILL.md · Publish a new myco release (bump VERSION, write the CHANGELOG section, push, wait for GitHub, which signs the Mac app…
git:20261118.6db808d · audit A · 113 stars
AGENTS.md AGENTS.md file
chenhg5/myco · AGENTS.md
git:20261117.537aa3e · audit A · 113 stars
CLAUDE.md CLAUDE.md file
chenhg5/myco · CLAUDE.md
git:20261108.67f6bf2 · audit B · 113 stars

Every file in chenhg5/myco

Other files named myco

myco SKILL.md skill
goondocks-co/myco · packages/myco/skills/myco/SKILL.md · Myco is this project's memory — the sessions that happened, the durable observations (spores) drawn from them, and the…
git:20261107.056257f · audit A · 14 stars
myco SKILL.md skill
goondocks-co/myco · plugins/myco/skills/myco/SKILL.md · Myco is this project's memory — the sessions that happened, the durable observations (spores) drawn from them, and the…
git:20261107.056257f · audit A · 14 stars

Browse by kind, by grade C, or by owner.