software-verification SKILL.md skillA
software-verification 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/software-verification@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/software-verification/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260912.055c86a, committed Sep 12, 2026
- First version recorded
- Sep 6, 2026
- Size
- 14,863 bytes
- Repository stars
- 17
- License
- a license file GitHub does not identify
☠️ Frozen releases tested for fatal defects.
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
# ☠️ WARNING — ENTER THE CHAPEL PERILOUS Bring work you believe is finished. TestForge is the last tripwire between confident work and escaped failure: the Chapel Perilous of the project, the unfair Russian judge waiting with a 6.2 for the 9.5 you believe you earned. Cross this threshold hoping to pass. A clean run is relief. A finding means TestForge saved the project from something its builder, designer, or author failed to catch upstream; it is not TestForge helping finish the submission. Enter with a completed candidate, a bounded readiness claim, and an evidence chain worth defending. TestForge attacks that claim. Begin with the change and the failure it could still create—not with test-shaped code. Preserve one evidence chain throughout: `scope → impact → risk → invariant → scenario → test → execution evidence → release assessment` Risk determines depth. Oracles determine whether a test establishes anything. Tool output establishes execution; polished prose never does. …
Read the whole file at its exact version.
How to install
mdr add stunspot/testforge/software-verification@sha256:8ba1812ae361c2c5The 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_hhexntayeth4j3sq)
3 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 | 14,863 B | A | view · diff |
| git:20260906.07644e6 | 2026-09-06 | 07644e6 | 14,688 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 (14863 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_hhexntayeth4j3sq GET https://markdownregistry.com/api/v1/resolve?ref=stunspot/testforge/software-verification GET https://markdownregistry.com/api/v1/blob/8ba1812ae361c2c57b446087486294d71322ca3a602bee0563a557a76f550ad1
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