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 agentmods add skills/dcosson/h2/babysit-prnpx skills add dcosson/h2 --skill babysit-prgit clone --depth 1 https://github.com/dcosson/h2Wrote 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/dcosson/h2/babysit-pr)<a href="https://agentmods.dev/skills/dcosson/h2/babysit-pr"><img src="https://agentmods.dev/badge/skills/dcosson/h2/babysit-pr.svg" alt="Measured on agentmods" 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 | $0.00084 | $0.03796 |
| Opus 5 | $0.00042 | $0.01898 |
| Sonnet 5 | $0.00017 | $0.00759 |
| Haiku 4.5 | $0.00008 | $0.00380 |
Grade A, and why
babysit-pr 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.
How it starts
The opening of the file, as written. The whole thing — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Babysit PR
You have an open PR that needs ongoing attention as CI runs, review bots post comments, and humans drop occasional feedback. Rather than the user (or you) actively babysitting it, you'll self-schedule wakeups every 5 minutes for up to ~20 fires and process whatever's new each time.
This skill ends when the PR is green and review is clean. It NEVER merges the PR — see the bottom of this doc.
Prerequisites: know your review bots
Before starting the loop, identify which review bots are active on this PR and how each one is triggered for re-review. Do not assume any bot auto-re-reviews on push. Most do not. Look up the bot's behavior before your first tick — not mid-loop when you've already pushed a fix and need to know.
Known bots
-
Cursor Bugbot (
@cursor) — Runs automatically on PR open and onready_for_review. Does not re-run on push. To re-request review after pushing a fix:gh pr comment <pr> --body "@cursor review". Always re-tag explicitly after any fix push. -
Other bots — Check the bot's docs or past PR comments to learn its trigger. When in doubt, re-tag explicitly — a redundant review request costs nothing; a missed review cycle costs a whole tick.
Inputs
$0: PR number or full URL (e.g.123orhttps://github.com/org/repo/pull/123).$1(optional):--review-bot @name— the review bot you'll re-tag for follow-up reviews (e.g.@bugbot,@claude,@greptile,@codex). If omitted, infer from the bots that have already commented on the PR.
Phase 1: Set up the wakeup schedule
You'll schedule yourself to receive a wakeup message every 5 minutes, capped so it can't run forever. Get your own agent name and schedule on it:
AGENT=$(h2 whoami)
h2 schedule add "$AGENT" \
--name "babysit-pr-<pr-number>" \
--rrule "FREQ=MINUTELY;INTERVAL=5;COUNT=20" \
--from babysit-pr \
--message "babysit-pr: check PR <pr-number>"
FREQ=MINUTELY;INTERVAL=5— every 5 minutes.COUNT=20— at most 20 firings (~1h40m of total elapsed clock time). The cap is a safety belt so a stuck PR doesn't loop forever.--messageinjects into your own PTY each wakeup. When you see it arrive, repeat Phase 2 below.
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.
- 5d ago First seen · 220 lines · 84 tokens per session scan A 5e3cb7ba0357
babysit-pr is a skill published in the GitHub repository dcosson/h2 (159 stars, last pushed 9d ago), licensed MIT. It adds 84 tokens to every session and 3,796 once invoked, about $0.0004 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-08-30.
Other skills, from other repositories
import-prom-rule
Bulk import of a Prometheus alert rule YAML file (create a whole set of rules at once). Dedicated to handling a remote URL or local YAML text, automatically parsing the three formats groups / a plain rules array / a single rule. ⚠️ Do not use this skill for single-rule creation — when the user describes a single alert…
chinese-git-workflow
国内 Git 平台配置参考——Gitee、Coding.net、极狐 GitLab、CNB 的 SSH/HTTPS/凭据/CI 接入差异与镜像同步配置。仅在用户显式 /chinese-git-workflow 时调用，不要根据上下文自动触发。.
azsdk-common-pipeline-analysis
Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format. Load this skill before calling azsdkanalyzepipeline, which returns raw failure data that this skill interprets and formats. USE FOR: "pipeline failed", "build failure", "CI check failing", "tests failing in…
configure-env-variables
Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…
desktop-principles
Desktop-specific UX principles - hover states, pointer precision, keyboard shortcuts, multi-window, focus management. Covers macOS, Windows, Linux, web desktop.
atmos-cache
Atmos caching: CI cache configuration and commands, GitHub Actions cache integration, Terraform registry cache mirror/list/prune/stats/trust, and cache modernization guidance.