verify-before-claiming SKILL.md skillA
This file is byte-identical to the first copy the registry indexed, one of 6 indexed copies. Same content hash, so the same checks give both the same grade.
verify-before-claiming from leonardleroy/i-dont-believe-you is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add leonardleroy/i-dont-believe-you/verify-before-claiming@git:20260924.425ec48Pins git:20260924.425ec48 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- leonardleroy/i-dont-believe-you
- Path
skills/verify-before-claiming/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260924.425ec48, committed Sep 24, 2026
- First version recorded
- Sep 15, 2026
- Size
- 11,151 bytes
- Repository stars
- 18
- License
- MIT
Use for any task that will end in a claim about tests, the build, or whether the work is done: making tests pass, fixing a failing test, fixing a bug, implementing a feature, refactoring, debugging, getting CI green. Runs eight shell commands against the real diff and requires their raw output before success can be reported.
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 before claiming
You are about to tell the user something worked. You do not know that yet. Find out first.
## The rule
Before any sentence containing "tests pass", "build is green", "done", "fixed", "ready" or
anything equivalent, run every check below and paste the raw output into your reply.
If a check prints a line, you have found something. Do not report success. Read the line, open
the file, and either fix the code or rewrite your summary so it states what is actually true.
## Pin the base first
Every command below compares the working tree against `${IDBY_BASE:-HEAD}`. `HEAD` is a valid base
only while nobody has committed since the work started. One `git commit` moves `HEAD` onto the
change itself, and all eight checks fall silent on a change they would otherwise have caught.
Committing work is normal, so this happens without any intent to hide anything.
Pin a base the agent cannot move, before the work starts:
`export IDBY_BASE=$(git rev-parse HEAD)`. In CI, pin the pull request's merge-base instead:
`export IDBY_BASE=$(git merge-base origin/main HEAD)`. A pinned SHA stays reachable after the base
commit is amended or rebased.
…Read the whole file at its exact version.
How to install
mdr add leonardleroy/i-dont-believe-you/verify-before-claiming@sha256:9248c172a0e468deThe line at the top of this page pins the label git:20260924.425ec48, 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_y5yo6djqqo6mo7dt)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Sep 15, 2026 and Sep 24, 2026, about one every 2 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260924.425ec48 latest | 2026-09-24 | 425ec48 | 11,151 B | A | view · diff |
| git:20260919.3048e34 | 2026-09-19 | 3048e34 | 7,698 B | A | view · diff |
| git:20260916.26170c6 | 2026-09-16 | 26170c6 | 5,768 B | A | view · diff |
| git:20260915.f4eeb8b | 2026-09-15 | f4eeb8b | 5,023 B | A | view · diff |
| git:20260915.1a63bb9 | 2026-09-15 | 1a63bb9 | 4,998 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 (11151 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
leonardleroy/i-dont-believe-you · 18 stars · license MIT · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_y5yo6djqqo6mo7dt GET https://markdownregistry.com/api/v1/resolve?ref=leonardleroy/i-dont-believe-you/verify-before-claiming GET https://markdownregistry.com/api/v1/blob/9248c172a0e468de98c5b209d032dfc3c6c12ba5ff42f693baadc9b263fe2a71
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.
More from leonardleroy/i-dont-believe-you
Every file in leonardleroy/i-dont-believe-you