verification-receipts SKILL.md skillA
verification-receipts from swcstudiospace/pumpgrok is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add swcstudiospace/pumpgrok/verification-receipts@git:20261023.ef2f2f6Pins git:20261023.ef2f2f6 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- swcstudiospace/pumpgrok
- Path
skills/verification-receipts/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261023.ef2f2f6, committed Oct 23, 2026
- Size
- 2,653 bytes
- Repository stars
- 42
- License
- AGPL-3.0
Attach a ledger-backed receipt to every completion claim so no Bot asserts success without proof the desk can re-check.
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
# Verification Receipts
## L1 - Summary
No completion claim without a receipt. Every Bot that reports work done attaches a receipt the desk can re-check with `desk.receipt_check`: what was claimed, which ledger rows prove it, and who approved it. An unreceipted claim is an unmade claim.
```
claim made -> receipt attached (desk.receipt_check exit 0) -> CHIEF accepts
claim made -> no receipt -> CHIEF rejects, work repeats
```
## L2 - Method
1. S1 - State the claim narrowly: ticket id, action taken, and the ledger event types that prove it (`OrderPlaced`, `FillRecorded`, `JournalNote`). Vague claims ("looks good") are not claims.
2. S2 - Query the proof with `desk.receipt_check`: pass the ticket id and the expected event kinds. The tool returns PASS only when the ledger holds matching rows; otherwise it names what is missing.
3. S3 - Record the approval: every receipt names `approved_by` (a seat for autonomous steps, `human:<id>` for human-gated steps per G-2). Self-approval is void.
4. S4 - Chain the receipt: the receipt for step N references the receipt for step N-1, so a broken chain points at the exact step that lost its proof.
…Read the whole file at its exact version.
How to install
mdr add swcstudiospace/pumpgrok/verification-receipts@sha256:98b3a931cc61409dThe line at the top of this page pins the label git:20261023.ef2f2f6, 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_whyfeb47ggt67mzh)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 23, 2026.
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 (2653 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
swcstudiospace/pumpgrok · 42 stars · license AGPL-3.0 · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_whyfeb47ggt67mzh GET https://markdownregistry.com/api/v1/resolve?ref=swcstudiospace/pumpgrok/verification-receipts GET https://markdownregistry.com/api/v1/blob/98b3a931cc61409df8710263020e3fc58aece7debf9a107a56dba4828cf06d78
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.