verify-contract SKILL.md skillA
verify-contract from tmusser/ai-engineering-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add tmusser/ai-engineering-skills/verify-contract@git:20261101.bfc03f8Pins git:20261101.bfc03f8 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- tmusser/ai-engineering-skills
- Path
skills/verify-contract/SKILL.md- Versions recorded
- 15
- Latest version
- git:20261101.bfc03f8, committed Nov 1, 2026
- First version recorded
- Jun 26, 2026
- Size
- 16,588 bytes
- Repository stars
- 6
- License
- MIT
Record clear evidence that a task works, including commands, results, remaining risks, scope adherence, and whether the implementation stayed under the spec ceiling.
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
# Verify Contract ## Purpose Prove the task actually works and leave durable evidence. Verification also checks that the implementation did not exceed the behavioral contract or frozen write boundary merely because the extra work looked reasonable. ## When to use After implementation, tests, bug fixes, data runs, or smoke checks. ## Inputs - Task name - `SPEC.md` acceptance criteria, non-goals, constraints, invalid-if rules, optional implementation diff budget, optional change-proof contract, and optional test-sensitivity contract - Optional persisted `SCOPE.md` plus its frozen Git base - Commands run or to run - Changed files - Evidence to record - Known risks or untested areas - Optional operator profile `Verification depth` ## Workflow 1. Update VERIFY.md with date + task name. 2. Record commands run as short evidence entries with command, exit code, relevant output, interpretation, acceptance criterion covered, and remaining uncertainty. Keep each entry concise and auditable. 3. For new verification records, maintain a machine-readable `Structured verification evidence` JSON block alongside the human-readable evidence. Use …
Read the whole file at its exact version.
How to install
mdr add tmusser/ai-engineering-skills/verify-contract@sha256:e491e2fe22439603The line at the top of this page pins the label git:20261101.bfc03f8, 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_v4lklf7q6jb5556c)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 15 versions of this file, between Jun 26, 2026 and Nov 1, 2026, about one every 9 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261101.bfc03f8 latest | 2026-11-01 | bfc03f8 | 16,588 B | A | view · diff |
| git:20261030.9f1d6eb | 2026-10-30 | 9f1d6eb | 14,911 B | A | view · diff |
| git:20261029.9a6297b | 2026-10-29 | 9a6297b | 13,228 B | A | view · diff |
| git:20261029.bb23514 | 2026-10-29 | bb23514 | 12,695 B | A | view · diff |
| git:20261027.35bf394 | 2026-10-27 | 35bf394 | 11,533 B | A | view · diff |
| git:20261008.67190ab | 2026-10-08 | 67190ab | 11,267 B | A | view · diff |
| git:20261006.7f6cad8 | 2026-10-06 | 7f6cad8 | 10,443 B | A | view · diff |
| git:20261005.a4c4424 | 2026-10-05 | a4c4424 | 9,087 B | A | view · diff |
| git:20261004.5fe3065 | 2026-10-04 | 5fe3065 | 8,504 B | A | view · diff |
| git:20261003.138fd78 | 2026-10-03 | 138fd78 | 7,337 B | A | view · diff |
| git:20260806.24a682d | 2026-08-06 | 24a682d | 6,318 B | A | view · diff |
| git:20260726.ce98f0d | 2026-07-26 | ce98f0d | 5,062 B | A | view · diff |
| git:20260703.5dfb298 | 2026-07-03 | 5dfb298 | 3,871 B | A | view · diff |
| git:20260626.611ea2c | 2026-06-26 | 611ea2c | 2,799 B | A | view · diff |
| git:20260626.cb061b5 | 2026-06-26 | cb061b5 | 2,333 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 (16588 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
tmusser/ai-engineering-skills · 6 stars · license MIT · pushed 2026-11-01 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_v4lklf7q6jb5556c GET https://markdownregistry.com/api/v1/resolve?ref=tmusser/ai-engineering-skills/verify-contract GET https://markdownregistry.com/api/v1/blob/e491e2fe224396037bb15aaecc59cda1a864d0e07a9acd8f9c9a9fddcd815834
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.