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 resolve-pr-threadsgit 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/resolve-pr-threads)<a href="https://agentmods.dev/skills/dryvist/claude-code-plugins/resolve-pr-threads"><img src="https://agentmods.dev/badge/skills/dryvist/claude-code-plugins/resolve-pr-threads/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/resolve-pr-threads"><img src="https://agentmods.dev/badge/skills/dryvist/claude-code-plugins/resolve-pr-threads.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.00073 | $0.02376 |
| Opus 5.5 | $0.00029 | $0.00950 |
| Sonnet 5.5 | $0.00015 | $0.00475 |
| Haiku 4.5 | $0.00007 | $0.00238 |
Grade A, and why
resolve-pr-threads 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 13d 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 — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resolve PR Feedback (Orchestrator)
Processes all PR feedback by grouping related items, fixing each issue or replying with command output as proof, tagging every reply with its ledger marker, and finally resolving each finished thread with the canonical resolve mutation.
State warning: Thread IDs and resolution status change as reviews arrive. Re-fetch all open threads — cached thread lists from earlier are unreliable.
Usage
/resolve-pr-threads # Current branch PR
/resolve-pr-threads 142 # Specific PR
/resolve-pr-threads all # All open PRs with unaddressed feedback (sequential)
Rules
- See /gh-cli-patterns for canonical query shapes, mutation names, and placeholder convention
- Follow the PR feedback ledger for item IDs, exclusions, bot parsing, coverage reviews, and marker verification
- Run gh/git/jq commands directly via Bash — no scripts, no temp files
- Diagnose and fix errors when a reply fails — the reply must land in the thread
- When a reply fails: re-fetch the source item and its IDs; for inline replies, also re-fetch the thread, verify
databaseIdis numeric, checkgh auth status, then retry - Do not reply to review threads by posting top-level PR comments as a fallback; top-level comments are fine for general PR feedback but cannot be used to resolve specific review threads
Context inference: Infer owner/repo/PR from current git context, then substitute
these values for <OWNER>, <REPO>, <PR_NUMBER> placeholders per gh-cli-patterns:
owner=$(gh repo view --json owner --jq '.owner.login')
repo=$(gh repo view --json name --jq '.name')
number=$(gh pr view --json number --jq '.number')
Workflow
Step 1: Fetch Unresolved Threads and All PR Feedback
Run 1a–1d in parallel.
Step 1a: Fetch Unresolved Threads
Run the canonical fetch-threads query from /gh-cli-patterns.
Replace <OWNER>, <REPO>, <PR_NUMBER> before running.
What ships with it
2 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.
- 13d ago Changed · +16 lines · +2 tokens per session 9439dbd0c21a
- 15d ago Changed aaa9bd06c237
- 1mo ago Changed d275157c5ac3
- 1mo ago First seen · 210 lines · 71 tokens per session scan A b264e4288b21
resolve-pr-threads is a skill published in the GitHub repository dryvist/claude-code-plugins (3 stars, last pushed today), licensed Apache-2.0. It adds 73 tokens to every session and 2,376 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.
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…
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…
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".