agent-coordination

agent-coordination is a skill for Claude Code from a5c-ai/babysitter. It costs 31 tokens per session (370 once invoked), scanned A, original, MIT.

An agent coordination system for distributing work through hooks, which are assigned work queues for agents. It supports persistent collaborators and temporary workers, including handoffs and recovery of stuck sessions.

In plain words
What is it for?
Use it to feed tasks to agents, hand work from one agent to another, prompt stuck agents, and revive an ended agent session.
Why use it?
It gives teams a consistent way to assign, transfer, and resume work when several coding agents are working together.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool.

Good fit Use it to feed tasks to agents, hand work from one agent to another, prompt stuck agents, and revive an ended agent session.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/a5c-ai/babysitter/agent-coordination
About the project

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.

a5c-ai/babysitter · 1,778 stars · on GitHub · a5c.ai

Install

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.

Any agent
npx skills add a5c-ai/babysitter --skill agent-coordination
Clone the repo
git clone --depth 1 https://github.com/a5c-ai/babysitter

Made for: Claude Code.

Wrote 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.

agentmods badge for agent-coordination

README.md
[![agentmods](https://agentmods.dev/badge/skills/a5c-ai/babysitter/agent-coordination.svg)](https://agentmods.dev/skills/a5c-ai/babysitter/agent-coordination)
Your own site
<a href="https://agentmods.dev/skills/a5c-ai/babysitter/agent-coordination"><img src="https://agentmods.dev/badge/skills/a5c-ai/babysitter/agent-coordination.svg" alt="Measured on agentmods" height="20"></a>
Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 370 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00031 $0.00370
Opus 5 $0.00015 $0.00185
Sonnet 5 $0.00006 $0.00074
Haiku 4.5 $0.00003 $0.00037

Measured 5d ago against content hash 920c164de57c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

agent-coordination 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 5d 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.

library/methodologies/gastown/skills/agent-coordination/SKILL.md · 42 lines

What it actually says

  • Managing agent handoffs
  • Nudging stuck agents
  • Coordinating Crew and Polecat workers
  • Setting up hook hierarchies

Agent Types

  • Crew: Long-lived, named agents for persistent collaboration
  • Polecats: Transient workers with persistent identity but ephemeral sessions
  • Dogs: Deacon helpers for infrastructure tasks

Hook Hierarchy

Three-tier hook system (base -> role -> rig+role):

  1. Base hooks: Apply to all agents
  2. Role hooks: Apply to agents in a specific role
  3. Rig+Role hooks: Apply to agents on a specific rig in a specific role

Key Commands

  • gt agents - List available agents
  • gt feed - Feed work to an agent's hook
  • gt handoff - Hand off work between agents
  • gt nudge - Nudge a stuck agent
  • gt seance - Revive a dead agent session

Tool Use

Invoke via babysitter process: methodologies/gastown/gastown-orchestrator (assign-workers step)

Files

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.

Changes

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.

  1. 5d ago First seen · 42 lines · 31 tokens per session scan A 920c164de57c

Subscribe to this mod's changes

agent-coordination is a skill published in the GitHub repository a5c-ai/babysitter (1,778 stars, last pushed 2d ago), licensed MIT. It adds 31 tokens to every session and 370 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.