agent-starters SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
agent-starters 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/agent-starters@git:20261004.89dc45ePins git:20261004.89dc45e 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/specs/agents/shared/skills/core/agent-starters/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261004.89dc45e, committed Oct 4, 2026
- First version recorded
- Aug 2, 2026
- Size
- 6,787 bytes
- Repository stars
- 8,889
- License
- Apache-2.0
Use when creating, refreshing, packaging, inspecting, promoting, or deprecating a named per-seat starting point — Agent Starter manifest authoring, the 6-state lifecycle (captured → named → inspectable → used → promoted → deprecated), provenance honesty, and refusal rules. NOT a VM image; a managed starting point composed from agent role + startup context + optional native session source + provenance.
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
# Agent Starters A named, reusable per-seat starting point. Composes an agent role, startup context, optional native session source, and provenance into something a user or rig can choose when creating, refreshing, or packaging a seat. This registry-backed startup context is distinct from the `rig agent-image` surface and from a VM image. See the current behavior below before treating optional session provenance as an executable native session source. ## Use this when - Creating a new seat from a known-good starting context. - Refreshing a seat with `rig expand` and `starter_ref`. - Authoring a new starter (registry entry). - Inspecting an existing starter's provenance, freshness, or recommended status. - Promoting / deprecating starters in the registry. - Composing a starter with a Composable Priming Pack (record manifest id/version, runtime, source session id or transcript path, ready-check evidence, freshness state). ## Don't use this when - You want VM-style deterministic state capture. Starters don't capture VM state. - You want to copy provider auth material into a starter. **Starters refer to session sources and context; they do NOT copy credentials.** …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_m26wi3uu6kzkwyas/8e8961f44fccb812f39e01174a331dab24f153ceaba91925f1e42371836cdec0.json
Then /plugin install agent-starters@markdownregistry-m26wi3uu6kzkwyas in Claude Code. It installs git:20261004.89dc45e, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add mvschwarz/openrig/agent-starters@sha256:8e8961f44fccb812The line at the top of this page pins the label git:20261004.89dc45e, 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_m26wi3uu6kzkwyas)
5 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/agent-starters 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 agent-starters from somewhere else? Ask it: where did my agent-starters 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 3 versions of this file, between Aug 2, 2026 and Oct 4, 2026, about one every 31 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261004.89dc45e latest | 2026-10-04 | 89dc45e | 6,787 B | A | view · diff |
| git:20260907.9006fc5 | 2026-09-07 | 9006fc5 | 7,052 B | A | view · diff |
| git:20260802.4c6d888 | 2026-08-02 | 4c6d888 | 6,470 B | A | 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/agent-starters/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 (6787 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_m26wi3uu6kzkwyas GET https://markdownregistry.com/api/v1/resolve?ref=mvschwarz/openrig/agent-starters GET https://markdownregistry.com/api/v1/blob/8e8961f44fccb812f39e01174a331dab24f153ceaba91925f1e42371836cdec0
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.
More from mvschwarz/openrig
Every file in mvschwarz/openrig