provenance SKILL.md skillA
provenance from zhiming-dev/roster is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add zhiming-dev/roster/provenance@git:20260607.cffeb43Pins git:20260607.cffeb43 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- zhiming-dev/roster
- Path
shared/provenance/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260607.cffeb43, committed Jun 7, 2026
- First version recorded
- Jun 7, 2026
- Size
- 5,511 bytes
- Repository stars
- 12
- License
- MIT
Append a structured event to the run's provenance log. Every agent calls this for every meaningful state transition (plan drafted, task dispatched, action proposed/executed, approval decided, etc.) so the run is fully replayable and auditable.
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
# Provenance Skill The provenance log is the **backbone of auditability and the research harness.** A run is defined by its log: anything not in the log effectively did not happen as far as Roster is concerned. ## File layout ``` runs/<runId>/ ├── goal.md ← principal's original instruction ├── plan.draft.json ← planner output, pre-ratification ├── plan.ratified.json ← post-approval, the dispatch source of truth ├── provenance.jsonl ← append-only event log (THIS FILE) ├── messages/<msg-id>.json ← every AgentMessage referenced from the log ├── proposals/<prop-id>.json← every ActionProposal referenced from the log ├── results/<task-id>.json ← every TaskResult referenced from the log └── artifacts/ ← outputs (diffs, test reports, screenshots, docs) ``` ## Procedure ### Step 1 — Build the event Construct an object that validates against [`shared/schemas/provenance-event.schema.json`](../schemas/provenance-event.schema.json). Required: `id`, `runId`, `t`, `kind`, `actor`. - Generate `id` as `evt_<13-char-base32>` (sortable and unique within a run). - `t` is ISO-8601 UTC (`new Date().toISOString()`). …
Read the whole file at its exact version.
How to install
mdr add zhiming-dev/roster/provenance@sha256:285408fe656d3a06The line at the top of this page pins the label git:20260607.cffeb43, 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_oewj3rc2xhsm4d3y)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, all committed on Jun 7, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260607.cffeb43 latest | 2026-06-07 | cffeb43 | 5,511 B | A | view · diff |
| git:20260607.31b1c63 | 2026-06-07 | 31b1c63 | 5,513 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 (5511 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
zhiming-dev/roster · 12 stars · license MIT · pushed 2026-10-12 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_oewj3rc2xhsm4d3y GET https://markdownregistry.com/api/v1/resolve?ref=zhiming-dev/roster/provenance GET https://markdownregistry.com/api/v1/blob/285408fe656d3a06c7132b8c89a3faf5f6a763c3e0bc2121e572ec49ae281e03
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 zhiming-dev/roster
Every file in zhiming-dev/roster