agent-relay SKILL.md skillA
agent-relay from agentworkforce/relay is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add agentworkforce/relay/agent-relay@git:20260820.32c36b8Pins git:20260820.32c36b8 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- agentworkforce/relay
- Path
plugins/codex-relay-skill/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260820.32c36b8, committed Aug 20, 2026
- First version recorded
- May 27, 2026
- Size
- 6,931 bytes
- Repository stars
- 1,134
- License
- Apache-2.0
Use when you need Codex to coordinate multiple agents through Agent Relay for peer-to-peer messaging, lead/worker handoffs, or shared status tracking across sub-agents and terminals.
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
# Agent Relay Use this skill when Codex needs real-time coordination across multiple agents. It gives Codex a repeatable workflow for: - connecting to an Agent Relay workspace - spawning relay-aware workers - sending direct messages, channel updates, and thread replies - keeping lead and worker state synchronized through ACK, STATUS, BLOCKED, and DONE signals Relay fills the peer-to-peer gap in Codex sub-agent workflows. Codex can spawn and collect worker results, but Agent Relay gives those workers a shared message bus so they can talk to the lead and to each other. ## Auto-setup On first activation, this skill auto-configures Codex by running `scripts/setup.sh`. This adds the Agent Relay MCP server to `.codex/config.toml`, enables hooks, installs `hooks.json`, and copies the `relay-worker.toml` agent definition. No manual setup is required after installing the skill. ## Startup protocol Every relay-connected Codex agent must complete these steps IN ORDER before substantive work: 1. **Set up a workspace.** - If `RELAY_WORKSPACE_KEY` is set in the environment, call `set_workspace_key` with that key. …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_z4onze7vkfweq5ee/6128972aeeba54d9ec8eeb1077f0da1a5aabd891e2a23fe58ad96d8b7b5ccb56.json
Then /plugin install agent-relay@markdownregistry-z4onze7vkfweq5ee in Claude Code. It installs git:20260820.32c36b8, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add agentworkforce/relay/agent-relay@sha256:6128972aeeba54d9The line at the top of this page pins the label git:20260820.32c36b8, 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.
[](https://markdownregistry.com/a/art_z4onze7vkfweq5ee)
4 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in agentworkforce/relay/agent-relay 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 agent-relay from somewhere else? Ask it: where did my agent-relay 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 5 versions of this file, between May 27, 2026 and Aug 20, 2026, about one every 21 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260820.32c36b8 latest | 2026-08-20 | 32c36b8 | 6,931 B | A | view · diff |
| git:20260802.28a6e9a | 2026-08-02 | 28a6e9a | 6,830 B | A | view · diff |
| git:20260610.2c174d7 | 2026-06-10 | 2c174d7 | 6,587 B | A | view · diff |
| git:20260603.1cb41cf | 2026-06-03 | 1cb41cf | 5,807 B | A | view · diff |
| git:20260527.bc15db8 | 2026-05-27 | bc15db8 | 5,805 B | A | view |
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.
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.
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.
Installed this file, say at .claude/skills/agent-relay/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
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
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (6931 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 curl or wget piped into a shell
- 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
- pass: No script tag
Source
agentworkforce/relay · 1,134 stars · license Apache-2.0 · pushed 2026-11-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_z4onze7vkfweq5ee GET https://markdownregistry.com/api/v1/resolve?ref=agentworkforce/relay/agent-relay GET https://markdownregistry.com/api/v1/blob/6128972aeeba54d9ec8eeb1077f0da1a5aabd891e2a23fe58ad96d8b7b5ccb56
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.