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 mblode/agent-skills --skill pr-babysittergit clone --depth 1 https://github.com/mblode/agent-skillsWrote 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/mblode/agent-skills/pr-babysitter)<a href="https://agentmods.dev/skills/mblode/agent-skills/pr-babysitter"><img src="https://agentmods.dev/badge/skills/mblode/agent-skills/pr-babysitter/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/mblode/agent-skills/pr-babysitter"><img src="https://agentmods.dev/badge/skills/mblode/agent-skills/pr-babysitter.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
- Socket pass
- Snyk warn
SkillSpector: 2 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 Tool Misuse · line 85 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- medium Excessive Agency · line 128 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.00055 | $0.03451 |
| Opus 5.5 | $0.00022 | $0.01380 |
| Sonnet 5.5 | $0.00011 | $0.00690 |
| Haiku 4.5 | $0.00006 | $0.00345 |
Grade A, and why
pr-babysitter 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 15d 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Babysitter
- IS: keeping one open PR moving: conflicts, CI across GitHub Actions/Buildkite/Vercel/Fly.io, inbound review comments, and merge readiness, then following the merge through the repo's post-merge watch, as a background monitor or as one-shot fixes.
- IS NOT: opening or editing the PR (
pr-creator), reviewing or fixing the diff itself (tidy), or npm release PRs (autoshipwatches its own release CI; never babysit a release or Version Packages PR it drives).
Mode Selection
| Invocation | Mode |
|---|---|
| "babysit", "watch this PR", "monitor", "keep it green" | Monitor: Phase 1 once, then phases 2-5 on every event or tick |
| "fix CI", "why is CI red", "loop on CI" | One-shot Phase 3 loop |
| "resolve conflicts", "rebase onto main", "update the branch" | One-shot Phase 2 |
| "address the comments", "reply to the reviewers", "triage review comments" | One-shot Comment Triage Workflow |
| "is it ready", "what is blocking the merge" | One-shot Phase 5 report |
Standing rules, every mode:
-
Monitoring or fixing code does not by itself authorize posting replies. Post, resolve threads, or request reviews only when the user authorized that communication; otherwise prepare replies and report them.
-
Resolve
scripts/fetch-comments.shrelative to this installed SKILL.md.${CLAUDE_SKILL_DIR}below is a Claude Code adapter, not a portable environment variable. -
No setup questions. Auto-detect the PR, the CI platforms, and the defaults (poll every 2 minutes, auto-resolve noise, no auto-merge), then start. Overrides arrive inline: "poll every 5 minutes", "enable auto-merge".
-
Skip closed PRs. Skip drafts (
isDraft) unless asked. A merged PR goes on to the repo's post-merge watch: wait for thewatch/<env>commit statuses on the merge SHA, stop at the firstfailureorerror, and report the result (Post-merge Watch inreferences/monitoring-setup.md). If the base it merged onto (the merge commit's first parent, or for a rebase merge the commit before the PR's rebased commits) has nowatch/*status, report "no post-merge watch". Either way, once the merge is live in production, smoke-test the change there read-only (Production smoke test in the same reference), report that too, and stop. -
Comment triage runs autonomously; the plan file is an audit trail, not an approval gate.
-
Speak only on transitions. A quiet poll says nothing.
What ships with it
10 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.
- evals/evals.json 8.4 KB
- references/bot-patterns.md 19 KB
- references/ci-platforms.md 7.5 KB
- references/fix-plan-template.md 5.4 KB
- references/git-resilience.md 1.8 KB
- references/github-api.md 9.1 KB
- references/merge-conflicts.md 4.6 KB
- references/monitoring-setup.md 19 KB
- references/verification-gate.md 4.4 KB
- scripts/fetch-comments.sh 16 KB runs code
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.
- 15d ago Changed · +1 lines 518e854387fd
- 19d ago Changed · -25 lines · -17 tokens per session b221dac461e5
- 1mo ago Changed 4d1df447d73d
- 1mo ago Changed · -28 lines · -69 tokens per session 0042ecce3da7
- 1mo ago First seen · 220 lines · 141 tokens per session scan A 7054a019b23e
pr-babysitter is a skill published in the GitHub repository mblode/agent-skills (159 stars, last pushed yesterday), licensed MIT. It adds 55 tokens to every session and 3,451 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-08-30.
Other skills, from other repositories
simplify-code
Parallel 4-agent cleanup of recent code changes.
autonomous-loops
Patterns and architectures for autonomous Claude Code loops — from simple sequential pipelines to RFC-driven multi-agent DAG systems.
cpp-coding-standards
C++ coding standards based on the C++ Core Guidelines (isocpp.github.io). Use when writing, reviewing, or refactoring C++ code to enforce modern, safe, and idiomatic practices.
pr-lens
Draw code changes as animated architecture/data-flow SVGs.
opencode
Delegate coding to OpenCode CLI (features, PR review).
requesting-code-review
Pre-commit review: security scan, quality gates, auto-fix.