patrol-monitoring

Continuous monitoring using Deacon/Witness patterns for agent health checks, stuck detection, and automated recovery.

509 stars

bya5c-ai

View on GitHub Installation ↓

Best use case

patrol-monitoring is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Continuous monitoring using Deacon/Witness patterns for agent health checks, stuck detection, and automated recovery.

Teams using patrol-monitoring should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

You only need a quick one-off answer and do not need a reusable workflow.
You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/patrol-monitoring/SKILL.md --create-dirs "https://raw.githubusercontent.com/a5c-ai/babysitter/main/library/methodologies/gastown/skills/patrol-monitoring/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/patrol-monitoring/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How patrol-monitoring Compares

Feature / Agent	patrol-monitoring	Standard Approach
Platform Support	Not specified	Limited / Varies
Context Awareness	High	Baseline
Installation Complexity	Unknown	N/A

Frequently Asked Questions

What does this skill do?

Continuous monitoring using Deacon/Witness patterns for agent health checks, stuck detection, and automated recovery.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Patrol Monitoring

## Overview

Continuous monitoring using Gas Town's Deacon/Witness pattern. The Deacon supervises overall health, the Witness manages per-rig agent lifecycle, and the Boot (Dog) watches the Deacon itself.

## When to Use

- During active convoy execution
- When agents may become stuck or unresponsive
- For long-running multi-agent workflows
- When automated recovery is desired

## Process

1. **Health check** all active agents and convoys
2. **Detect** stuck or unresponsive agents via heartbeats
3. **Recover** - restart, reassign, or escalate as needed
4. **Report** patrol findings with trend analysis

## Monitoring Roles

- **Deacon**: Daemon supervisor, monitors overall health
- **Witness**: Per-rig lifecycle manager for workers
- **Boot (Dog)**: Watches the Deacon every 5 minutes

## Recovery Modes

- **restart**: Restart the stuck agent session
- **reassign**: Move beads to a different agent
- **escalate**: Alert human for manual intervention

## Tool Use

Invoke via babysitter process: `methodologies/gastown/gastown-patrol`

Related Skills

media-monitoring

509

from a5c-ai/babysitter

Deep integration with media monitoring platforms for coverage tracking, sentiment analysis, and reporting

process-builder

509

from a5c-ai/babysitter

Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.

Workflow & Productivity

babysitter

509

from a5c-ai/babysitter

Orchestrate via @babysitter. Use this skill when asked to babysit a run, orchestrate a process or whenever it is called explicitly. (babysit, babysitter, orchestrate, orchestrate a run, workflow, etc.)