verification-reviewer SKILL.md skillA
verification-reviewer from stunspot/testforge is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add stunspot/testforge/verification-reviewer@git:20260912.055c86aPins git:20260912.055c86a in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- stunspot/testforge
- Path
releases/v2.0.0/codex/testforge/skills/verification-reviewer/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260912.055c86a, committed Sep 12, 2026
- First version recorded
- Sep 6, 2026
- Size
- 3,921 bytes
- Repository stars
- 17
- License
- a license file GitHub does not identify
🔍 Audit release verdicts and test proof.
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
# Try to make the release claim fail Receive the verification brief, impact map, manifest, scenarios, tests, raw and normalized execution evidence, findings, residual risks, and proposed status. Preserve independence: inspect before accepting the operator's narrative, and do not improve weak work invisibly. Ask first: **what would have to be false for this recommendation to be unsafe?** Find the smallest consequential break in the chain: `scope → impact → risk → invariant → scenario → test → evidence → status` Use `review-rubric.md` and `adversarial-checks.md`. Re-run `scripts/validate_manifest.py` and `scripts/validate_traceability.py` when tool access exists. A valid file is not a valid argument; deterministic checks establish structure, not test quality or correctness. When author confidence or earlier verdicts could anchor the review, use `cold-read-review.md`: inspect the complete relevant evidence before the proposed status, then reconcile your assessment with it. Retain failure history and methodological changes; blinding removes evaluative priming, not inconvenient evidence. …
Read the whole file at its exact version.
How to install
mdr add stunspot/testforge/verification-reviewer@sha256:29d3f974ae9cefffThe line at the top of this page pins the label git:20260912.055c86a, 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_uzao6tunptels3if)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Sep 6, 2026 and Sep 12, 2026, about one every 7 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260912.055c86a latest | 2026-09-12 | 055c86a | 3,921 B | A | view · diff |
| git:20260906.07644e6 | 2026-09-06 | 07644e6 | 3,603 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 (3921 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
stunspot/testforge · 17 stars · license a license file GitHub does not identify · pushed 2026-10-12 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_uzao6tunptels3if GET https://markdownregistry.com/api/v1/resolve?ref=stunspot/testforge/verification-reviewer GET https://markdownregistry.com/api/v1/blob/29d3f974ae9cefffa8a524c838ab0c00211cd22ce86bc8df86605c4ccb3f2d5e
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 stunspot/testforge
Every file in stunspot/testforge