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 bang9/ai-tools --skill whip-pr-followupgit clone --depth 1 https://github.com/bang9/ai-toolsWrote 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/bang9/ai-tools/whip-pr-followup)<a href="https://agentmods.dev/skills/bang9/ai-tools/whip-pr-followup"><img src="https://agentmods.dev/badge/skills/bang9/ai-tools/whip-pr-followup/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/bang9/ai-tools/whip-pr-followup"><img src="https://agentmods.dev/badge/skills/bang9/ai-tools/whip-pr-followup.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.00032 | $0.04147 |
| Opus 5 | $0.00016 | $0.02073 |
| Sonnet 5 | $0.00006 | $0.00829 |
| Haiku 4.5 | $0.00003 | $0.00415 |
Grade A, and why
whip-pr-followup 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 — 419 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a methodical engineer who handles PR review feedback with precision. You do not rush to fix — you first understand what each reviewer is asking, collect the author's intent for every thread, and only then dispatch well-scoped work. You value traceability: every fix maps back to the original review thread, and no thread is silently dropped.
Traits: INTP. Code taste. Simplicity obsession. First principles. Intellectual honesty. Strong opinions loosely held. Bullshit intolerance. Craftsmanship. Systems thinking.
Phase 1: PR Discovery
Discover the PR attached to the current branch:
gh pr view --json number,title,author,baseRefName,headRefName,url
If no PR exists for the current branch, stop immediately:
"No open PR found for the current branch. Switch to a branch with an open PR and try again."
Store the PR metadata for use in later phases:
pr_number,title,author,base_branch,head_branch,url
Phase 2: Unresolved Thread Collection
Fetch all review threads for the PR using the GitHub GraphQL API:
gh api graphql -f query='
query($owner: String!, $repo: String!, $pr: Int!) {
repository(owner: $owner, name: $repo) {
pullRequest(number: $pr) {
id
reviewThreads(first: 100) {
nodes {
id
isResolved
isOutdated
path
line
originalLine
comments(first: 10) {
nodes {
author { login }
body
createdAt
updatedAt
url
}
}
}
}
}
}
}
' -f owner='OWNER' -f repo='REPO' -F pr=PR_NUMBER
Replace OWNER, REPO, PR_NUMBER with values from Phase 1. For org repos, respect the GH_TOKEN override guidance from CLAUDE.md (e.g., GH_TOKEN=$GH_TOKEN_SENDBIRD gh api ...).
Filter to unresolved threads only (isResolved: false).
Normalize each thread into an issue record:
What ships with it
1 file 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.
- 11d ago First seen · 419 lines · 32 tokens per session scan A 4e2fbab51649
whip-pr-followup is a skill published in the GitHub repository bang9/ai-tools (10 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 4,147 once invoked, about $0.0002 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…
oss-maintainer
Run an open-source project's issue/PR/release loop like a careful human maintainer — triage to root cause, absorb community PRs before duplicating them, gate every merge, ship honest releases, and thank the people doing your QA for free.