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 bendrucker/claude --skill babysitgit clone --depth 1 https://github.com/bendrucker/claudeWrote 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/bendrucker/claude/babysit)<a href="https://agentmods.dev/skills/bendrucker/claude/babysit"><img src="https://agentmods.dev/badge/skills/bendrucker/claude/babysit/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/bendrucker/claude/babysit"><img src="https://agentmods.dev/badge/skills/bendrucker/claude/babysit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00040 | $0.01407 |
| Opus 5.5 | $0.00016 | $0.00563 |
| Sonnet 5.5 | $0.00008 | $0.00281 |
| Haiku 4.5 | $0.00004 | $0.00141 |
Grade A, and why
pull-request:babysit 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 20d 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.
How it starts
The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Babysit PR
Delegate CI monitoring to a provider-specific watcher and react to its events with fix-and-push behavior, stopping when CI turns green.
Context
- Branch: !
git branch --show-current - Remote URL: !
git remote get-url origin - Start SHA: !
git rev-parse HEAD - Session:
${CLAUDE_SESSION_ID}
Workflow
Inspect the remote URL. For a github.com remote, invoke the github:actions-monitor skill. For a gitlab.com remote, invoke the gitlab:ci-monitor skill. Each provider skill owns the watcher process (via the Monitor tool) and emits a structured JSON event stream describing CI state changes.
Babysit consumes that event stream and reacts with the handlers below. The watcher handles polling, deduping by (sha, state), rate limits, timeouts, and session-scoped lifecycle. Babysit handles fixes, pushes, and reporting. Remember the start SHA above so the success handler can summarize work done in the session.
Parse $ARGUMENTS for an optional PR positional and two optional flags, both flags off by default so plain babysit stays CI-only:
$0(pr-url): the PR to babysit, given as a URL or number. Pass it through tofollow-upand the merge commands below. Default: resolve the PR from the branch in Context.--reviews: after the first green, triage AI-reviewer threads. See Reviews Hand-off.--merge: don't stop at green; drive the PR to merged. See Merge Mode.
Bounds
Every wait babysit performs runs through a watcher, including the post-submit merge wait (Merge Mode); babysit has no poll loop of its own. The watcher enforces the wall clock (--max-minutes, default 60), poll interval, and dedup, so pass --max-minutes through when the user supplies one. After a watcher emits max-time-reached it has exited: report and stop, never re-arm a fresh watcher. If babysit runs under /loop, the loop owns repetition, not babysit.
Event Handlers
status: running
Do nothing. The watcher emits a new status event when the situation changes.
What ships with it
3 files 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.
- 1mo ago Changed · -1 lines 6fde9e2b8fda
- 1mo ago First seen · 101 lines · 40 tokens per session scan A f24a21bad860
pull-request:babysit is a skill published in the GitHub repository bendrucker/claude (18 stars, last pushed today), licensed MIT. It adds 40 tokens to every session and 1,407 once invoked, about $0.0002 per session on Opus 5.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
pr-watch
Local PR watcher. Monitors CI status, automatically fixes failing checks by reading failure logs and applying targeted fixes, then optionally merges when all checks pass. Local CLI analog to Claude Code's cloud auto-fix feature.
ops-ship
OPS on-demand: This skill should be used when the user asks to "ship ops plugin", "merge all PRs and…
push-ci
Push to remote and monitor CI. Validates branch safety, executes git push WITH explicit user approval, then monitors CI run status via gh CLI. Use when: user says 'push', 'push and watch CI', 'ship it', 'push-ci'. Not for: committing (use /smart-commit), creating PRs (use /create-pr), merging (use /merge-prep).
cloudflare-workers-ci-cd
Complete CI/CD guide for Cloudflare Workers using GitHub Actions and GitLab CI. Use for automated testing, deployment pipelines, preview environments, secrets management, or encountering deployment failures, workflow errors, environment configuration issues.
renovate
Generate renovate.json covering all dependency file types used in a repo, emit a GitHub Actions workflow that validates renovate.json on every PR, or generate a pre-commit hook for local validation.
pipeline-digest
Daily release-pipeline digest with a change gate — reports which plugins are pending release, whether main's CI is green, and which branches went stale, and notifies the operator only when that state actually moved since the last run. Use when the operator asks "what moved in the pipeline", "anything to ship"…