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 fetch-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/fetch-pr-comments)<a href="https://agentmods.dev/skills/tobihagemann/turbo/fetch-pr-comments"><img src="https://agentmods.dev/badge/skills/tobihagemann/turbo/fetch-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/fetch-pr-comments"><img src="https://agentmods.dev/badge/skills/tobihagemann/turbo/fetch-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.00083 | $0.00922 |
| Opus 5 | $0.00042 | $0.00461 |
| Sonnet 5 | $0.00017 | $0.00184 |
| Haiku 4.5 | $0.00008 | $0.00092 |
Grade A, and why
fetch-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 9d 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fetch PR Comments
Fetch unresolved review comments, top-level review body comments, and PR conversation comments from a GitHub PR and present them in a readable summary. This is a read-only skill -- it does not evaluate, fix, or reply to any comments.
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 (review threads, inner comment pages for long threads, reviews, issue comments) 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" },
"reviewThreads": [ { "id", "isResolved", "isOutdated", "comments": { "nodes": [ { "author", "body", "path", "line", "originalLine", "diffHunk" } ] } } ],
"reviews": [ { "author", "body", "state" } ],
"issueComments": [ { "author", "body", "createdAt", "url" } ]
}
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.
Step 2: Present Results
Display a summary header followed by comments grouped by file.
Summary header:
- PR title and link
- Branch:
head->base - Total threads / unresolved threads
Top-level review comments (if any):
Show reviews with non-empty body before the file-grouped threads:
## Review Comments
### @reviewer (CHANGES_REQUESTED)
> Review body text here
### @another-reviewer (COMMENTED)
> Another review body here
Issue comments (if any):
Show PR conversation comments after review comments, ordered by createdAt:
## Issue Comments
### @commenter (2026-04-20)
> Issue comment body here
### @another-commenter (2026-04-21)
> Another issue comment body here
Inline threads grouped by file:
For each file with unresolved threads, show:
## `path/to/file.ts`
### Line 42 (by @reviewer)
```diff
<diffHunk from first comment>
```
> Comment body here
### Line 10 (by @another-reviewer) [outdated]
```diff
<diffHunk from first comment>
```
> First comment body
>
> **@reply-author:** Reply 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.
- 9d ago First seen · 109 lines · 83 tokens per session scan A 9fbf605c66f1
fetch-pr-comments is a skill published in the GitHub repository tobihagemann/turbo (402 stars, last pushed yesterday), licensed MIT. It adds 83 tokens to every session and 922 once invoked, about $0.0004 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-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.
request-pr-review
A workflow for finding your open GitHub pull requests and asking the right people to review them. A pull request is a proposed code change waiting for teammates to check before it is merged.
mx-pr
Draft a pull request from the feature spec and git log, run an autonomous commit-history cleanup (content check), then publish to GitHub or GitLab (Bitbucket experimental) — or hand off. Use when a feature branch is ready for PR, standalone or from mx-flow. Usage: /mx-pr [name].
mx-commit
Commit all pending changes as one commit per logical concern, following the project's message convention (type prefix, 50-char subject, English). Use when the working tree may hold several changes or the convention must be enforced; a single trivial change can use plain git commit. Usage: /mx-commit [--auto].
breaking-change-audit
Audit shipctl's public interface before a release — compare flags, exit codes, and output formats against the previous tag to catch accidental breaking changes. Use when preparing a release, when asked to "check for breaking changes", or as a gate before tagging a new version.