prove-checks SKILL.md skillA
prove-checks from sergeyklay/.agents is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add sergeyklay/.agents/prove-checks@v1.2Pins v1.2 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- sergeyklay/.agents
- Path
.agents/skills/prove-checks/SKILL.md- Versions recorded
- 9
- Latest version
- v1.2, committed Sep 25, 2026
- First version recorded
- Sep 3, 2026
- Size
- 16,622 bytes
- Repository stars
- 6
- License
- Apache-2.0
Prove a passing check was capable of failing before recording it as evidence. Use when a test, CI job, build-and-diff, smoke test or rehearsal comes back green and that green is about to be treated as proof - especially when the check depends on a setup mutation (a sed/awk rewrite, an env var, a secret, a fixture file, a branch or working-copy state), when a job passes under continue-on-error, `|| true`, `set +e` or warning-only output, when an event-driven workflow is hand-run while nothing…
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
# Prove the Check Can Fail A green result is evidence only if red was reachable. Every check runs in a state, and when that state is wrong the check does not error — it passes, cheaply and convincingly. The failure is silent by construction: nothing in the output distinguishes "the system works" from "the system was never asked". Five ways a check goes green without testing anything: | Shape | What happened | What green meant | |---|---|---| | Setup no-op | The mutation the check depends on never applied | The check compared the old state to itself | | Subject not exercised | Only the downstream half ran, or it ran its no-op branch | The upstream half is still unverified | | Failure suppressed | The failure path was routed to a warning or a forced exit 0 | Exit status carries no information | | Nothing executed | The gate was set and the run exercised none of the subject anyway | Zero checks ran, and exit 0 says what a full pass says | | Subject substituted | The named target was unreachable and the tool silently chose another one | The work was done correctly, on the wrong thing | ## Trigger Run this before recording any green as proof, and always when one of these is true: …
Read the whole file at its exact version.
How to install
mdr add sergeyklay/.agents/prove-checks@sha256:d0dfe69faa31b91fThe line at the top of this page pins the label v1.2, 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_37ueeyw53ilk237d)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 9 versions of this file, between Sep 3, 2026 and Sep 25, 2026, about one every 3 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.2 latest | 2026-09-25 | 435499d | 16,622 B | A | view · diff |
| v1.2 | 2026-09-20 | b08d02a | 16,553 B | A | view · diff |
| v1.2 | 2026-09-12 | b1f8f9c | 16,722 B | A | view · diff |
| v1.2 | 2026-09-11 | 774512f | 18,368 B | A | view · diff |
| v1.2 | 2026-09-08 | 7141f0b | 16,225 B | A | view · diff |
| v1.1 | 2026-09-07 | 0b11e47 | 15,737 B | A | view · diff |
| v1.0 | 2026-09-07 | 498dfc1 | 12,740 B | A | view · diff |
| v1.0 | 2026-09-06 | e9757b4 | 10,838 B | A | view · diff |
| v1.0 | 2026-09-03 | c449755 | 9,771 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 (16622 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
sergeyklay/.agents · 6 stars · license Apache-2.0 · pushed 2026-11-04 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_37ueeyw53ilk237d GET https://markdownregistry.com/api/v1/resolve?ref=sergeyklay/.agents/prove-checks GET https://markdownregistry.com/api/v1/blob/d0dfe69faa31b91f7e7f2bb993d1fb5072a1331e0b276b77813663cc787b2e4f
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.