applying-a-permission-policy SKILL.md skillA
applying-a-permission-policy from mvschwarz/openrig is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add mvschwarz/openrig/applying-a-permission-policy@git:20261006.141513ePins git:20261006.141513e in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- mvschwarz/openrig
- Path
packages/daemon/assets/plugins/openrig-core/skills/applying-a-permission-policy/SKILL.md- Versions recorded
- 8
- Latest version
- git:20261006.141513e, committed Oct 6, 2026
- First version recorded
- Aug 5, 2026
- Size
- 14,021 bytes
- Repository stars
- 8,889
- License
- Apache-2.0
Use before launching a team during agent-guided setup, or when a user asks to configure OpenRig command permissions, reduce repeated native approval prompts, or apply a selected rig/seat permission policy.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 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 …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_z5yqi7pa244lu4ma/f7bba8d50b10fc8715f40a57bf82677ca9388c6718c8a162833d9c6daf2afdca.json
Then /plugin install applying-a-permission-policy@markdownregistry-z5yqi7pa244lu4ma in Claude Code. It installs git:20261006.141513e, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add mvschwarz/openrig/applying-a-permission-policy@sha256:f7bba8d50b10fc87The line at the top of this page pins the label git:20261006.141513e, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_z5yqi7pa244lu4ma)
4 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in mvschwarz/openrig/applying-a-permission-policy since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of applying-a-permission-policy from somewhere else? Ask it: where did my applying-a-permission-policy come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 8 versions of this file, between Aug 5, 2026 and Oct 6, 2026, about one every 9 days. Its first recorded version is graded B and its latest A.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261006.141513e latest | 2026-10-06 | 141513e | 14,021 B | A | view · diff |
| git:20261006.2bbe82a | 2026-10-06 | 2bbe82a | 13,540 B | A | view · diff |
| git:20260929.aa7bc44 | 2026-09-29 | aa7bc44 | 12,539 B | A | view · diff |
| git:20260925.efde04f | 2026-09-25 | efde04f | 9,056 B | A | view · diff |
| git:20260925.681b5c1 | 2026-09-25 | 681b5c1 | 7,623 B | A | view · diff |
| git:20260907.3949b26 | 2026-09-07 | 3949b26 | 18,720 B | B | view · diff |
| git:20260830.80d5290 | 2026-08-30 | 80d5290 | 20,804 B | B | view · diff |
| git:20260805.864cea6 | 2026-08-05 | 864cea6 | 20,959 B | B | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/applying-a-permission-policy/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (14021 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
mvschwarz/openrig · 8,889 stars · license Apache-2.0 · pushed 2026-11-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_z5yqi7pa244lu4ma GET https://markdownregistry.com/api/v1/resolve?ref=mvschwarz/openrig/applying-a-permission-policy GET https://markdownregistry.com/api/v1/blob/f7bba8d50b10fc8715f40a57bf82677ca9388c6718c8a162833d9c6daf2afdca
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.