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 assimilate-popular-workflowsgit 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/assimilate-popular-workflows)<a href="https://agentmods.dev/skills/a5c-ai/babysitter/assimilate-popular-workflows"><img src="https://agentmods.dev/badge/skills/a5c-ai/babysitter/assimilate-popular-workflows/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/assimilate-popular-workflows"><img src="https://agentmods.dev/badge/skills/a5c-ai/babysitter/assimilate-popular-workflows.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 216 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 392 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00110 | $0.07523 |
| Opus 5 | $0.00055 | $0.03762 |
| Sonnet 5 | $0.00022 | $0.01505 |
| Haiku 4.5 | $0.00011 | $0.00752 |
Grade A, and why
assimilate-popular-workflows scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Use a browser tool or `curl` to fetch these pages and extract GitHub repo links. For each new repo found, enrich and classify using the standard pipeline. How it starts
The opening of the file, as written. The whole thing — 518 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Assimilate Popular Workflows
Search public GitHub repositories for SKILL.md files, classify each repo by archetype, and maintain structured research documents under docs/reference-repos/[org]/[repo-name]/. The goal is not to copy skills verbatim but to extract transferable value: processes for the babysitter process library, babysitter marketplace plugin ideas, and implicit procedural knowledge that can be codified into babysitter JS processes.
Process Library Placement Rules
Extracted processes go into the babysitter process library (library/). Placement depends on scope:
| What it is | Where it goes | Examples |
|---|---|---|
| Full generic dev methodology (entire workflow paradigm) | methodologies/<name>/ |
agile, gsd, tdd, scrum, kanban, waterfall |
| Common cross-domain pattern (reusable across many specializations) | specializations/shared/ |
audit-pipeline, expert-advisory, progressive-disclosure |
| Domain-specific process | specializations/<domain>/ |
security-compliance, devops-sre-platform, data-science-ml |
Important: Do NOT place domain-specific processes in methodologies/. Only full, generic development methodologies belong there. A "k8s security audit" is specializations/security-compliance/, not a methodology. A "deep research pipeline" is specializations/shared/ (cross-domain). A "TDD agent workflow" is methodologies/atdd-tdd/ (full dev methodology).
Plugin Ideas = Babysitter Marketplace Plugins
A babysitter plugin is a set of natural language instructions (markdown) or deterministic coded processes (JS) that an AI agent reads and executes to install a modular set of capabilities. A plugin contains at minimum install.md with instructions the AI agent follows to modify the user's project. See docs/plugins.md for the full specification.
CRITICAL DISTINCTION: Plugin ideas should ONLY be things that modify project setup, install external integrations, or enforce workflows beyond just adding processes. Do NOT suggest plugins for:
- Skill pack collections: If you mark processes for extraction, don't suggest a plugin that just bundles those processes
- Expert/Role plugins: ".NET Expert", "React Native Expert", "Vue Development Suite", "Security Expert" - these are just skill packs
- Domain suites: "Frontend Development Suite", "DevOps Toolkit", "Data Science Suite" - these bundle processes
- Orchestration patterns: Multi-agent coordination, session continuity, workflow orchestration belong in babysitter core or as processes
- Process repackaging: Any plugin that just wraps processes you already marked for extraction
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.
- 11d ago First seen · 518 lines · 110 tokens per session scan A ebbd089014e2
assimilate-popular-workflows is a skill published in the GitHub repository a5c-ai/babysitter (1,788 stars, last pushed 5d ago), licensed MIT. It adds 110 tokens to every session and 7,523 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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-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.
goga-brainstorm-plan-verification
Verification of the assembled architecture plan against the DSL.