anti-drift
Hierarchical coordination and drift detection with frequent checkpoints, shared memory coherence validation, role specialization enforcement, and short task cycles.
npx skills add a5c-ai/babysitter --skill anti-drift --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
- Tasks with high risk of scope creep - When multiple agents work on related subtasks - Critical tasks where deviation is costly ## Anti-Drift Mechanisms 1. **Hierarchical Coordinator** - Queen agent validates alignment at checkpoints 2. **Frequent Checkpoints** - Every 2 subtasks (configurable) 3. **Shared Memory Coherence** - Validate all agents see consistent state 4. **Short Task Cycles** - Bounded execution windows prevent runaway agents 5. **Role Specialization** - Agents stay within their assigned scope ## Drift Scoring - `0.0-0.1`: Fully aligned, no intervention needed - `0.1-0.3`: Minor drift, automatic correction - `0.3-0.5`: Significant drift, checkpoint correction with logging - `0.5+`: Critical drift, human escalation via breakpoint ## Agents Used - `agents/swarm-coordinator/` - Drift detection and correction - `agents/tactical-queen/` - Checkpoint enforcement - `agents/adaptive-queen/` - Real-time course correction ## Tool Use Invoke via babysitter process: `methodologies/ruflo/ruflo-swarm-coordination`
- Anti-Drift Mechanisms
- Drift Scoring
- Agents Used
- Tool Use
What does the anti-drift skill do?
Hierarchical coordination and drift detection with frequent checkpoints, shared memory coherence validation, role specialization enforcement, and short task cycles.
How do I install it?
Run `npx skills add a5c-ai/babysitter --skill anti-drift --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From a5c-ai/babysitter, a repository with 1,642 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.