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 tobihagemann/turbo --skill resolve-pr-commentsgit clone --depth 1 https://github.com/tobihagemann/turboWrote 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/tobihagemann/turbo/resolve-pr-comments)<a href="https://agentmods.dev/skills/tobihagemann/turbo/resolve-pr-comments"><img src="https://agentmods.dev/badge/skills/tobihagemann/turbo/resolve-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/tobihagemann/turbo/resolve-pr-comments"><img src="https://agentmods.dev/badge/skills/tobihagemann/turbo/resolve-pr-comments.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 12 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00096 | $0.03962 |
| Opus 5.5 | $0.00038 | $0.01585 |
| Sonnet 5.5 | $0.00019 | $0.00792 |
| Haiku 4.5 | $0.00010 | $0.00396 |
Grade A, and why
resolve-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 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 — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resolve PR Review Comments
Fetch unresolved review comments from a GitHub PR (inline threads, review-body observations, and issue-comment observations from the PR conversation), evaluate each one, fix or skip based on confidence, answer reviewer questions using the recalled rationale behind the change, and reply. Inline threads are answered with thread replies; issue-comment findings from people are answered with new PR conversation comments. Review-body findings and AI-reviewer issue comments flow through the same evaluate-and-fix pipeline; their outcomes land only in the summary.
Task Tracking
At the start, use TaskCreate to create a task for each step:
- Fetch comments
- Triage already-addressed feedback
- Run
/interpret-feedbackskill - Split questions and change requests
- Run
/evaluate-findingsskill - Resolve ambiguities
- Run
/resolve-findingsskill - Verify fixes
- Answer reviewer questions
- Wait for AI re-reviews
- Run
/reply-to-pr-threadsskill - Run
/reply-to-pr-conversationskill - Summary
Step 1: Fetch Comments
Auto-detect owner, repo, and PR number from current branch if not provided. Then run scripts/fetch-pr-data.sh, which handles full pagination (reviews, review threads, inner comment pages for long threads, issue comments, commits) and emits a single merged JSON document:
bash <skill-dir>/scripts/fetch-pr-data.sh <owner> <repo> <pr_number>
Output shape:
{
"meta": { "title", "url", "headRefName", "baseRefName", "body" },
"reviewThreads": [ { "id", "isResolved", "isOutdated", "comments": { "nodes": [ { "author", "body", "path", "line", "originalLine", "diffHunk" } ] } } ],
"reviews": [ { "author", "body", "state", "submittedAt" } ],
"issueComments": [ { "author", "body", "createdAt", "url" } ],
"commits": [ { "commit": { "oid", "abbreviatedOid", "message", "committedDate" } } ]
}
Filter review threads to unresolved only. Filter reviews to those with a non-empty body, excluding PENDING state (unsubmitted drafts). Filter issue comments to those with a non-empty body.
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.
- 2d ago Changed a6f7929faf17
- 6d ago Changed · +2 lines c2aa3d7b5762
- 9d ago Changed f4629917a8e8
- 11d ago Changed · +16 lines 8f9cd68c9241
- 18d ago Changed · +4 lines 5be4d8d25067
- 19d ago Changed · +2 lines 4d1308a7c529
- 25d ago Changed · +1 tokens per session 4916b59e4b25
- 28d ago Changed · -1 lines 72d96fa5227d
- 1mo ago Changed · +2 lines cec037f71f28
- 1mo ago First seen · 197 lines · 95 tokens per session scan A 5d9b48fbb752
resolve-pr-comments is a skill published in the GitHub repository tobihagemann/turbo (416 stars, last pushed 2d ago), licensed MIT. It adds 96 tokens to every session and 3,962 once invoked, about $0.0004 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
audit-pr
Audit a whole PR against the delivery contract and return MERGE-READY or evidenced blockers with the full URL. Consumes the current review-change REVIEW-PASS receipt instead of re-running review axes; posts a SHA-bound ready comment; never edits or merges. Triggers: "audit-pr", "is this PR ready", "merge gate".
neo-pr
Use this skill when the user asks to create, draft, review, format, or generate a Pull Request (PR) title and description, specify target or source branches for a repository, or convert git branch diffs into concise, high-impact, non-AI-slop PR content.
glab-mr
A command-line tool for creating, reviewing, approving, discussing, and merging GitLab merge requests. A merge request is a proposed set of code changes for others to inspect before it is added to a project.
glab-stack
A GitLab CLI skill for working with stacked merge requests, where several smaller changes depend on one another. Each merge request in the stack builds on an earlier change.
address-github-comments
Use when you need to address review or issue comments on an open GitHub Pull Request using the gh CLI.
pr-review
Run an intelligent, risk-adaptive PR review with parallel multi-agent analysis.