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 dryvist/claude-code-plugins --skill finalize-prgit clone --depth 1 https://github.com/dryvist/claude-code-pluginsWrote 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/dryvist/claude-code-plugins/finalize-pr)<a href="https://agentmods.dev/skills/dryvist/claude-code-plugins/finalize-pr"><img src="https://agentmods.dev/badge/skills/dryvist/claude-code-plugins/finalize-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/dryvist/claude-code-plugins/finalize-pr"><img src="https://agentmods.dev/badge/skills/dryvist/claude-code-plugins/finalize-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.00063 | $0.03479 |
| Opus 5.5 | $0.00025 | $0.01392 |
| Sonnet 5.5 | $0.00013 | $0.00696 |
| Haiku 4.5 | $0.00006 | $0.00348 |
Grade A, and why
finalize-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 4d 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 — 283 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Finalize PR
FULLY AUTOMATIC - Fully automates PR finalization: monitor, fix, prepare for merge. Assumes PR already exists.
No manual intervention required. For manual review-focused workflows, use /review-pr.
State warning: Automated reviewers (CodeQL, Copilot, AI reviews) post asynchronously. CI may have re-run. Merge conflicts may have appeared. Re-fetch live PR state from Step 1.
Goal and done-criteria
Goal: drive every targeted PR (single, all in-repo, or org) to
merge-ready without manual intervention — CI green, CodeQL clean, all PR
feedback answered, no conflicts, code simplified, metadata current — by
taking direct action on whatever blocks it, never by reporting the blocker
back.
Done when, for every targeted PR: Phase 3's live-API gate passes (re-run on
every invocation — "mergeable" means git-conflict-free only, not fully
unblocked); /resolve-pr-threads and /resolve-codeql found nothing left
to fix; /simplify ran once after all other fixes (Step 2.3.5 — pre-push
simplification is /ship's job, not this skill's); local linters and tests
pass; title/description/linked-issues were regenerated via a haiku subagent
before reporting ready; bot-authored PRs (dependabot, release-please,
claude, github-actions, etc.) were never filtered out; org mode never
crossed the org boundary the current repo implies; and, on a Git Flow repo,
the post-merge develop→main promotion via /promote-release was added
to the active session checklist as mandatory, not optional.
Phase 1: PR Discovery and Targeting
Steps 1.1–1.4 run sequentially.
1.1 Parse Argument
| Argument | Mode | Target |
|---|---|---|
| (none) | Current branch | Single PR on current branch |
42 |
Single PR | PR #42 |
all |
Repo-wide | All open PRs in current repo |
org |
Org-wide | All open PRs across all repos in current org |
1.2 Discover PRs
- Single/current-branch: Resolve PR number from current branch, proceed to Phase 1.5.
- Repo-wide (
all): List all open PRs (limit 50) with number, title, author, headRefName. - Org-wide (
org): Enumerate repos, list open PRs per repo (limit 50 each, 50 total cap), includerepositoryfield.
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.
- 4d ago Changed · +23 lines ada760bf2bea
- 6d ago Changed 5995d73ce3a0
- 11d ago Changed · -11 lines 8aca92e36fdf
- 24d ago Changed · -22 lines 2b34caa721fe
- 1mo ago First seen · 293 lines · 63 tokens per session scan A 56b11970f719
finalize-pr is a skill published in the GitHub repository dryvist/claude-code-plugins (3 stars, last pushed today), licensed Apache-2.0. It adds 63 tokens to every session and 3,479 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
review-pr
Multi-agent PR review with four modes (review, re-review, self-review, address-feedback) - spawns parallel subagents, saves diff to /tmp for context efficiency, supports file exclusion patterns.
code-review-loop
Use when opening a PR for review or when receiving review feedback. Activate for keywords like "code review", "PR review", "request review", "review feedback", "address comments", "reviewer said". Covers both ends of the loop: preparing a reviewable PR and acting on feedback rigorously. Always engage with every…
prkit
Draft and open a GitHub pull request from your branch, with title, summary, and test plan written from the actual commits and diff, then created with the gh CLI, embedding verifykit proof artifacts inline when a bundle is present. Use when the user asks to open a PR, says "create a pull request", "raise a PR", "submit…
mergekit
Take an open GitHub PR and set it up for review on your machine (worktree, project running, review pack), then merge it once you say so, or service review feedback on a PR you authored. Use when you say "pull PR #34 down so I can test it", "merge PR #34", "address the review comments on my PR", or "my PR is red, fix…
contribute
Complete contribution workflow using git-town. Create branch → commit → PR → ship. Preflight at every step.
commit-review
Review git commits for quality, clarity, and best practices before pushing. Checks commit message format, diff size, test coverage signals, and common mistakes. Use when reviewing commits, before pushing, when asked to "check my commits", "review changes", or "is this ready to push".