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 hoblin/claude-ruby-marketplace --skill review-prgit clone --depth 1 https://github.com/hoblin/claude-ruby-marketplaceWrote 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/hoblin/claude-ruby-marketplace/review-pr)<a href="https://agentmods.dev/skills/hoblin/claude-ruby-marketplace/review-pr"><img src="https://agentmods.dev/badge/skills/hoblin/claude-ruby-marketplace/review-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/hoblin/claude-ruby-marketplace/review-pr"><img src="https://agentmods.dev/badge/skills/hoblin/claude-ruby-marketplace/review-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.00039 | $0.03824 |
| Opus 5 | $0.00019 | $0.01912 |
| Sonnet 5 | $0.00008 | $0.00765 |
| Haiku 4.5 | $0.00004 | $0.00382 |
Grade A, and why
review-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 2d 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 — 306 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Input Format
/rpi:review-pr [mode] [PR] [additional instructions]
- mode (optional):
review(default),re-review,self-review, oraddress-feedback - PR: PR number or link (required)
- additional instructions (optional): file exclusions, focus areas, or any custom guidance
Examples:
/rpi:review-pr #1234
/rpi:review-pr re-review #1234
/rpi:review-pr self-review #1234
/rpi:review-pr address-feedback #1234
/rpi:review-pr #1234 exclude config/locales and .yml files
/rpi:review-pr re-review #1234 skip rails guru because it is not a rails project
Process
Your role is orchestrator and judge, not doer. You collect artifacts, delegate analysis to subagents, and apply judgment to their output. The subagents read the code and comments — you decide what to do about their findings.
Steps are sequential — later steps depend on earlier results. Complete each step and wait for its results before starting the next. Skipping ahead without subagent results means the judgment layer in "Step 6: Judge Findings" has nothing to work with. Only parallelize where explicitly marked (e.g., "spawn in parallel").
Step 1: Gather PR Metadata
gh pr view <PR_NUMBER> --json number,title,body,url,headRefName,baseRefName
If re-review or address-feedback mode is activated, also save all existing review feedback to /tmp/:
Do not read these files — pass them to subagents by path only. The subagents will read and analyze the content.
# Review verdicts and bodies (APPROVED, CHANGES_REQUESTED, COMMENTED)
gh api repos/<OWNER>/<REPO>/pulls/<PR_NUMBER>/reviews \
--jq '[.[] | {id, state, body, html_url, commit_id, submitted_at, author_association, user: .user.login}]' \
| tee /tmp/pr_<NUMBER>_reviews.json | jq length
# Inline review comments on specific diff lines
gh api repos/<OWNER>/<REPO>/pulls/<PR_NUMBER>/comments \
--jq '[.[] | {id, pull_request_review_id, body, path, line, start_line, side, diff_hunk, commit_id, created_at, author_association, in_reply_to_id, user: .user.login}]' \
| tee /tmp/pr_<NUMBER>_inline_comments.json | jq length
# Conversation-level comments
gh api repos/<OWNER>/<REPO>/issues/<PR_NUMBER>/comments \
--jq '[.[] | {id, body, html_url, created_at, updated_at, author_association, user: .user.login}]' \
| tee /tmp/pr_<NUMBER>_conversation.json | jq length
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.
- 2d ago First seen · 306 lines · 39 tokens per session scan A d2f5d7adafed
review-pr is a skill published in the GitHub repository hoblin/claude-ruby-marketplace (37 stars, last pushed 2d ago), licensed MIT. It adds 39 tokens to every session and 3,824 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-09-07.
Other skills, from other repositories
finalize-pr
Automatically finalize pull requests for merge by resolving CodeQL violations, review threads, merge conflicts, and CI failures. Handles single PR (current branch or by number), all open PRs in the repo, or all open PRs across the org. Includes bot-authored PRs in all modes.
resolve-pr-threads
Orchestrates resolution of GitHub PR review threads AND reads recent non-thread PR comments (top-level + review bodies) by grouping related feedback, processing each group sequentially inline with superpowers:receiving-code-review, and resolving threads via GraphQL. Use when you need to batch-process review feedback…
pr-sweep
Use when open pull requests have piled up in one repo or across an owner's repos and you want the pile triaged and driven toward zero in one pass — including when most of them are bot- or teammate-authored. Also use when a sweep must run many repos in parallel without racing approvals or flooding CI.
trigger-ai-reviews
Use when asked to "trigger AI reviews", "request AI re-reviews", "get Claude/Gemini/Copilot to review my PR", "re-review this PR", or trigger review-request comments on a PR. Triggers all three AI reviewers by default, or specific ones when named.
breaking-changes
Detects breaking changes between two git refs and generates a migration guide.
pr-create
Creates a pull request from the current branch with a generated title and description.