agent-starters skillA
agent-starters is agent-read markdown (skill) from mvschwarz/openrig: 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..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns 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
mdr add mvschwarz/openrig/agent-starters@git:20260907.9006fc5mdr add mvschwarz/openrig/agent-starters@sha256:66cbaa251b05cde6Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_m26wi3uu6kzkwyas)
0 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260907.9006fc5 latest | 2026-09-07 | 9006fc5 | 7,052 B | A | view · diff |
| git:20260802.4c6d888 | 2026-08-02 | 4c6d888 | 6,470 B | A | view |
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 (7052 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 · 362 stars · license Apache-2.0 · pushed 2026-09-25 · 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/66cbaa251b05cde6a09f51b08c70ea78c6c4f75ae5db0f95baa15b8255714a1d
Your agent 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.