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 swarm-orchestrationgit 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/swarm-orchestration)<a href="https://agentmods.dev/skills/a5c-ai/babysitter/swarm-orchestration"><img src="https://agentmods.dev/badge/skills/a5c-ai/babysitter/swarm-orchestration/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/swarm-orchestration"><img src="https://agentmods.dev/badge/skills/a5c-ai/babysitter/swarm-orchestration.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.00028 | $0.00432 |
| Opus 5 | $0.00014 | $0.00216 |
| Sonnet 5 | $0.00006 | $0.00086 |
| Haiku 4.5 | $0.00003 | $0.00043 |
Grade A, and why
swarm-orchestration 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 7d 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
- Tasks needing coordinated parallel execution
- When consensus among agents is required for quality
- Projects requiring anti-drift enforcement during execution
Process
- Topology Selection - Analyze task and agent pool to select optimal topology
- Agent Assignment - Assign Queen (Strategic/Tactical/Adaptive) and Worker roles
- Consensus Init - Initialize Raft/Byzantine/Gossip/CRDT protocol
- Parallel Execution - Distribute subtasks with shared memory
- Anti-Drift Checkpoints - Validate alignment every N subtasks
- Consensus Voting - Weighted voting (Queen=3x) for final decision
Topologies
- Mesh: All-to-all communication, best for small swarms (<8 agents)
- Hierarchical: Queen coordinates workers, best for large/structured tasks
- Ring: Sequential handoff, best for pipeline/transformation tasks
- Star: Central coordinator fan-out, best for independent subtasks
Agents Used
agents/strategic-queen/- Long-term planning swarmsagents/tactical-queen/- Execution coordination swarmsagents/adaptive-queen/- Real-time optimization swarmsagents/swarm-coordinator/- Topology management
Tool Use
Invoke via babysitter process: methodologies/ruflo/ruflo-swarm-coordination
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.
- 7d ago First seen · 43 lines · 28 tokens per session scan A 5b9fca8aaa9e
swarm-orchestration is a skill published in the GitHub repository a5c-ai/babysitter (1,788 stars, last pushed 5d ago), licensed MIT. It adds 28 tokens to every session and 432 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
kano-backlog
Prioritize and refine a GitHub Issues backlog with the Kano model — categorize every open issue as Must-be, Performance, Attractive, Indifferent, or Reverse, apply Kano + priority labels back to GitHub automatically, and recommend the single best next issue to pick up. Use this whenever the user wants to triage…
team-structure
Breaks a reviewed design into verified slices. Trigger on "slice this up", "break the design into steps", or "/team-structure".
tracking-tickets
Defines tracker status transitions and closing rules. Load when a pipeline run is linked to a ticket.
team-pr
Opens a pull request after verification. Trigger on "open the PR", "open a draft PR", or "/team-pr" only; never infer the phase from passed verification.
pr-watch-mechanics
Bounded watch-loop mechanics for the pr-watch skills: cycle timing, soft cap, handoff. Load when running or authoring a PR watch loop.
team-question
Decomposes a feature into task and question artifacts. Trigger on "shape this idea", "decompose this task", or "/team-question".