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 ao92265/claude-code-playbook --skill pr-batch-reviewgit clone --depth 1 https://github.com/ao92265/claude-code-playbookWrote 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/ao92265/claude-code-playbook/pr-batch-review)<a href="https://agentmods.dev/skills/ao92265/claude-code-playbook/pr-batch-review"><img src="https://agentmods.dev/badge/skills/ao92265/claude-code-playbook/pr-batch-review.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.00064 | $0.00360 |
| Opus 5 | $0.00032 | $0.00180 |
| Sonnet 5 | $0.00013 | $0.00072 |
| Haiku 4.5 | $0.00006 | $0.00036 |
Grade A, and why
pr-batch-review 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 8d 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.
What it actually says
PR Batch Review
Review and manage multiple open PRs in a single consolidated pass.
Steps
-
Verify git credentials work:
gh auth status- If credentials fail, STOP and report — do not proceed
-
List all open PRs:
gh pr list --state open- Show count and titles
-
For each PR (limit to 6 max to avoid rate limits):
- Check CI status:
gh pr checks <number> - Review diff:
gh pr diff <number> - Note any issues: failing tests, security concerns, style problems
- Check CI status:
-
Present a consolidated summary table:
PR # Title CI Status Issues Found Recommendation -
STOP and ask which PRs to merge — do not auto-merge anything
Important
- Do NOT merge any PR without explicit user approval
- Do NOT spawn more than 3 parallel agents for PR reviews
- If a PR has failing checks, recommend investigating before merging
- Flag any PRs with security-sensitive changes for closer 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.
- 8d ago First seen · 44 lines · 64 tokens per session scan A cc29e1f036b5
pr-batch-review is a skill published in the GitHub repository ao92265/claude-code-playbook (10 stars, last pushed 21d ago), licensed MIT. It adds 64 tokens to every session and 360 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
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
engram-branch-pr
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
verify-behavior
Verify or reproduce visible product behavior by driving the real UI with pi-computer-use's checked tools, requiring verified expect postconditions and durable state evidence for meaningful UI flows. Use when triage needs visual reproduction, implementation needs behavioral proof, review needs interactive confirmation…
github-contributor
End-to-end playbook for shipping high-quality pull requests to open-source projects you don't maintain — discovery, CONTRIBUTING compliance, PR-size check, minimal-diff implementation, PR description with AI-assisted disclosure, conflict resolution, and post-submission maintainer interaction. Use whenever creating…
revdiff
Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…
write-pr
Reference standards for writing pull request titles and descriptions in the tldraw repository, plus the pre-flight comment sweep over the diff. Use as supporting guidance when another skill or workflow needs PR content standards, not as the user-facing create/update PR workflow.