OpenRig is a software harness that coordinates Claude Code and Codex coding agents as one system, with agent teams defined in YAML and launched together. It is for organizing persistent teams of coding agents that can delegate work to specialists and return results or decisions. The catalogue lists 53 skills and one plugin as add-ons for OpenRig.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add mvschwarz/openrig --skill developing-openriggit clone --depth 1 https://github.com/mvschwarz/openrigWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/mvschwarz/openrig/developing-openrig)<a href="https://agentmods.dev/skills/mvschwarz/openrig/developing-openrig"><img src="https://agentmods.dev/badge/skills/mvschwarz/openrig/developing-openrig/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/mvschwarz/openrig/developing-openrig"><img src="https://agentmods.dev/badge/skills/mvschwarz/openrig/developing-openrig.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00084 | $0.01364 |
| Opus 5.5 | $0.00034 | $0.00546 |
| Sonnet 5.5 | $0.00017 | $0.00273 |
| Haiku 4.5 | $0.00008 | $0.00136 |
Grade A, and why
developing-openrig scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Developing OpenRig
This skill is a map to the other maps. Each one is incomplete and may be stale: where a map and the code disagree, the code is right, and fixing the map is a welcome contribution.
First: which OpenRig are you in?
If you are an agent running inside OpenRig, two different OpenRigs are in play:
- The installed one runs your session.
rig --versionandrig daemon statusdescribe it. - The checkout is what you're changing.
git rev-parse HEADdescribes it.
Restarting the installed daemon does not run your checkout, and stopping it stops the agents running on it, including you. Test your change with the repo's own harnesses, which start a private daemon and tmux server (see "Test it" below), not by restarting the daemon you live in.
Find your way
| You want to know | Read | How much to trust it |
|---|---|---|
| What OpenRig can already do, before you decide something is missing | rig context get onboarding-width/public-what-you-can-do.md; in this checkout, packages/daemon/context-packs-src/onboarding-width/public-what-you-can-do.md (the installed copy can differ) |
The capability map; check it before proposing a new command or calling a gap a defect |
Whether a rig command already exists |
rig --help: the full command list, before you decide a command is missing |
The running binary; read the whole list, not only the command you expected |
| Whether a problem is already known | The "Known problems to compare against" section of docs/reference/help.md |
Lists known issues by symptom; check an issue's current status before relying on it |
| Whether a feature is already planned | ROADMAP.md |
Check it before proposing a feature |
| How the packages fit, the request path, where to add a command, route, migration, adapter, skill, context pack or scenario | ARCHITECTURE.md |
Checked against the commit it names; counts come with the command to refresh them |
| Whether your change touches a high-risk area, what depends on it, what broke there before | docs/as-built/arteries.md |
Incomplete by design: absence from it doesn't make a change safe |
| What to run before you push, and what each layer can and can't prove | docs/as-built/test-layers.md |
Checked against the commit it names |
The exact behaviour of a rig command |
rig <command> --help on the running binary, then packages/cli/src/commands/ |
The binary and the code win over any document |
| A subsystem in depth | docs/as-built/ |
Each module names the commit it was last checked against in last-verified-against-source; compare that marker with git log before relying on it |
| Rig spec, agent spec and other user-facing reference | docs/reference/ |
Ships to every user; if you find drift, fix it there |
| Which shipped skill covers a task | skills/_canonical/core/openrig-skills/SKILL.md |
The index of the skills that ship with OpenRig |
| How to open a good pull request, and what review looks like | CONTRIBUTING.md |
Current |
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 5d ago Changed · +7 lines fba6335a4e09
- 6d ago Changed · +2 lines 2d30abc5d609
- 10d ago First seen · 67 lines · 84 tokens per session scan A c59017278389
developing-openrig is a skill published in the GitHub repository mvschwarz/openrig (6,984 stars, last pushed today), licensed Apache-2.0. It adds 84 tokens to every session and 1,364 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-02.
Other skills, from other repositories
test-failure-explorer
Import and query an existing Vitest 3.2 JSON report to explore test failures, file-level errors and original diagnostic evidence.
confirm-failures-are-causally-linked-to-the-task-before-reportin
When delegating a task affected by this skill, include.
isolate-the-specific-failure-mode-before-proposing-a-fix
When delegating a task affected by this skill, include.
debug
Use when something is broken — a failing or flaky test, crash, wrong result or regression — and the root cause must be reproduced and proven before any fix. On-demand; callable mid-implement. NOT a feature to spec or build (that is specify/implement), NOT the lint/test gate (that is verify), NOT adversarial diff…
qa-sweep
Codex adapter for independent QA review of opencode-swarm changes. Use after implementation or debugging when the user asks for a QA sweep, regression check, review pass, quality gate, or confidence check before publishing.
reqforge-greenkeeper
name: reqforge-greenkeeper description: Used when maintaining the ReqForge repository itself and its release gates fail — pnpm test, pnpm forge-smoke, pnpm sync:discover, adapter drift, skill fixtures, loadouts, or test-demo golden path. Restores a green, synced state with minimal changes. Not for bugs in user apps…