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 Smirnov-Labs/claude-skills --skill watching-pr-bot-reviewsgit clone --depth 1 https://github.com/Smirnov-Labs/claude-skillsWrote 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/smirnov-labs/claude-skills/watching-pr-bot-reviews)<a href="https://agentmods.dev/skills/smirnov-labs/claude-skills/watching-pr-bot-reviews"><img src="https://agentmods.dev/badge/skills/smirnov-labs/claude-skills/watching-pr-bot-reviews/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/smirnov-labs/claude-skills/watching-pr-bot-reviews"><img src="https://agentmods.dev/badge/skills/smirnov-labs/claude-skills/watching-pr-bot-reviews.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.00177 | $0.01634 |
| Opus 5.5 | $0.00071 | $0.00654 |
| Sonnet 5.5 | $0.00035 | $0.00327 |
| Haiku 4.5 | $0.00018 | $0.00163 |
Grade A, and why
watching-pr-bot-reviews 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Watching PR bot reviews
Never hand-roll a poller for PR bots — no until gh api …; do sleep 30; done, no
wait-codex.sh. A 2026-10-16 transcript audit found 365 such waits across ~30 sessions
(~800K output tokens, ~133M context tokens re-read), re-written after every push, keyed on
five different "done" signals — and three PRs merged code Codex never reviewed.
Use prbots, which ships in this skill's bin/ and is on PATH wherever skillsync installed
it (otherwise run bin/prbots from this skill's base directory).
| Situation | Run | How |
|---|---|---|
| Just opened the PR | prbots wait <PR> |
Bash run_in_background: true |
| Just pushed to an open PR | prbots wait <PR> --trigger |
Bash run_in_background: true |
| "What did the bots say?" / before merging | prbots <PR> |
foreground, ~6-line digest |
<PR> = number or PR URL (default: the current branch's PR); add -R owner/repo when cwd
isn't the repo. After starting a background wait, do not poll it — no sleep, no tailing
its output, no re-checking with gh. You are notified when it exits; its output is the digest.
This skill reads and waits; it never commits or pushes. To drive a PR to clean (fix → push →
wait, repeated), the user runs /pr-fix.
Why --trigger after a push
Neither bot re-reviews a push by itself: Codex runs on PR open / ready-for-review / an
@codex review comment; the SAR on open / ready-for-review / an @architect-run comment,
never on push. --trigger posts those comments once per HEAD, only when no review of HEAD
is running or already requested. Without it, wait exits 2 within ~75s once it is clear no
review will start, instead of sitting out the timeout. If your checkout is the pushed PR
branch, wait first waits for GitHub to show that SHA, so a wait started right after
git push never reads the previous commit's review.
Reading the result
PR #42 · acme/webapp · fix/session-timeout · HEAD 56d1b7b · OPEN
codex ✗ 1 finding(s) @56d1b7b (P2×1) · PR opened
P2 src/auth/session.ts:51 Expire refresh tokens on logout
sar ✓ No issues found · severity 0/4 · blockers false · 01:22Z
ci · no checks
verdict FIX — codex P2 src/auth/session.ts:51
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.
- 5d ago First seen · 93 lines · 177 tokens per session scan A d063341c0594
watching-pr-bot-reviews is a skill published in the GitHub repository Smirnov-Labs/claude-skills (6 stars, last pushed 2d ago), licensed MIT. It adds 177 tokens to every session and 1,634 once invoked, about $0.0007 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-10-17.
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.
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
review-delta
Review only changes since last commit using impact analysis. Token-efficient delta review with automatic blast-radius detection.
github-contributor
A step-by-step guide for contributing code, tests, documentation, or build changes to open-source projects you do not maintain. It explains how to prepare a pull request that follows the project’s rules and is easier for maintainers to review.
hero-diff-highlight
A dark code editor reveals a red deletion then a green addition with a soft pulse. Function: PR / code-change explainer.
git-pr-workflows-git-workflow
Guide changes through code checks, testing, commits, and pull request preparation. Use when coordinating a complete Git workflow and verifying readiness for collaboration.