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 retrospect-external-babysitter-rungit 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/retrospect-external-babysitter-run)<a href="https://agentmods.dev/skills/a5c-ai/babysitter/retrospect-external-babysitter-run"><img src="https://agentmods.dev/badge/skills/a5c-ai/babysitter/retrospect-external-babysitter-run/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/retrospect-external-babysitter-run"><img src="https://agentmods.dev/badge/skills/a5c-ai/babysitter/retrospect-external-babysitter-run.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.00120 | $0.02134 |
| Opus 5 | $0.00060 | $0.01067 |
| Sonnet 5 | $0.00024 | $0.00427 |
| Haiku 4.5 | $0.00012 | $0.00213 |
Grade A, and why
retrospect-external-babysitter-run 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 11d 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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Retrospect External Babysitter Run
Analyse a babysitter run that lives in an external public repository, using the same lens as the in-repo /babysitter:retrospect command. Produce a written retrospective with concrete suggestions for the process author (or, if the insight generalizes, for the babysitter project itself).
When to use
- User names an external repo and asks for a retrospective.
- User asks "find a babysitter run to retrospect on" (combine with the
catalog-babysitter-usersskill to pick one). - User asks "how are other people using babysitter processes? What do they get wrong?".
Prerequisites
ghCLI authenticated.docs/repo-with-babysitter-processes.mdexists (if not, run thecatalog-babysitter-usersskill first).- A workspace directory where external repos can be shallow-cloned (default:
/tmp/babysitter-retrospect/or.a5c/tmp/external-runs/).
Phase 1 -- Target selection
- Read
docs/repo-with-babysitter-processes.mdand list Active repos with stars + description. If the user already named a repo, skip to step 3. - Ask the user which repo to retrospect on (use AskUserQuestion in interactive mode; if non-interactive, pick the highest-starred Active repo that wasn't retrospected in the last 30 days -- track via
docs/retrospectives/<owner>-<name>/log.md). - Confirm the target with the user before cloning.
Phase 2 -- Discover processes and runs
Shallow clone the target:
mkdir -p .a5c/tmp/external-runs
cd .a5c/tmp/external-runs
gh repo clone <owner>/<name> -- --depth 50 --single-branch
cd <name>
Locate:
- Process files: files importing
defineTaskfrom@a5c-ai/babysitter-sdk. Use Grep:grep -rl "from '@a5c-ai/babysitter-sdk'" -- . --include='*.js' --include='*.ts'. - Committed runs:
.a5c/runs/<runId>/directories. Many repos gitignore.a5c/runs/entirely -- that's fine; note it and proceed with process-only retrospective. When runs ARE committed, look forrun.json,journal/,tasks/,state/output.json. - Historical runs via git log:
git log --all --diff-filter=A --name-only -- '.a5c/runs/'surfaces runs that existed at some commit even if later cleaned up. Check out the commit that introduced the run if you want the journal content.
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.
- 11d ago First seen · 173 lines · 120 tokens per session scan A 2fbc8873f476
retrospect-external-babysitter-run is a skill published in the GitHub repository a5c-ai/babysitter (1,788 stars, last pushed 6d ago), licensed MIT. It adds 120 tokens to every session and 2,134 once invoked, about $0.0006 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-08-30.
Other skills, from other repositories
goga-review-plan
Verify execution plan completeness and correctness.
goga-brainstorm
Pipeline orchestrator for brainstorming the cells architecture.
goga-define-challenge
Challenge the complete product definition before the PRD is generated.
goga-define-experience
Define the user experience required to achieve the established product goals and solve the identified problem.
goga-define-goals
Define the product outcomes that should be achieved by solving the identified problem for the relevant users.
goga-brainstorm-cell-assembly
Assembling CODEMANIFEST and .usages per cell, with final approval.