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 openrig-software-factorygit 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/openrig-software-factory)<a href="https://agentmods.dev/skills/mvschwarz/openrig/openrig-software-factory"><img src="https://agentmods.dev/badge/skills/mvschwarz/openrig/openrig-software-factory/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/openrig-software-factory"><img src="https://agentmods.dev/badge/skills/mvschwarz/openrig/openrig-software-factory.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.00041 | $0.02206 |
| Opus 5.5 | $0.00016 | $0.00882 |
| Sonnet 5.5 | $0.00008 | $0.00441 |
| Haiku 4.5 | $0.00004 | $0.00221 |
Grade A, and why
openrig-software-factory 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 9d 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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenRig Software Factory
Start with a useful repository outcome and add coordination when it earns its cost. A beginner can complete reviewed work without Workflow. These are choices using existing capabilities, not stages everyone must graduate through.
Choose how the team works
| Need | Start here | Add more when… |
|---|---|---|
| One change, close human guidance | Manual/team work: give an owner the outcome, use repository instructions, implement and obtain the chosen independent check. | Work must survive turns or move between seats. |
| Continuing work with visible ownership | Queue-supported orchestration: use rig queue create, claim work, then rig queue handoff with the candidate/evidence to the next owner. Record real blockers and the continuation. No Workflow instance is needed. |
Repeated steps need an explicit dependency graph and permitted exits. |
| An explicit execution contract | Workflow: inspect rig workflow compile, then deliberately use rig workflow instantiate-lifecycle. Advance its packets through the workflow projection mechanism. |
The actual project needs reusable profiles, additional roles or gates. |
For the concrete queue loop, wake behavior and optional two-slice Workflow,
read references/worked-example.md. Installed copy:
rig context get skills/core/openrig-software-factory/references/worked-example.md.
A roadmap, YAML file or wake does not execute work or authorize a new outcome.
Choose the first team and its providers
Ask what the user wants to build and which working account(s) they have: Claude
Code, Codex, or both. Recommend one of three teams: starter (a Claude builder
and a Codex reviewer, for one bounded change), workshop (a lead, a builder, QA
and a reviewer; a rig bundle installed from its pinned listing) or factory (seven
agents for sustained product work). When the user lacks a provider a team needs,
write an adapted copy of the team under the same name, as the kernel operator's
guidance describes; never offer per-provider variants. first-project is
starter's old name. Check only the CLIs/logins the team needs; request claude auth login
or codex login once when that selected login is missing. No credential copying,
unused provider prerequisite or silent model/provider fallback.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago Changed · +7 lines 530490b70246
- 10d ago Changed · +3 lines 647f0537d794
- 17d ago Changed · +31 lines 33930e723416
- 21d ago First seen · 139 lines · 41 tokens per session scan A ecf4597abb7c
openrig-software-factory is a skill published in the GitHub repository mvschwarz/openrig (7,545 stars, last pushed yesterday), licensed Apache-2.0. It adds 41 tokens to every session and 2,206 once invoked, about $0.0002 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-09-26.
Other skills, from other repositories
metis
A task-routing and checking workflow for explicitly requested Metis work. It assigns work to defined roles, records checks, and limits recovery when something fails.
metis-browser
Control Metis Desktop Inspector built-in browser for local preview (HTML/SVG/file paths), page interaction, accessibility snapshots, and screenshots. Use when the user asks to open, show, preview, inspect, click, type, or verify UI in the in-app/built-in browser. Prefer browsernavigate over bash…
dynamic-resources
Example skill loaded from resourcesdiscover.
browser-use
Control the user's Chrome through the existing persistent Node REPL and the Qwen Browser SDK.
verify
Exercise the real app/API/CLI and collect observable evidence; tests alone do not count as end-to-end verification.
swarm-pr-review
Run a graph-guided, tool-augmented PR review using context packing, parallel exploration, mandatory repository-agnostic risk-family coverage with dispatch scaled to diff size and risk, independent reviewer validation, critic challenge, and metrics writeback. Use for deep pull request review with low false-positive…