run-history skillA
run-history is agent-read markdown (skill) from runxhq/runx: Read Runx's native receipt history and skill catalog, then return deterministic run outcomes, catalog test coverage, and governance follow-ups without model-authored metrics..
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
# Run History Read the local Runx ledger through the native `receipt.query` service and the installed catalog through `runx.skill.inspect`. The runner computes the report itself; it does not ask an agent to invent commands, launch subprocesses, or transcribe counts. Use it for operational questions about recent Runx activity, failed or blocked runs, pending runs, frequently used receipt subjects, and skill entries without fixtures or inline harness cases. Use `audit-receipt` or `diagnose-skill-run` to inspect one suspicious run, and `least-privilege` when receipt-backed authority usage is available for grant attenuation. ## Evidence boundary - Live execution reads only the native receipt and catalog projections. These services share the same store resolution, signature policy, and catalog parser as the Runx CLI without routing back through the CLI as a subprocess. - History reads are bounded to 1,000 rows by default and 10,000 at most. - `history_receipts`, `pending_runs`, and `catalog_items` are replay inputs for harnesses and controlled analysis. `history_receipts` and `catalog_items` must be supplied together; replay never silently mixes caller data with live …
Read the whole file at its exact version.
How to install
mdr add runxhq/runx/run-history@git:20260808.8b7af2amdr add runxhq/runx/run-history@sha256:cf8e8732664dddcePin 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_vbfowro525voynqd)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260808.8b7af2a latest | 2026-08-08 | 8b7af2a | 2,455 B | A | view · diff |
| git:20260723.6e5370b | 2026-07-23 | 6e5370b | 2,447 B | A | view · diff |
| git:20260716.fe90232 | 2026-07-16 | fe90232 | 2,139 B | A | view · diff |
| git:20260715.8644be9 | 2026-07-15 | 8644be9 | 4,574 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 (2455 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
runxhq/runx · 93 stars · license Apache-2.0 · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_vbfowro525voynqd GET https://markdownregistry.com/api/v1/resolve?ref=runxhq/runx/run-history GET https://markdownregistry.com/api/v1/blob/cf8e8732664dddce70f2f5aebf34bed987e497c0bf400ece72b9dd619867ef2f
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.