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 agentmods add skills/a5c-ai/babysitter/codebase-syncnpx skills add a5c-ai/babysitter --skill codebase-syncgit 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/codebase-sync)<a href="https://agentmods.dev/skills/a5c-ai/babysitter/codebase-sync"><img src="https://agentmods.dev/badge/skills/a5c-ai/babysitter/codebase-sync.svg" alt="Measured on agentmods" height="20"></a>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.00032 | $0.00531 |
| Opus 5 | $0.00016 | $0.00266 |
| Sonnet 5 | $0.00006 | $0.00106 |
| Haiku 4.5 | $0.00003 | $0.00053 |
Grade A, and why
codebase-sync 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 3d 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
- Scan directory structure for project type identification
- Detect language, framework, package manager
- Identify build tools, CI/CD config, test framework
- Map high-level architecture (monorepo, microservices, etc.)
2. Semantic Index Building
Four parallel index domains:
- Code Index: Source files with exports, purposes, dependencies
- Test Index: Test files with cases, fixtures, patterns
- Config Index: Configuration files with parsed rules
- API Index: Public interfaces, types, data models
3. Convention Discovery
- Code style patterns (naming, structure, organization)
- Error handling conventions
- Testing conventions (naming, structure, assertions)
- Git commit message conventions
- Documentation standards
- Language-conditional standards
4. Rule Generation
Convert conventions into enforceable rules:
{
"id": "ts-no-any",
"category": "coding-standards",
"description": "Avoid 'any' type; use 'unknown' and narrow",
"severity": "error",
"autoFixable": false,
"language": "typescript"
}
Rule Categories
| Category | Examples |
|---|---|
| core | task-and-workflow, testing, verification |
| dev-practices | development-practices, context-management |
| tools | research-tools, cli-tools |
| coding-standards | Language-specific rules (conditional) |
Output Artifacts
artifacts/CONVENTIONS.md-- Discovered conventionsartifacts/SEARCH-INDEX.json-- Semantic search indexartifacts/RULES.md-- Generated project rules
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.
- 3d ago First seen · 65 lines · 32 tokens per session scan A ebd1b7cfdb89
codebase-sync is a skill published in the GitHub repository a5c-ai/babysitter (1,772 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session and 531 once invoked, about $0.0002 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
goga-review-plan
Verify execution plan completeness and correctness.
goga-accept-manifest-review
Verify each Cell's CODEMANIFEST against the implementation.
eng-design-doc-review
Reviews a technical design document with fresh context. Trigger on "review the design doc", "audit 6-design.md", "is this design ready", or "/eng-design-doc-review".
goga-change-manifest-reconciler
Reconciliation of CODEMANIFEST specifications with implementation.
goga-change-validator
Final end-to-end validation of the completed change.
goga-accept-report
Generate the final acceptance report with verdict.