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/a1f/agent-templates/pr-babysitnpx skills add a1f/agent-templates --skill pr-babysitgit clone --depth 1 https://github.com/a1f/agent-templatesWrote 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/a1f/agent-templates/pr-babysit)<a href="https://agentmods.dev/skills/a1f/agent-templates/pr-babysit"><img src="https://agentmods.dev/badge/skills/a1f/agent-templates/pr-babysit.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.1 | $0.00059 | $0.06880 |
| Opus 5 | $0.00030 | $0.03440 |
| Sonnet 5 | $0.00012 | $0.01376 |
| Haiku 4.5 | $0.00006 | $0.00688 |
Grade A, and why
pr-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 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 — 500 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Babysit
Automate the post-PR feedback loop. Polls for new review comments, fixes them, checks CI, resolves merge conflicts, pushes, and repeats until the PR is clean or max rounds are exhausted.
/pr-babysit [--interval 3m] [--max-rounds 5]
Loop:
1. Fetch PR comments & reviews + CI status + mergeable status (parallel)
2. Filter for unresolved/new comments since last check, split by human vs bot
3. Human comments → trade-off assessment + user decision gate (AskUserQuestion or worksheet)
4. Fix all actionable comments per gate decisions (bot: auto; human: per decision), run quick gates once
5. Reply to question comments (bot: auto; human: only approved reply, in parallel)
6. If CI failing → read logs, fix failures
7. If conflicts → rebase/merge main and resolve conflicts
8. If changes were made → commit & push, refresh the PR explainer, reset idle counter
9. If nothing left to fix AND CI green AND no conflicts AND no undecided human comments → final explainer refresh, then [READY TO MERGE]
10. Otherwise → wait interval, repeat
Prerequisites
The gh CLI must be authenticated with repo scope. The jq command must be available.
Arguments
Parse arguments from the user's message. All are optional:
| Arg | Default | Example |
|---|---|---|
--interval=DURATION |
3m |
--interval=5m |
--max-rounds=N |
5 |
--max-rounds=10 |
Phase 0: Setup
0a. Detect Current PR and Repo Info
Fetch PR data and repo info in parallel:
CURRENT_BRANCH=$(git rev-parse --abbrev-ref HEAD)
# Parallel: PR info + repo info
PR_JSON=$(gh pr view --json number,url,baseRefName,mergeable,mergeStateStatus,createdAt)
REPO_INFO=$(gh repo view --json owner,name)
If no PR exists for the current branch, stop and tell the user to create one first (suggest /make-pr or /pr-make).
Extract:
PR_NUMBER=$(echo "$PR_JSON" | jq -r '.number')
PR_URL=$(echo "$PR_JSON" | jq -r '.url')
BASE_BRANCH=$(echo "$PR_JSON" | jq -r '.baseRefName')
PR_CREATED_AT=$(echo "$PR_JSON" | jq -r '.createdAt')
OWNER=$(echo "$REPO_INFO" | jq -r '.owner.login')
REPO=$(echo "$REPO_INFO" | jq -r '.name')
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 · 500 lines · 59 tokens per session scan A 7c63f713e22a
pr-babysit is a skill published in the GitHub repository a1f/agent-templates (2 stars, last pushed 5d ago), licensed MIT. It adds 59 tokens to every session and 6,880 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…