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.
git clone --depth 1 https://github.com/acolomba/pi-claude-marketplaceWrote 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/commands/acolomba/pi-claude-marketplace/babysit-pr)<a href="https://agentmods.dev/commands/acolomba/pi-claude-marketplace/babysit-pr"><img src="https://agentmods.dev/badge/commands/acolomba/pi-claude-marketplace/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/commands/acolomba/pi-claude-marketplace/babysit-pr"><img src="https://agentmods.dev/badge/commands/acolomba/pi-claude-marketplace/babysit-pr.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.00057 | $0.01448 |
| Opus 5 | $0.00028 | $0.00724 |
| Sonnet 5 | $0.00011 | $0.00290 |
| Haiku 4.5 | $0.00006 | $0.00145 |
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 11d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Babysit PR
Take an already-open pull request and harden it in two phases: a local review-convergence loop, then a SonarQube pass once CI has analyzed the pushed head. The point is to hand a human reviewer a PR that already clears the automated bars, with the expensive review and fixing done in subagents rather than in this conversation's context.
Invoke this yourself after the PR exists ($ARGUMENTS is an optional PR number; default to the current branch's PR). It is safe to re-run — a clean PR converges to a no-op.
Phase 0 — Resolve the PR
Run gh pr view $ARGUMENTS --json number,headRefName,url,state. If there is no open PR for this branch, stop and say so — this command hardens an existing PR, it does not create one. Record the PR number and head branch.
Phase 1 — Review convergence (local, fast)
Converge the PR's diff to review-clean before Sonar even runs. One review pass is never enough — reviewers miss things, fixes introduce new problems, and the only way to know a fix worked is to review again — so this is a bounded loop:
- Scope. Review the PR's changes: the branch's commits versus its base (merge-base with
main) plus any uncommitted work. If there is nothing to review, skip to Phase 2. - Review. Run
/pr-review-toolkit:review-prover all applicable aspects. Its specialized reviewers run as subagents. It sorts findings into Critical (must fix), Important (should fix), Suggestions (advisory), and Strengths. - Triage. Separate Critical + Important (actionable now) from Suggestions (advisory — these never block finishing).
- Fix, one cause at a time. Address each Critical and Important finding at its root. Fix the actual defect; do not silence the reviewer with a blanket lint-disable or by deleting the test that caught it. After each fix, run the project's checks (
npm run checkand the pre-commit hooks) so a fix cannot quietly break the build, then commit it atomically. Never--no-verify. Delegate independent fixes to subagents. - Re-review. Return to step 2. The re-review is the point: it confirms the fixes landed and catches anything they introduced.
- Finish on advisory-only. When a review returns no Critical or Important findings, make one pass over the Suggestions — apply the ones that clearly improve the code, and note in one line why you leave the rest — then stop. Optionally run the
simplifyaspect as a final polish; the toolkit is built to run that once a change passes review.
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.
- 11d ago First seen · 63 lines · 57 tokens per session scan A e1ed43a28e71
babysit-pr is a command published in the GitHub repository acolomba/pi-claude-marketplace (23 stars, last pushed 2d ago), licensed MIT. It adds 57 tokens to every session and 1,448 once invoked, about $0.0003 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 commands, from other repositories
devkit.github.review-pr
Provides comprehensive GitHub pull request review with code quality, security, and best practices analysis. Use when reviewing a PR before merging.
speckit.spex.submit
Push and create PR for team review, with optional watch mode for CI monitoring.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
code-review
Code review for branch changes. Analyzes git diff between branches with multi-level depth (low/medium/high). Matches changes against task description. Returns structured report with severity levels and verdict.
advanced-code-review-context
Advanced Code Review Phase 2: Context Analysis - load previous reviews, PR history, declined items.