Use when implementing any feature or bugfix, before writing implementation code. Enforces RED-GREEN-REFACTOR cycle.
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
## Red Flags (STOP and Start Over)
- Code before test
- Test passes immediately
- "I'll test after"
- "Too simple to test"
- Rationalizing "just this once"
## Agents Used
- Process agents defined in `test-driven-development.js`
## Tool Use
Invoke via babysitter process: `methodologies/superpowers/test-driven-development`
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 (1019 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_4k3cs7lmskf3rsl4
GET https://markdownregistry.com/api/v1/resolve?ref=a5c-ai/babysitter/test-driven-development
GET https://markdownregistry.com/api/v1/blob/b24ad18628325b9256684e069c6ca75fd07cfb779d7759f85e2213d37b9e1b7b
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…
addyosmani/agent-skills · skills/test-driven-development/SKILL.md · Drives development with tests using the red-green-refactor loop. Use when implementing any logic, fixing any bug, or…
mvschwarz/openrig · skills/_canonical/process/test-driven-development/SKILL.md · Use when implementing any feature or bugfix, before writing implementation code
mvschwarz/openrig · packages/daemon/specs/agents/shared/skills/process/test-driven-development/SKILL.md · Use when implementing any feature or bugfix, before writing implementation code
cbrock84/headcount · plugins/technology/skills/test-driven-development/SKILL.md · Drives implementation by writing a failing test first, then the smallest code that passes it. Use this before writing…
a5c-ai/babysitter · library/methodologies/rpikit/skills/test-driven-development/SKILL.md · Test-first development practice where test specifications are written before production code, integrated into plan…
a5c-ai/babysitter · library/methodologies/cc10x/skills/test-driven-development/SKILL.md · Strict RED-GREEN-REFACTOR cycle enforcement. Tests are never skipped or deferred. Run mode only, never watch mode. Exit…
