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 sonichi/sutando --skill pr-watchgit clone --depth 1 https://github.com/sonichi/sutandoWrote 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/sonichi/sutando/pr-watch)<a href="https://agentmods.dev/skills/sonichi/sutando/pr-watch"><img src="https://agentmods.dev/badge/skills/sonichi/sutando/pr-watch/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/sonichi/sutando/pr-watch"><img src="https://agentmods.dev/badge/skills/sonichi/sutando/pr-watch.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.00125 | $0.04245 |
| Opus 5.5 | $0.00050 | $0.01698 |
| Sonnet 5.5 | $0.00025 | $0.00849 |
| Haiku 4.5 | $0.00013 | $0.00424 |
Grade A, and why
pr-watch 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 today.
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 — 271 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pr-watch
Watches GitHub pull requests by event, not by polling. A Claude Code mod (a plugin of function
hooks) starts pr_watch.py run when the session starts; the runner keeps one
gh webhook forward per watched repo and prints one line per relevant event. Nothing polls
GitHub, and nothing expires the way a Monitor does at 30 minutes.
How an event reaches the session depends on whether a turn is running:
- Idle: the mod submits the event as a new prompt (
$.prompt.submit), which starts a turn. - Turn running: a submitted prompt would only wait for the turn to end, so the mod holds the
event and attaches it to the next tool result of the main loop (the tool call's
context, which the model reads right after that tool's output). Events still held when the turn ends are submitted together as one prompt. Subagents' tool calls never carry them.
When to use it
- "Re-review Alice's PRs whenever she pushes", "tell me when Bob's PR merges".
- "Ping me when someone requests my review on acme/widgets."
- "Keep an eye on every PR I've reviewed there, whoever wrote it."
- Any standing PR watch that should survive past one Monitor window.
Not for one-off checks of a single PR: read it with gh pr view instead.
Events forwarded
Per watched repo (config.json), filtered by pr_watch.py:
| Event | Forwarded when | Line |
|---|---|---|
pull_request opened, synchronize, reopened, ready_for_review, closed |
the PR author is a watched --author (* = anyone) |
PR_EVENT o/r#N <action> author=… head=<sha8> merged=true|false reason=author |
pull_request synchronize, reopened, ready_for_review, closed |
the watch has --reviewed and one of the --me logins has submitted a review on the PR, whoever wrote it |
PR_EVENT o/r#N <action> author=… head=<sha8> merged=… reason=reviewed |
pull_request review_requested |
the requested reviewer is one of the --me logins, on any PR in the repo |
PR_EVENT o/r#N review_requested reviewer=… author=… head=… |
pull_request_review submitted |
on a watched author's PR, by someone other than the --me logins (the owner's own review echoing back is dropped, though it still marks the PR reviewed) |
PR_EVENT o/r#N review_submitted by=… state=approved|changes_requested|commented author=… head=… |
pull_request_review dismissed |
the dismissed review is by one of the --me logins, on any PR in the repo |
PR_EVENT o/r#N review_dismissed reviewer=… author=… head=… |
What ships with it
8 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.
- today First seen · 271 lines · 125 tokens per session scan A a58c96c9128d
pr-watch is a skill published in the GitHub repository sonichi/sutando (401 stars, last pushed today), licensed MIT. It adds 125 tokens to every session and 4,245 once invoked, about $0.0005 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-31.
Other skills, from other repositories
flag-cleanup
Weekly reusable-session feature-flag cleanup for {{targetrepo}}. Inventories every feature flag, classifies each as fully rolled out, long dead, partial rollout, or active experiment, removes the flag and the dead branch it guards on an isolated branch when the suite is green, and opens a PR — never touching a flag…
vellum-github-app-setup
Create and configure a GitHub App so the assistant can push commits, open PRs, and comment under its own bot identity. Use when the user wants the assistant to have its own GitHub identity, or when setting up git push access for the first time.
pr-sweep
Review every open PR with the code-reviewer agent and an adversarial review, apply the findings, and merge each one once CI is green. Use when asked to ship, sweep, or merge open PRs.
github-pr-workflow
Pull request lifecycle: create, review, merge, manage (gh CLI).
review-branch
Review the current branch: summarize changes, check plan compliance, and evaluate quality. Use for "review branch" or "summarize this branch".
create-pr
Create GitHub pull requests following team best practices - proper title format, description template, reviewers, labels, and linked issues.