Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add bendrucker/claude/plugin install pull-requestWrote 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/bendrucker/claude/follow-up)<a href="https://agentmods.dev/skills/bendrucker/claude/follow-up"><img src="https://agentmods.dev/badge/skills/bendrucker/claude/follow-up/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/bendrucker/claude/follow-up"><img src="https://agentmods.dev/badge/skills/bendrucker/claude/follow-up.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.00069 | $0.01569 |
| Opus 5.5 | $0.00028 | $0.00628 |
| Sonnet 5.5 | $0.00014 | $0.00314 |
| Haiku 4.5 | $0.00007 | $0.00157 |
Grade A, and why
pull-request:follow-up 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Follow-Up
Follow up on review feedback for: $ARGUMENTS
Parse the URL and flags from $ARGUMENTS. GitHub is primary: work through gh, mcp__github, and github:* skills directly. Delegate all GitLab behavior to gitlab:merge-request (no glab calls).
Arguments
--auto: autonomously triage bot threads, looping until the acceptance bar is met (see The Autonomous Loop). Human threads stay gated.--include-human-nits: under--auto, also act on human threads, but only trivial high-confidence changes (typos, renames, one-liners). Off by default.--local [base]: run the bot loop pre-push through the reviewer's CLI instead of PR threads, against the branch's unmerged commits (see Local Mode). The optional base overrides what the review runs against. No PR is involved, sopr-urland the other flags don't apply.
With no flags, run the gated default.
Default Workflow (Gated)
Without --auto, stay read-only: fetch, classify, draft, check with me before posting or resolving.
Fetch all resolvable threads (resolved and unresolved) via github:pr-comments (--role author) or gitlab:merge-request, then classify:
- Unresolved / no reply
- Unresolved / replied
- Resolved / with reply
- Resolved / silent: resolved with no author reply; flag these, they hide context
For unresolved threads, diff the comment's creation date against HEAD to see whether later commits addressed the feedback. Draft replies per replies.md.
The Autonomous Loop
With --auto, drive bot threads to closure without asking. Partition threads with each provider's --bots filter (github:pr-comments, gitlab:merge-request): fetch once filtered for the bot set, once unfiltered to see the human threads you're leaving alone. Add reviewers per reviewers.md.
Triage each bot thread:
- Actionable → fix in the working tree, batching across threads. For a straightforward fix (test coverage, a rename, an obvious guard), acknowledge with a thumbs up reaction rather than a fleshed-out reply (see
github:pr-comments, Reactions) - Noise / false positive → reply with a one-line reason and resolve, or thumbs down a clearly wrong bot comment
- Unsure → collect to escalate; don't guess
What ships with it
4 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.
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 · 93 lines · 69 tokens per session scan A d23023f95181
pull-request:follow-up is a skill published in the GitHub repository bendrucker/claude (18 stars, last pushed today), licensed MIT. It adds 69 tokens to every session and 1,569 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-09-03.
Other skills, from other repositories
pr-review
Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.
phx-pr-review
Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.
signing-preflight
Before the first commit of a session, check that commit signing will work — the key is loaded and unlocked — and ask the operator to unlock it once, up front, instead of discovering it after a hundred unsigned commits. Never disables signing silently, never re-signs history without asking. Use at the start of…
pr-review
Review pull requests and Git diffs with Graph-It-Live risk, breaking-change, dependency-impact, cycle, unused-export, and test-candidate evidence. Use when asked to review a PR, inspect a diff, assess merge risk, check a branch before merging, create a Graph-It-Live review gate, or explain review-pr results. Trigger…
loop-gh-pr
A recipe for a scheduled GitHub pull-request watcher. It checks open pull requests for new activity and prepares read-only review drafts without posting comments or merging anything.
review
Structured code review with parallel audit agents, confidence-scored triage, and optional auto-fix. Examines uncommitted changes, staged diffs, commit ranges, or specific paths. Produces a tiered report (MUST-FIX / RECOMMENDED / NIT) backed by evidence, then optionally applies fixes with verification.