A workflow for reviewing another person's pull request, which is a proposed code change awaiting review. It fetches the change, analyzes it, drafts comments, and can post them after approval.

Use it to inspect remote pull requests, identify issues, prepare review comments, and publish approved comments.

It brings the pull request context and review findings together while keeping comment posting under the user's control.

pr-patrol — Skill for Claude Code by sandsower

Install

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.

Any agent

npx skills add sandsower/beislid --skill pr-patrol

Clone the repo

git clone --depth 1 https://github.com/sandsower/beislid

Made for: Claude Code.

Or install beislid, the plugin that ships this one along with the rest of its 21 skills.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/sandsower/beislid/pr-patrol.svg)](https://agentmods.dev/skills/sandsower/beislid/pr-patrol)

Your own site

<a href="https://agentmods.dev/skills/sandsower/beislid/pr-patrol"><img src="https://agentmods.dev/badge/skills/sandsower/beislid/pr-patrol.svg" alt="Measured on agentmods" height="20"></a>

Per session 69 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,781 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.01781
Opus 5	$0.00034	$0.00890
Sonnet 5	$0.00014	$0.00356
Haiku 4.5	$0.00007	$0.00178

Measured 7d ago against content hash a8f0ce3211cd, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

pr-patrol 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 7d 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.

skills/pr-patrol/SKILL.md · 214 lines

How it starts

The opening of the file, as written. The whole thing — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.

PR Patrol

Review someone else's pull request and optionally post approved review comments. This is an inbound review workflow built around the side-effect-free review contract.

Boundary:

review inspects a diff and returns findings.
pr-patrol fetches PR context, decides with the user which findings are worth posting, drafts comments, and performs posting side effects only after approval.

Use this for:

Reviewing another person's GitHub/GitLab/etc. PR
Turning review-contract findings into human-approved PR comments
Running a fresh-eyes pass on a remote PR before posting comments
Security-sensitive inbound reviews where multiple reviewers may be worth the cost

Do not use this for:

Reviewing your own local diff before PR handoff — use review, fresh-eyes, or ready-for-review
Addressing feedback on your own PR — use review-response
Interactive walkthroughs of your own changes — use walk-the-diff
Posting comments without explicit user approval

Preflight

Before touching external systems, establish capabilities and print them to the user.

Resolve:

PR URL or host/owner/repo/number. If the user did not supply one, default to the PR for the current branch — try gh pr view --json number,url,author,headRefName,state (or the host equivalent) before asking. Only prompt the user if no PR is associated with the current branch, or if the current branch's author is the user themselves (pr-patrol is for inbound review, not your own PRs).
PR host tooling available in this session (gh, glab, MCP tool, API client, or paste-only)
Whether inline comments are supported by the available tool
Whether the user wants comment drafts only or actual posting

Example capability table:

pr-patrol preflight
  pr:              <url>
  host:            github / gitlab / other / paste
  fetch_diff:      gh / glab / mcp / paste        ✓
  inline_comments: yes/no                         ✓
  post_comments:   yes/no                         ✓

Read the full file on GitHub · 214 lines

Changes

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.

7d ago First seen · 214 lines · 69 tokens per session scan A a8f0ce3211cd

Subscribe to this mod's changes

pr-patrol is a skill published in the GitHub repository sandsower/beislid (10 stars, last pushed 7d ago), licensed MIT. It adds 69 tokens to every session and 1,781 once invoked, about $0.0003 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.

Code review Git and workflow

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.

prisma/orm · 38 tokens

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.

Gentleman-Programming/engram · 37 tokens

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…

nicknisi/dotfiles · 68 tokens

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…

daymade/claude-code-skills · 133 tokens

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…

umputun/revdiff · 248 tokens

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.

tldraw/tldraw · 53 tokens