Babysitter is a workflow engine for AI coding agents that enforces predefined steps, quality checks, human approvals, and decision records. It is used to coordinate complex, repeatable agent workflows across supported coding tools. The catalogue contains skills, agents, instructions, settings, a plugin, and an MCP integration for its workflow.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add a5c-ai/babysitter --skill quality-checklistgit clone --depth 1 https://github.com/a5c-ai/babysitterWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/a5c-ai/babysitter/quality-checklist)<a href="https://agentmods.dev/skills/a5c-ai/babysitter/quality-checklist"><img src="https://agentmods.dev/badge/skills/a5c-ai/babysitter/quality-checklist/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/a5c-ai/babysitter/quality-checklist"><img src="https://agentmods.dev/badge/skills/a5c-ai/babysitter/quality-checklist.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00025 | $0.00360 |
| Opus 5 | $0.00013 | $0.00180 |
| Sonnet 5 | $0.00005 | $0.00072 |
| Haiku 4.5 | $0.00003 | $0.00036 |
Grade A, and why
quality-checklist scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
- When validating code quality against constitution standards
- When verifying specification requirement coverage
- When running custom project-specific quality checks
Key Principle
Quality validation must be objective, reproducible, and multi-dimensional. Failed items must have actionable remediation recommendations. The checklist supports convergence loops -- re-validate after fixes until quality threshold is met.
Process
- Validate code quality - Check against constitution coding standards
- Verify test coverage - Ensure coverage meets constitution thresholds
- Check spec satisfaction - Verify all requirements are implemented
- Assess performance - Validate against constitution benchmarks
- Verify security - Check compliance with constitution security constraints
- Execute custom checks - Run any project-specific quality checks
- Score overall quality - Weighted average across categories (0-100)
- Produce recommendations - Actionable fixes for failed items
- Remediation loop - Re-validate after fixes (up to 3 iterations)
Tool Use
Invoke via babysitter process: methodologies/spec-kit/spec-kit-implementation (quality checklist phase)
Full pipeline: methodologies/spec-kit/spec-kit-orchestrator
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 5d ago First seen · 37 lines · 25 tokens per session scan A ac391eb84a85
quality-checklist is a skill published in the GitHub repository a5c-ai/babysitter (1,778 stars, last pushed 3d ago), licensed MIT. It adds 25 tokens to every session and 360 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
team-implement
Executes and verifies implementation slices. Trigger on "implement this", "execute the plan", or "/team-implement" only; never infer the phase from a ready plan.
pr-verify
Verifies a PR test plan with evidence-rated verdicts. Trigger on "verify the test plan", "check the PR items", "is this PR ready", or "/pr-verify".
check
Confirm a change before merge. /check verify drives the real app to prove behavior against the spec (every acceptance criterion met, every surface built). /check review runs a senior code review on a fresh model, one that did not write the code. Verify after /develop, review before a PR. Writes to docs/reviews/, never…
attest
Verifying spec compliance: extracts ACs from specs, adversarially checks conformance, generates BDD scenarios and traceability matrices. Use when impl must be proven to match a PRD/SRS/AC.
test-generator
Automatically suggest tests for new functions and components. Use when new code is written, functions added, or user mentions testing. Creates test scaffolding with Jest, Vitest, Pytest patterns. Triggers on new functions, components, test requests, testing mentions.
radar
Adding edge-case tests, repairing flaky tests, and improving coverage. Use when test gaps need filling or regressions need guarding. Supports JS/TS, Python, Go, Rust, and Java.