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 samsantosb/ship-it/plugin install ship-itWrote 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/samsantosb/ship-it/watch-pr)<a href="https://agentmods.dev/skills/samsantosb/ship-it/watch-pr"><img src="https://agentmods.dev/badge/skills/samsantosb/ship-it/watch-pr/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/samsantosb/ship-it/watch-pr"><img src="https://agentmods.dev/badge/skills/samsantosb/ship-it/watch-pr.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.00078 | $0.02231 |
| Opus 5 | $0.00039 | $0.01115 |
| Sonnet 5 | $0.00016 | $0.00446 |
| Haiku 4.5 | $0.00008 | $0.00223 |
Grade A, and why
watch-pr 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 9d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: watch-pr
Watches one PR through the review cycle. Works with any Reviewer (external bot, humans, or both) and any Notifier. Respond to the invoking user in the conversation language (docs/agents/language.md; unset → their language) — but team-visible surfaces (thread replies, PR comments, notifications to shared channels) follow the language: setting in docs/agents/tracker.md when configured, same as cards: a shared thread must be readable by the whole team.
Load before acting: ${CLAUDE_PLUGIN_ROOT}/shared/workflow-context.md, ${CLAUDE_PLUGIN_ROOT}/shared/pr-flow.md, ${CLAUDE_PLUGIN_ROOT}/shared/card-format.md, ${CLAUDE_PLUGIN_ROOT}/shared/autonomy.md, and ${CLAUDE_PLUGIN_ROOT}/shared/guardrails.md — this skill pushes commits and acts on external content; the loading contract applies in full.
Step 0 — Resolve target and roles
- Target PR: argument (
#N, PR URL) or, with no argument, the current branch's PR (gh pr view --json number). No PR found → stop with the accepted shapes. - Target already merged or closed at invocation → skip straight to Step 4 (closing protocol). This is the supported way to finish cleanup after a watch that ended in silence missed the merge.
- Roles (workflow-context): Repo must have a remote (no remote → nothing to watch; say so). Reviewer from
docs/agents/reviewer.md— the bot login to wait for, or human-only. Notifier — a real channel enables async pings;chatmeans updates land here and only while this session lives (say that in the opening line). - Identify the card from the PR body/branch (for status transitions at the end).
Open with one line: Watching PR #<N> — applying reasonable review fixes, rerunning flaky CI once, notifying on approval/lock. Polling every 3 min.
Step 1 — Baseline
Snapshot via gh (or the repo platform's equivalent): gh pr view --json reviews,reviewDecision,mergeable,mergeStateStatus,headRefOid, gh pr checks, review threads (gh api repos/{o}/{r}/pulls/{n}/comments). Record lastPush = the head SHA + its timestamp, lastEventAt (the silence clock), and the dedupe state: processed comment ids, rerunAttempts[check:sha], lastNotifiedReviewId, notifiedLockReasons.
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.
- 9d ago First seen · 81 lines · 78 tokens per session scan A 45b21fc62518
watch-pr is a skill published in the GitHub repository samsantosb/ship-it (23 stars, last pushed 1mo ago), licensed MIT. It adds 78 tokens to every session and 2,231 once invoked, about $0.0004 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-30.
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.