cad-verifier-contract SKILL.md skillA
cad-verifier-contract from crenshawdev/cadence is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add crenshawdev/cadence/cad-verifier-contract@git:20261103.1c353cePins git:20261103.1c353ce in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- crenshawdev/cadence
- Path
skills/cad-verifier-contract/SKILL.md- Versions recorded
- 10
- Latest version
- git:20261103.1c353ce, committed Nov 3, 2026
- First version recorded
- Aug 14, 2026
- Size
- 12,052 bytes
- Repository stars
- 8
- License
- MIT
Role contract preloaded at spawn by the cad-verifier, cad-verifier-low, cad-verifier-medium, cad-verifier-xhigh and cad-verifier-max agents. Not for direct use: do not invoke it from a conversation.
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
<role> A completed phase is submitted for goal-backward verification: start from what the phase promised, verify it actually exists, is wired, and behaves in the codebase. SUMMARY.md documents what was SAID to be done; you verify what IS. These often differ. You are dispatched by cad-verify (spawn-agent seam) with the phase number, goal, the current UAT items, and artifact paths. You write exactly ONE file - `.planning/phases/<N>/verifier-findings.json`, in a single `Write` call - and your final message is a digest plus that path. The orchestrator pipes that file straight into `uat merge`; nothing is transcribed by hand. </role> <stance> Assume the goal was NOT achieved until code evidence proves it. Completed tasks never prove a delivered goal on their own. How verifiers go soft - do none of these: - Trusting SUMMARY bullets without reading the files they describe. - Accepting "file exists" as "works" - a stub satisfies existence. - Marking UNCERTAIN when absence is observable - that is FAILED. - Letting early passes buy later truths less scrutiny. </stance> <core_principle> Task completion != goal achievement. "Create login handler" is complete …
Read the whole file at its exact version.
How to install
mdr add crenshawdev/cadence/cad-verifier-contract@sha256:94db1aea2a29fec8The line at the top of this page pins the label git:20261103.1c353ce, 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_cv22fzd42nnbthce)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 10 versions of this file, between Aug 14, 2026 and Nov 3, 2026, about one every 9 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261103.1c353ce latest | 2026-11-03 | 1c353ce | 12,052 B | A | view · diff |
| git:20261103.17a83e7 | 2026-11-03 | 17a83e7 | 11,112 B | A | view · diff |
| git:20261028.dd1f3d4 | 2026-10-28 | dd1f3d4 | 11,112 B | A | view · diff |
| git:20261027.9ef4f3a | 2026-10-27 | 9ef4f3a | 11,458 B | A | view · diff |
| git:20261005.a1a691d | 2026-10-05 | a1a691d | 11,247 B | A | view · diff |
| git:20260904.a4e118d | 2026-09-04 | a4e118d | 11,138 B | A | view · diff |
| git:20260904.1159847 | 2026-09-04 | 1159847 | 11,030 B | A | view · diff |
| git:20260825.049b26e | 2026-08-25 | 049b26e | 10,792 B | A | view · diff |
| git:20260824.ea21a2f | 2026-08-24 | ea21a2f | 10,792 B | A | view · diff |
| git:20260814.81bdb5d | 2026-08-14 | 81bdb5d | 10,805 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 (12052 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
crenshawdev/cadence · 8 stars · license MIT · pushed 2026-11-04 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_cv22fzd42nnbthce GET https://markdownregistry.com/api/v1/resolve?ref=crenshawdev/cadence/cad-verifier-contract GET https://markdownregistry.com/api/v1/blob/94db1aea2a29fec8089968d5dc2d924eef68cb2400e82923e473ae7bbb2fb27e
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.