scout-verify SKILL.md skillA
scout-verify from confighub/cub-scout is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add confighub/cub-scout/scout-verify@git:20260926.4c4b67cPins git:20260926.4c4b67c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- confighub/cub-scout
- Path
skills/scout-verify/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260926.4c4b67c, committed Sep 26, 2026
- First version recorded
- May 25, 2026
- Size
- 20,070 bytes
- Repository stars
- 14
- License
- MIT
Use when the user wants a TYPED, FINGERPRINTED, IMMUTABLE evidence artifact about a Kubernetes resource — the Verify verb group of cub-scout (the receipt capability shipped in #446). Natural phrasing: "produce a receipt that this is in compliance", "give me an attestation that the cluster matches Git", "I need a verifiable record for the audit trail", "build a receipt verifying no manual edits since deploy", "verify deploy/api against source-truth and save the artifact…
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
# scout-verify The Verify verb group of cub-scout. Produces typed, fingerprinted, immutable evidence artifacts — **receipts** — wrapping cub-scout's existing field-level evidence into a verifiable record CI/CD gates, audit trails, postmortems, and acceptance-judge tooling can attach to a decision and later re-check for tampering. > A **receipt** is a stamped, hand-offable record of one verification: an in-toto Statement v1 envelope around a verdict, evidence, omissions, and optional upstream receipt references. Its **proof** is the verifiable integrity property created by the fingerprint: SHA-256 over RFC 8785 canonical JSON of the full Statement, with only `predicate.fingerprint` removed before hashing. Any third party can recompute that fingerprint to confirm the receipt has not been edited since it was stamped. That is tamper-evidence, not producer authentication or formal proof of truth. A receipt without proof is a claim; a receipt with proof is evidence. Receipts are HISTORICAL records. Updates produce new receipts; old ones never mutate. ## When to use Explicit phrasings: - "Produce a receipt that deploy/api is in compliance" …
Read the whole file at its exact version.
How to install
mdr add confighub/cub-scout/scout-verify@sha256:2df9bcbd6e378876The line at the top of this page pins the label git:20260926.4c4b67c, 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_ggth632t5u2uzs5v)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between May 25, 2026 and Sep 26, 2026, about one every 31 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260926.4c4b67c latest | 2026-09-26 | 4c4b67c | 20,070 B | A | view · diff |
| git:20260910.abf56b4 | 2026-09-10 | abf56b4 | 19,872 B | A | view · diff |
| git:20260910.d56245f | 2026-09-10 | d56245f | 19,756 B | A | view · diff |
| git:20260910.e36f2e2 | 2026-09-10 | e36f2e2 | 19,205 B | A | view · diff |
| git:20260525.26dd797 | 2026-05-25 | 26dd797 | 19,638 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 (20070 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
confighub/cub-scout · 14 stars · license MIT · pushed 2026-10-11 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ggth632t5u2uzs5v GET https://markdownregistry.com/api/v1/resolve?ref=confighub/cub-scout/scout-verify GET https://markdownregistry.com/api/v1/blob/2df9bcbd6e37887601f8cbb16d1e5e2bdff91263a01b82a693261e22196646af
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.