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 applying-a-permission-policygit 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/applying-a-permission-policy)<a href="https://agentmods.dev/skills/mvschwarz/openrig/applying-a-permission-policy"><img src="https://agentmods.dev/badge/skills/mvschwarz/openrig/applying-a-permission-policy/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/applying-a-permission-policy"><img src="https://agentmods.dev/badge/skills/mvschwarz/openrig/applying-a-permission-policy.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.00046 | $0.02924 |
| Opus 5.5 | $0.00018 | $0.01170 |
| Sonnet 5.5 | $0.00009 | $0.00585 |
| Haiku 4.5 | $0.00005 | $0.00292 |
Grade A, and why
applying-a-permission-policy 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 19d 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 — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Applying a permission policy
Configure the user's chosen permissions in the harness that runs the agent. OpenRig operating posture, native command rules, sandbox access and launch flags are separate controls. A command rule grants execution capability, not authority to invent tasks, publish work or change another host.
Ask once before team launch
Reuse an existing explicit choice for these harnesses and this scope from the user's onboarding context; do not ask again. Existing rules are configuration, not evidence of consent to expand their scope. Preserve them without expansion.
For a team with no explicit policy, recommend keeping the team default. Claude
already allows ordinary rig commands, project reads and common tests, while
lifecycle commands ask. Codex already has writable workspace and pod state;
its on-request policy does not guarantee lifecycle prompts. Explicit
policies, seat choices and named Codex profiles keep their existing meaning.
Native restrictions can still prompt for installs, commits, other shell
commands and writes outside writable roots. With the Claude team default, an
allow does not override lifecycle ask rules: rig up, rig down and the other listed
lifecycle commands still ask even after Yes. Do not promise prompt-free operation.
Only offer additional persistent allowances when wanted, for the selected project or explicitly user-wide scope, or to adjust an explicit seat policy:
Remember these selected OpenRig commands in your native settings for this project? This is separate from the team launch default; stricter rules and Claude lifecycle asks remain. Yes / No — keep the team default
- Yes: require an affirmative answer, then apply the procedure below only at the agreed scope. Do not replace ask/deny rules or substitute user-wide settings when project rules are unsupported.
- No / no answer: leave settings and any existing explicit choice unchanged.
With no policy selected, keep it unset; never record
noneto mean keeping the team default. Do not repeat the question during this setup.
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.
- 19d ago Changed · +20 lines f7bba8d50b10
- 26d ago Changed · +53 lines · +9 tokens per session e8dbd8eec758
- 1mo ago Changed · +51 lines · -74 tokens per session scan D → A 3b76dcc08954
- 1mo ago Changed · -3 lines fa4eaa920a4f
- 1mo ago First seen · 121 lines · 111 tokens per session scan D 7fde2a1220ba
applying-a-permission-policy is a skill published in the GitHub repository mvschwarz/openrig (8,192 stars, last pushed today), licensed Apache-2.0. It adds 46 tokens to every session and 2,924 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-08-30.
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.
interview
Ask one useful structured question at a time only when material product/implementation choices are genuinely missing; remember answers and produce a brief/spec. Discoverable facts should be investigated instead of asked.
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…