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 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/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/dcosson/h2/babysit-pr"><img src="https://agentmods.dev/badge/skills/dcosson/h2/babysit-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 85 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 85 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium Excessive Agency · line 45 Skill allows unbounded resource consumption (API calls, storage, compute). Without rate limits or quotas, a compromised or misbehaving agent can cause denial-of-service or cost overruns.Fix: Set explicit rate limits, timeouts, and resource quotas for API calls, file operations, and compute. Implement circuit breakers for runaway loops.
- medium Excessive Agency · line 138 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00084 | $0.03796 |
| Opus 5.5 | $0.00034 | $0.01518 |
| Sonnet 5.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 1mo 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.
- 1mo ago First seen · 220 lines · 84 tokens per session scan A 5e3cb7ba0357
babysit-pr is a skill published in the GitHub repository dcosson/h2 (163 stars, last pushed yesterday), licensed MIT. It adds 84 tokens to every session and 3,796 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
deployment-patterns
Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications. Use when setting up deployment infrastructure or planning releases.
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.
baby-sit
Monitor a GitHub pull request until CI is green, diagnose failures, and rerun only evidence-backed flaky GitHub Actions jobs.
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
atmos-hooks
Atmos hooks: lifecycle events, hook kinds, command/store/git/security hooks, step/steps hooks, when: conditions, scoping and overrides, toolchain integration, --skip-hooks, and Atmos Pro/local output.
atmos-pro
Atmos Pro setup and workflows: settings.pro, GitHub OIDC, affected and inventory uploads, stack locks, pro commit, workflow dispatch, merge queues, and drift detection.