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 development-teamgit 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/development-team)<a href="https://agentmods.dev/skills/mvschwarz/openrig/development-team"><img src="https://agentmods.dev/badge/skills/mvschwarz/openrig/development-team/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/development-team"><img src="https://agentmods.dev/badge/skills/mvschwarz/openrig/development-team.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00020 | $0.00582 |
| Opus 5.5 | $0.00008 | $0.00233 |
| Sonnet 5.5 | $0.00004 | $0.00116 |
| Haiku 4.5 | $0.00002 | $0.00058 |
Grade A, and why
development-team 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 1mo 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Development Team
The pod turns the assigned user outcome into working software. Builders, QA and designers are capabilities; neighboring roles may be held by one seat unless independence was explicitly selected.
Start from the work
Run rig whoami --json, then resolve project.yaml -> mission.yaml -> active slice.yaml -> selected component or wave map -> addressed context. The complete
lookup and precedence rule is docs/reference/product-journey-sdlc.md#resolve-the-selected-path
(installed: $OPENRIG_HOME/reference/product-journey-sdlc.md#resolve-the-selected-path).
Read the selected addresses and source needed for this task; skills available in
your profile are capabilities, not a mandatory reading list. No composition means
light Part A. Role names and idle seats add no gates. Explicit rigor and authored
wave boundaries retain their named checks.
Build and verify
Clarify consequential uncertainty, inspect the existing seam, then complete one coherent outcome. Reproduce a defect before repairing it; use tests that distinguish the failure and verify through the public surface. Keep chunks as large as the outcome and file territory permit. TDD is a feedback loop, not a two-seat protocol.
The builder reports the exact candidate, changed behavior, commands and observed results, with remaining uncertainty. No universal pre-edit proposal, QA approval or post-edit gate is implied. When one is explicitly selected, honor its boundary and send the relevant evidence directly to its owner.
QA and design
QA compares the delivered behavior with the actual contract. Read the diff and exercise the result; avoid tests that merely repeat the implementation. On a tiny change the builder may hold QA. Independent QA excludes the author when selected. A wave receives independent review at its authored boundary, not per slice.
Design clarifies user flows and ambiguous behavior when the outcome needs it. Browser and dogfood skills load for a relevant UI journey, not every task. During assigned dogfood, fix-and-retest only within the granted scope; a read-only assignment stays read-only. If a tester becomes an author, preserve that attribution when independent evaluation is required.
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.
- 1mo ago Changed · -99 lines · +2 tokens per session 3d712a94a172
- 1mo ago First seen · 157 lines · 18 tokens per session scan A 5baee21f46d2
development-team is a skill published in the GitHub repository mvschwarz/openrig (7,999 stars, last pushed today), licensed Apache-2.0. It adds 20 tokens to every session and 582 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
create-issue
Draft and submit a GitHub issue from a user idea or bug description, with bilingual body and correct labels.
gh-file-issue
Use when filing a new Codewhale GitHub issue: turn a bug or idea into a well-formed, actionable issue with repro, acceptance criteria, labels, and milestone.
gh-treasure-hunt
Hunt the issue/PR queue for highest value-over-risk wins: clean focused community PRs, already-implemented issues to close, safe quick-fixes.
gh-assign-issues
Use to assign GitHub issues to a milestone and/or owners in bulk, verifying each.
swarm-plan
Full execution protocol for MODE: PLAN -- plan creation, external plan ingestion, QA gate persistence, task granularity, and traceability checks.
client-onboarding
Use when a deal closed or a user signed up and the first 30 days need an activation plan: sales→delivery handoff, one verifiable activation event, kickoff, and a 30/60/90 or day-0→14 plan with owners, dates and a measurable exit. NOT reactive ticket triage (that is customer-support), NOT renewals/churn past the…