Evidence requirement enforcement ensuring all claims are backed by logs, test results, or exit codes. Zero = success, non-zero = failure. No guessing allowed.
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
## Rules
- Never claim "should work" without evidence
- Never claim success without exit code 0
- Never claim a bug is fixed without reproduction failure
- Always capture and report exit codes
- Always run the full test suite, not just targeted tests
- Use timeout guards (`timeout 60s`) to prevent hanging
## When to Use
- Before completing any BUILD workflow step
- Before claiming a DEBUG fix is verified
- Before approving a REVIEW result
- Before marking any task as done
## Agents Used
- `integration-verifier` (primary consumer)
- `component-builder` (TDD evidence)
- `bug-investigator` (fix evidence)
The line at the top of this page pins the label git:20260601.da7723a, 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.
A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (1314 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
GitHub
a5c-ai/babysitter · 1,891 stars · license MIT · pushed 2026-11-01 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_unqx7coohpxpa46g
GET https://markdownregistry.com/api/v1/resolve?ref=a5c-ai/babysitter/verification-before-completion
GET https://markdownregistry.com/api/v1/blob/96b1c95e6f07aeaf814ff8d3882a4779aa868960b41d5ddb8667a7106ea27730
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.
a5c-ai/babysitter · .claude/skills/assimilate-popular-workflows/SKILL.md · This skill should be used when the user asks to "find skills in the wild", "assimilate popular workflows", "discover…
a5c-ai/babysitter · .claude/skills/babysit-babysitter-issues/SKILL.md · This skill should be used when the user asks to "babysit issues", "work on assigned issues", "check a5c-agent issues"…
a5c-ai/babysitter · .claude/skills/catalog-babysitter-users/SKILL.md · Discover public GitHub repositories that import defineTask from @a5c-ai/babysitter-sdk and maintain a deduplicated…
a5c-ai/babysitter · .claude/skills/fix-failing-pipelines/SKILL.md · This skill should be used when the user asks to "fix pipelines", "fix CI", "check staging pipelines", "fix failing…
a5c-ai/babysitter · .claude/skills/process-builder/SKILL.md · Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the…
a5c-ai/babysitter · .claude/skills/retrospect-external-babysitter-run/SKILL.md · For a repository in the babysitter-users catalog, locate its babysitter processes and any committed runs…
a5c-ai/babysitter · .codex/skills/babysit/SKILL.md · Orchestrate via @babysitter. Use this skill when asked to babysit a run, orchestrate a process or whenever it is called…
obra/superpowers · skills/verification-before-completion/SKILL.md · Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running…
mvschwarz/openrig · packages/daemon/specs/agents/shared/skills/process/verification-before-completion/SKILL.md · Use when about to claim work is complete, fixed, or passing, or before committing or creating PRs
mvschwarz/openrig · skills/_canonical/process/verification-before-completion/SKILL.md · Use when about to claim work is complete, fixed, or passing, or before committing or creating PRs
a5c-ai/babysitter · library/methodologies/superpowers/skills/verification-before-completion/SKILL.md · Use when about to claim work is complete, fixed, or passing, before committing or creating PRs. Evidence before…
ganyuanran/aegis · skills/verification-before-completion/SKILL.md · Use when about to claim work is complete, fixed, passing, verified, release-ready, or ready to commit, merge, publish…
coco-research/coco · skills/verification-before-completion/SKILL.md · Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running…
xu123-bob/baize · agent/skills/superpowers/5.1.0/skills/verification-before-completion/SKILL.md · Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running…