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 review-prgit 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/review-pr)<a href="https://agentmods.dev/skills/tobihagemann/turbo/review-pr"><img src="https://agentmods.dev/badge/skills/tobihagemann/turbo/review-pr/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/review-pr"><img src="https://agentmods.dev/badge/skills/tobihagemann/turbo/review-pr.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.00059 | $0.00428 |
| Opus 5.5 | $0.00024 | $0.00171 |
| Sonnet 5.5 | $0.00012 | $0.00086 |
| Haiku 4.5 | $0.00006 | $0.00043 |
Grade A, and why
review-pr 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.
What it actually says
Review PR
Fetch PR context, run a comprehensive code review, evaluate findings, and dispatch accepted findings to implementation.
Task Tracking
At the start, use TaskCreate to create a task for each step:
- Run
/fetch-pr-commentsskill - Resolve base branch
- Run
/review-codeskill - Run
/evaluate-findingsskill - Run
/resolve-findingsskill
Step 1: Run /fetch-pr-comments Skill
Run the /fetch-pr-comments skill to get unresolved review comments.
Step 2: Resolve Base Branch
Detect the PR's base branch via gh pr view --json baseRefName --jq '.baseRefName', then run git fetch origin <base-branch> to bring the remote ref up to date.
Step 3: Run /review-code Skill
Run the /review-code skill. The diff command is git diff origin/<base-branch>...HEAD. Take the base from origin/: a local branch of the same name can sit behind the remote, which puts the merge base before an already-merged pull request and pulls merged work into the review as if it were new.
Step 4: Run /evaluate-findings Skill
Run the /evaluate-findings skill on the combined results from Step 3. Include any unresolved PR comments from Step 1 as additional findings for evaluation.
Step 5: Run /resolve-findings Skill
If zero actionable findings survive evaluation, report that the code looks clean and stop.
Otherwise, run the /resolve-findings skill on the accepted findings from Step 4.
Rules
- If fetching PR comments fails, proceed with code review only.
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 · 45 lines · 59 tokens per session scan A f6dc0f6b5841
review-pr is a skill published in the GitHub repository tobihagemann/turbo (417 stars, last pushed 4d ago), licensed MIT. It adds 59 tokens to every session and 428 once invoked, about $0.0002 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-description-writer
Redacta una descripción de pull request clara y estructurada a partir de un diff de git, resumen de rama o lista de commits. Úsalo cuando te pidan escribir una descripción de PR, redactar una solicitud de cambios o documentar cambios de código. Produce una descripción con resumen, motivación, cambios realizados, pasos…
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.