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-skillsgit 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-skills)<a href="https://agentmods.dev/skills/mvschwarz/openrig/openrig-skills"><img src="https://agentmods.dev/badge/skills/mvschwarz/openrig/openrig-skills/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-skills"><img src="https://agentmods.dev/badge/skills/mvschwarz/openrig/openrig-skills.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.00109 | $0.02412 |
| Opus 5.5 | $0.00044 | $0.00965 |
| Sonnet 5.5 | $0.00022 | $0.00482 |
| Haiku 4.5 | $0.00011 | $0.00241 |
Grade A, and why
openrig-skills 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 yesterday.
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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenRig skills — the index (start here)
You're running inside OpenRig. OpenRig ships a set of skills — small documents that tell you when to do something and how. This file is the map: what ships, when to reach for each, and how to load it. If you don't know which skill applies, or nothing is projected into your context, start here.
How OpenRig context works (30 seconds)
Skills are progressive disclosure: a skill's name + description sit in your context ambiently (the "hot tier"); its body loads only when you open it. So you don't pre-read everything — you pattern-match a skill's "when" to your moment, then open just that one. This file recommends skills from the shipped set. (For bounded procedures, open agent-operated-workflows; for ongoing agent-backed applications, open agent-operated-software.)
Every row below names how to reach the skill — already-hot, or an exact load path. No row is a dead end.
Loading an entry on demand — rig context get
Don't guess a file path or a name. Go ask → ref → load in three steps:
- Discover — run
rig context listfor every shipped entry's ref and name. The when for each is the index below (orrig context list --json, which carries each entry's purpose) — match your moment there. - Select — match your moment to a row's when and take its ref. Refs are canonical full paths
that mirror the library layout —
skills/<namespace>/<name>(e.g.skills/core/rig-lifecycle,skills/process/systematic-debugging). A unique bare name (e.g.watchdog) also resolves; any slash-bearing ref is an exact lookup and fails loud if it does not exist. - Load —
rig context get skills/<namespace>/<name>:
rig context get skills/core/rig-lifecycle
The router itself is available through both forms it teaches:
rig context get openrig-skills and rig context get skills/core/openrig-skills.
The content is served from the installed CLI, so what you load always matches your running version —
no path-guessing, no frozen-fork drift. (The daemon assembles the same bundle rig context preview
shows an operator — get is the agent-facing pull.)
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.
- yesterday Changed bdd6594ae110
- 4d ago Changed c30ca27054b4
- 10d ago Changed · +30 tokens per session ed2de7fe238d
- 15d ago Changed c3de569b72ff
- 16d ago Changed · -1 lines 3a55d25cacae
- 21d ago Changed · +7 lines e5f47e24a4c3
- 23d ago Changed · +7 lines fee88b59cf45
- 27d ago Changed · +1 lines 15b084e35264
- 1mo ago Changed · +2 lines af08e74804de
- 1mo ago First seen · 116 lines · 79 tokens per session scan A f606f2e50085
openrig-skills is a skill published in the GitHub repository mvschwarz/openrig (8,096 stars, last pushed today), licensed Apache-2.0. It adds 109 tokens to every session and 2,412 once invoked, about $0.0004 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
codegraph
Analyze indexed codebases via graph database (neug) and vector index (zvec). Covers call graphs, dependencies, dead code, hotspots, module coupling, architecture reports, semantic search, impact analysis, bug root cause from GitHub issues, class diagrams (UML), and PR review (risk scoring, conflict detection…
stuck
Diagnose frozen, stuck, or slow Qwen Code sessions on this machine. Scans for problematic processes, high CPU/memory usage, hung subprocesses, and debug logs. Use /stuck or /stuck to focus on a specific process.
structured-debugging
Hypothesis-driven debugging methodology for hard bugs. Use this skill whenever you're investigating non-trivial bugs, unexpected behavior, flaky tests, or tracing issues through complex systems. Activate proactively when debugging requires more than a quick glance — especially when the first attempt at a fix didn't…
memory-leak-debug
Diagnose memory leaks in the Qwen Code CLI using heap snapshots and the chrome-devtools CLI. Use when investigating high memory usage, unbounded growth, or suspected object retention issues.
bugfix
Fix a bug from a GitHub issue, following the reproduce-first workflow. Use when the user asks to fix a bug, investigate a GitHub issue, or debug a user-reported problem. Takes a GitHub issue URL or number as input.
test-failure-explorer
Import and query an existing Vitest 3.2 JSON report to explore test failures, file-level errors and original diagnostic evidence.