Borrowing it
Nothing to install: this file belongs to WolframResearch/AgentTools. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/WolframResearch/AgentTools/main/.claude/skills/review-pr-comments/SKILL.mdgit clone --depth 1 https://github.com/WolframResearch/AgentToolsWrote 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/wolframresearch/agenttools/review-pr-comments)<a href="https://agentmods.dev/skills/wolframresearch/agenttools/review-pr-comments"><img src="https://agentmods.dev/badge/skills/wolframresearch/agenttools/review-pr-comments/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/wolframresearch/agenttools/review-pr-comments"><img src="https://agentmods.dev/badge/skills/wolframresearch/agenttools/review-pr-comments.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00066 | $0.01213 |
| Opus 5.5 | $0.00026 | $0.00485 |
| Sonnet 5.5 | $0.00013 | $0.00243 |
| Haiku 4.5 | $0.00007 | $0.00121 |
Grade A, and why
review-pr-comments 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 1mo 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Address Pull Request Review Comments
Fetch unresolved review comments on a GitHub PR, investigate each one, fix valid issues, reply, and resolve the threads.
Bundled Scripts
This skill includes two helper scripts in scripts/:
| Script | Purpose |
|---|---|
get-unresolved-comments.sh |
Fetches only unresolved review threads via GraphQL — returns thread IDs, file paths, line numbers, and comment bodies |
resolve-thread.sh |
Resolves a single review thread by its node ID (PRRT_...) via the resolveReviewThread GraphQL mutation |
GitHub's REST API does not expose thread resolution at all — these scripts use gh api graphql because it's the only programmatic path.
Determine the PR and Repository
Use $ARGUMENTS as the PR number if provided. Otherwise, detect it from the current branch:
gh pr view --json number,title,url,state --jq '{number, title, url, state}'
If no PR is found, ask the user for the PR number.
Get the owner and repo name if unknown (the scripts need them as separate arguments):
gh repo view --json owner,name --jq '[.owner.login, .name]'
Fetch Unresolved Comments
Use the bundled script to get only unresolved review threads:
bash <skill-path>/scripts/get-unresolved-comments.sh OWNER REPO PR_NUMBER
This returns a JSON array of unresolved threads. Each thread contains:
id— the thread node ID (PRRT_...), needed to resolve the thread laterpath— file path the comment is online— line numbercomments— array of{ body, author.login, createdAt, databaseId }
Also check for top-level issue-style comments (these live in a separate API and aren't part of review threads):
gh pr view <pr-number> --comments --json comments
Skip bot-generated overview comments that list changed files without raising specific issues. Focus on comments that raise an actionable concern.
If there are no unresolved threads and no new issue-style comments, report that to the user and stop.
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.
- 1mo ago First seen · 136 lines · 66 tokens per session scan A 5c352161ffa0
review-pr-comments is a skill published in the GitHub repository WolframResearch/AgentTools (96 stars, last pushed yesterday), licensed MIT. It adds 66 tokens to every session and 1,213 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-30.
Other skills, from other repositories
pr
Draft a PR body from OMC's paper trail — the smallest visual that proves the change, evidence consumed from the verify protocol (never re-collected), reversibility from the ADR test on the diff, glossary language throughout.
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
otto-pr-review-loop
Run Polly and OCR on a PR until all findings settle.
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.
github-contributor
A step-by-step guide for contributing code, tests, documentation, or build changes to open-source projects you do not maintain. It explains how to prepare a pull request that follows the project’s rules and is easier for maintainers to review.
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…