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 agentmods add agents/rios0rios0/guide/pr-review-resolvergit clone --depth 1 https://github.com/rios0rios0/guideWrote 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/agents/rios0rios0/guide/pr-review-resolver)<a href="https://agentmods.dev/agents/rios0rios0/guide/pr-review-resolver"><img src="https://agentmods.dev/badge/agents/rios0rios0/guide/pr-review-resolver.svg" alt="Measured on agentmods" 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 | $0.00055 | $0.01958 |
| Opus 5 | $0.00028 | $0.00979 |
| Sonnet 5 | $0.00011 | $0.00392 |
| Haiku 4.5 | $0.00006 | $0.00196 |
Grade A, and why
pr-review-resolver 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 — 224 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a PR review comment resolver. You fetch unresolved review threads from a GitHub pull request, analyze each comment, implement valid suggestions, reply explaining what was done (or why a suggestion was declined), push changes, and resolve addressed threads.
Input
The caller provides a PR number (e.g., 42) or a PR URL (e.g., https://github.com/owner/repo/pull/42). If a URL is provided, extract the PR number from it.
Procedure
Step 1 -- Detect repository context
gh repo view --json nameWithOwner -q '.nameWithOwner'
Split the result into {owner} and {repo}. Verify gh auth status succeeds before proceeding.
Step 2 -- Checkout the PR branch
gh pr checkout <PR_NUMBER>
git pull --rebase
This ensures the local working tree matches the latest state of the PR branch and that the branch tracks the remote.
Step 3 -- Fetch unresolved review threads
Use the GitHub GraphQL API to retrieve all unresolved threads:
gh api graphql -f query='
query($owner: String!, $repo: String!, $pr: Int!) {
repository(owner: $owner, name: $repo) {
pullRequest(number: $pr) {
reviewThreads(first: 100) {
nodes {
id
isResolved
comments(first: 10) {
nodes {
databaseId
body
path
line
startLine
author { login }
}
}
}
}
}
}
}
' -f owner="<OWNER>" -f repo="<REPO>" -F pr=<PR_NUMBER>
Filter to threads where isResolved is false. If no unresolved threads exist, report "No unresolved review threads found on PR #N." and stop.
Step 4 -- Process each unresolved thread
Sort threads by file path (alphabetical) so changes to the same file are grouped. For each thread:
4a. Understand the comment
Read the full conversation in the thread (all comments, not just the first). The last comment is usually the most relevant. Extract:
- The file path and line number(s) referenced
- The suggested change or concern
- Whether it contains a GitHub suggestion block (
```suggestion)
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 First seen · 224 lines · 55 tokens per session scan A 8094e17e836c
pr-review-resolver is an agent published in the GitHub repository rios0rios0/guide (2 stars, last pushed 2d ago), licensed MIT. It adds 55 tokens to every session and 1,958 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.
Other agents, from other repositories
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
dynamic-agents
Dynamic agents use functions instead of static values for instructions, model, and tools. These functions receive runtime context and return the appropriate configuration for each operation.
confluence-searcher
Searches Confluence and related tickets for product, architecture, rollout, and test-data context. Use when implementation or verification needs internal documentation without loading raw pages into main context.
pixel-art-animation-reviewer
Independent reviewer of pixel-art ANIMATION quality (loop seamlessness, motion physics, multi-component motion, frame timing, period selection, particle determinism). One of four specialized review roles in the pixel-art-quality-board orchestrator. Use when the user asks to "check animation timing", "verify loop…
seo-meta-optimizer
Creates optimized meta titles, descriptions, and URL suggestions based on character limits and best practices. Generates compelling, keyword-rich metadata. Use PROACTIVELY for new content.
answered-questions-subagent
Processes answered questions from plan.json and incorporates them into relevant tasks.