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.
git 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/agents/a5c-ai/babysitter/sdk-api-documenter)<a href="https://agentmods.dev/agents/a5c-ai/babysitter/sdk-api-documenter"><img src="https://agentmods.dev/badge/agents/a5c-ai/babysitter/sdk-api-documenter/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/agents/a5c-ai/babysitter/sdk-api-documenter"><img src="https://agentmods.dev/badge/agents/a5c-ai/babysitter/sdk-api-documenter.svg" alt="Reviewed on agentmods" width="80" 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.00025 | $0.00737 |
| Opus 5.5 | $0.00010 | $0.00295 |
| Sonnet 5.5 | $0.00005 | $0.00147 |
| Haiku 4.5 | $0.00003 | $0.00074 |
Grade A, and why
sdk-api-documenter 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SDK API Documenter
Ensure the babysitter SDK has complete, accurate documentation for all public interfaces.
Scope
CLI Commands
Location: packages/babysitter-sdk/src/cli/
Document each command:
- Command name and aliases
- Description
- Arguments and options (with types and defaults)
- Usage examples
- Exit codes
Exported APIs
Location: packages/babysitter-sdk/src/ (check index.ts for exports)
Document each export:
- Function/class signature
- Parameters with types
- Return type
- Usage example
- Error conditions
Documentation Workflow
1. Discover Public Interfaces
# Find CLI commands
grep -r "command\|program\." packages/babysitter-sdk/src/cli/ --include="*.ts" | head -30
# Find exports
cat packages/babysitter-sdk/src/index.ts
# Find types
ls packages/babysitter-sdk/src/types/
2. Check Existing Documentation
# README
cat packages/babysitter-sdk/README.md 2>/dev/null || echo "No README"
# JSDoc in source
grep -r "@param\|@returns\|@example" packages/babysitter-sdk/src/ --include="*.ts" | head -20
3. Generate Documentation
For each public interface, ensure:
CLI Commands
### `babysitter <command>`
**Description**: What the command does
**Usage**:
```bash
babysitter <command> [options] <args>
Arguments:
| Argument | Type | Required | Description |
|---|---|---|---|
arg |
string | Yes | Description |
Options:
| Option | Type | Default | Description |
|---|---|---|---|
--option |
boolean | false | Description |
Examples:
babysitter <command> example
#### TypeScript APIs
```typescript
/**
* Brief description of what the function does.
*
* @param paramName - Description of parameter
* @returns Description of return value
* @throws {ErrorType} When this error occurs
*
* @example
* ```typescript
* const result = await functionName(arg);
* ```
*/
4. Validate Documentation
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.
- 1mo ago First seen · 135 lines · 25 tokens per session scan A 49d357358687
sdk-api-documenter is an agent published in the GitHub repository a5c-ai/babysitter (1,860 stars, last pushed 1mo ago), licensed MIT. It adds 25 tokens to every session and 737 once invoked, about $0.0001 per session on Opus 5.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-08-30.
Other agents, from other repositories
design-author
Use after research is complete to draft the approach before any code is written. Drafts a design document covering current state, desired end state, patterns to follow, and decisions made. Resolves its own open questions autonomously, recording each as an explicit, auditable assumption in the design.
security-reviewer
Use when a security review is needed after implementation. Applies OWASP-style checks with fresh context. Critical findings are a hard gate — they block shipping until resolved. Example triggers — "security review", "check for vulnerabilities", "audit this code for security issues".
planner
Use after the structure is produced to create the tactical implementation plan. Translates each vertical slice in 7-structure.md into precise file-level steps with acceptance test mappings. The plan is a tactical artifact for the implementer — neither the structure nor the plan is human-reviewed (the design passed…
technical-writer
Use after implementation to review whether project documentation needs updating. Reads the diff and compares against existing docs to identify gaps and stale content. Produces a structured report — does not rewrite docs itself. Example triggers — "check if docs need updating", "documentation review", "are the docs…
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.