rigs SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
rigs from mvschwarz/openrig is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add mvschwarz/openrig/rigs@git:20261117.a33abfcPins git:20261117.a33abfc in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- mvschwarz/openrig
- Path
packages/daemon/assets/skills/rigs/SKILL.md- Versions recorded
- 31
- Latest version
- git:20261117.a33abfc, committed Nov 17, 2026
- First version recorded
- Oct 7, 2026
- Size
- 41,858 bytes
- Repository stars
- 8,889
- License
- Apache-2.0
Use when a person in their own Claude Code or Codex session mentions OpenRig, rigs or the rig command, or wants a team of coding agents (Claude Code, Codex) on their project. That includes installing, setting up, starting or updating OpenRig, seeing, getting back to or re-attaching to their OpenRig agents (including bringing a stopped team back), TUI or operator, starting or sharing a team, and joining this session to one. Operating a running rig from inside it…
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
# rigs: your route into OpenRig OpenRig runs a team of coding agents (Claude Code, Codex and others) side by side in tmux. A local daemon keeps their tasks, messages and state, so the team keeps working across restarts. This skill gets OpenRig installed, gets a team working on what the person wants, and shows how to work with that team from here. **The goal is a team doing the person's work, not just an install.** Go through the steps in order and stop early only if the person asks you to. When they say what they want built, give it to OpenRig's operator (step 2) instead of building it yourself. **If `/rigs` or your skill tool said this skill doesn't exist** right after it was added to a running Claude Code session: that session doesn't see a skills folder created after it started. Ask the person to type `/reload-skills` (Claude Code 2.1.152 or later), or start a new session, then `/rigs`. Until then, read this whole file before you act on it; a step skipped here changes where the person answers the team. Tell the person what you're about to run and why before you run it. Don't install system packages or change their …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_guq4rmxhqv4fj46k/c2849d02b022f01742926ef1fae3400c37e57ece734ea3cb495444d0f4dcdaa7.json
Then /plugin install rigs@markdownregistry-guq4rmxhqv4fj46k in Claude Code. It installs git:20261117.a33abfc, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add mvschwarz/openrig/rigs@sha256:c2849d02b022f017The line at the top of this page pins the label git:20261117.a33abfc, 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_guq4rmxhqv4fj46k)
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 mvschwarz/openrig/rigs 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 rigs from somewhere else? Ask it: where did my rigs 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 31 versions of this file, between Oct 7, 2026 and Nov 17, 2026, about one every day.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261117.a33abfc latest | 2026-11-17 | a33abfc | 41,858 B | A | view · diff |
| git:20261117.5ebcd9a | 2026-11-17 | 5ebcd9a | 40,818 B | A | view · diff |
| git:20261116.fc1bf9a | 2026-11-16 | fc1bf9a | 39,880 B | A | view · diff |
| git:20261116.6068c9f | 2026-11-16 | 6068c9f | 39,689 B | A | view · diff |
| git:20261115.861710b | 2026-11-15 | 861710b | 38,248 B | A | view · diff |
| git:20261113.c2815a6 | 2026-11-13 | c2815a6 | 32,098 B | A | view · diff |
| git:20261112.5f2dc3f | 2026-11-12 | 5f2dc3f | 27,228 B | A | view · diff |
| git:20261112.ec53cd1 | 2026-11-12 | ec53cd1 | 26,932 B | A | view · diff |
| git:20261112.b269302 | 2026-11-12 | b269302 | 26,763 B | A | view · diff |
| git:20261111.049637a | 2026-11-11 | 049637a | 26,407 B | A | view · diff |
| git:20261106.829ddfc | 2026-11-06 | 829ddfc | 22,969 B | A | view · diff |
| git:20261025.5e0db11 | 2026-10-25 | 5e0db11 | 22,179 B | A | view · diff |
| git:20261025.a528913 | 2026-10-25 | a528913 | 22,135 B | A | view · diff |
| git:20261025.6d58c28 | 2026-10-25 | 6d58c28 | 20,668 B | A | view · diff |
| git:20261024.676d407 | 2026-10-24 | 676d407 | 18,974 B | A | view · diff |
| git:20261023.0e2f9a6 | 2026-10-23 | 0e2f9a6 | 18,664 B | A | view · diff |
| git:20261021.58862b8 | 2026-10-21 | 58862b8 | 18,506 B | A | view · diff |
| git:20261020.9c903e6 | 2026-10-20 | 9c903e6 | 18,002 B | A | view · diff |
| git:20261020.1f7a8b7 | 2026-10-20 | 1f7a8b7 | 17,515 B | A | view · diff |
| git:20261020.755c66f | 2026-10-20 | 755c66f | 16,865 B | A | view · diff |
| git:20261019.46c5c01 | 2026-10-19 | 46c5c01 | 16,566 B | A | view · diff |
| git:20261019.c64c4e6 | 2026-10-19 | c64c4e6 | 16,093 B | A | view · diff |
| git:20261019.0149d01 | 2026-10-19 | 0149d01 | 15,802 B | A | view · diff |
| git:20261012.ada3678 | 2026-10-12 | ada3678 | 11,756 B | A | view · diff |
| git:20261011.66a13ca | 2026-10-11 | 66a13ca | 11,523 B | A | view · diff |
| git:20261011.b8b6258 | 2026-10-11 | b8b6258 | 11,398 B | A | view · diff |
| git:20261008.da5e9a9 | 2026-10-08 | da5e9a9 | 11,287 B | A | view · diff |
| git:20261008.dbfc5a5 | 2026-10-08 | dbfc5a5 | 10,107 B | A | view · diff |
| git:20261008.8f80086 | 2026-10-08 | 8f80086 | 10,406 B | A | view · diff |
| git:20261008.4fa8a73 | 2026-10-08 | 4fa8a73 | 10,308 B | A | view · diff |
| git:20261007.680a210 | 2026-10-07 | 680a210 | 9,774 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/rigs/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 (41858 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
mvschwarz/openrig · 8,889 stars · license Apache-2.0 · pushed 2026-11-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_guq4rmxhqv4fj46k GET https://markdownregistry.com/api/v1/resolve?ref=mvschwarz/openrig/rigs GET https://markdownregistry.com/api/v1/blob/c2849d02b022f01742926ef1fae3400c37e57ece734ea3cb495444d0f4dcdaa7
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 mvschwarz/openrig
Every file in mvschwarz/openrig