sign-receipt skillA
sign-receipt is agent-read markdown (skill) from runxhq/runx: Bind an off-runtime action claim to opaque evidence references in a signed Runx receipt without pretending Runx verified the external action..
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
# Sign Receipt Record a bounded attestation about something that happened outside Runx so a later governed run can cite exactly what was claimed, by whom, on which evidence, and for what reliance scope. The native Runx receipt signature proves the attestation packet was sealed without later modification. It does **not** prove the external action itself happened. That distinction makes this skill useful without turning a signature into a fictional provider verifier. The actual proof remains in the referenced commit, provider object, approval record, transaction, or other evidence system. ## When to use it Use `sign-receipt` when an operator performed a legitimate off-runtime action and downstream automation needs a stable, auditable assertion about it. Examples include a manual console change, an externally approved decision, or a provider operation completed before a native adapter existed. Do not use it to launder an unsupported claim, copy raw evidence into a receipt, or replace a provider readback surface that Runx can actually call. If the external record is available through a governed reader, prefer that stronger evidence path. ## How it works …
Read the whole file at its exact version.
How to install
mdr add runxhq/runx/sign-receipt@git:20260723.6e5370bmdr add runxhq/runx/sign-receipt@sha256:512935aa95e2884fPin 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_63gafbuepd4g4qfj)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260723.6e5370b latest | 2026-07-23 | 6e5370b | 3,724 B | A | view · diff |
| git:20260715.8d8fc90 | 2026-07-15 | 8d8fc90 | 6,808 B | A | view · diff |
| git:20260715.8644be9 | 2026-07-15 | 8644be9 | 7,106 B | A | view · diff |
| git:20260615.3b0f02c | 2026-06-15 | 3b0f02c | 7,110 B | A | view · diff |
| git:20260614.b6a05c8 | 2026-06-14 | b6a05c8 | 6,742 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 (3724 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_63gafbuepd4g4qfj GET https://markdownregistry.com/api/v1/resolve?ref=runxhq/runx/sign-receipt GET https://markdownregistry.com/api/v1/blob/512935aa95e2884f7bf8e45b1ba0a8bc071b249f5ed296a81fe767023d0cfae3
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.