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 richkuo/rk-skills --skill fix-pr-reviewgit clone --depth 1 https://github.com/richkuo/rk-skillsWrote 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/richkuo/rk-skills/fix-pr-review)<a href="https://agentmods.dev/skills/richkuo/rk-skills/fix-pr-review"><img src="https://agentmods.dev/badge/skills/richkuo/rk-skills/fix-pr-review/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/richkuo/rk-skills/fix-pr-review"><img src="https://agentmods.dev/badge/skills/richkuo/rk-skills/fix-pr-review.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.00056 | $0.02906 |
| Opus 5 | $0.00028 | $0.01453 |
| Sonnet 5 | $0.00011 | $0.00581 |
| Haiku 4.5 | $0.00006 | $0.00291 |
Grade A, and why
fix-pr-review 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 5d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
fix-pr-review
Resolve every unaddressed review finding autonomously: validate, fix or refute, implement judgment calls and optional improvements, request a re-review. Never stop to ask the user. The review is a hypothesis: trace every finding to current file:line before changing anything.
Input
In any order: an optional PR reference (number or URL; default = the current branch's PR) and an optional literal codex token selecting Codex as this cycle's re-review bot. Any other token is ignored and named in the step 11 report. No PR found → say so and stop.
Steps
0. Resolve the PR and sync
gh pr view [<N>] --json number,headRefName,headRefOid,headRepositoryOwner,baseRefName,state,mergeable,mergeStateStatus, then git fetch origin. MERGED/CLOSED → stop and report. Be on the PR's head branch (gh pr checkout <N> if not; never fix a review on the base branch). On a fork PR (headRepositoryOwner differs) pull from and push to the tracked upstream, which may differ from origin. git pull --ff-only; no fast-forward → stop and report. CONFLICTING/DIRTY → step 7 runs this invocation.
1. Fetch all unaddressed review feedback
Three channels: formal reviews, issue comments, inline diff threads. Fetch and select the unaddressed set per fetch-recipes.md, read completely. Never delete, edit, or bury a disposition comment: the next review reads them on purpose. Record whether the set contains any blocking finding (a Needs Fixing / Requires Human Review item, a thread asserting a real defect, or a step 2 CI failure) — step 10 routes on it.
LGTM with non-blocking items still gets them. Bare LGTM (no finding items, no open threads, and after step 2 no CI failure this PR caused) → report approved and stop, naming any **Verification limitation:** lines and any CI failure attributed elsewhere. A conflict on a bare-LGTM PR still runs steps 7 through 9; step 7's merge re-review rule decides whether step 10 posts a trigger.
What ships with it
4 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.
- 5d ago Changed 8c3b51b4626d
- 6d ago Changed · +2 lines d319a6d17807
- 7d ago Changed · -112 lines · -142 tokens per session da779f1e2955
- 11d ago First seen · 200 lines · 198 tokens per session scan A 4e938c908039
fix-pr-review is a skill published in the GitHub repository richkuo/rk-skills (49 stars, last pushed yesterday), licensed MIT. It adds 56 tokens to every session and 2,906 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-30.
Other skills, from other repositories
criticism-self-criticism
A structured review method for examining completed work, criticism, and repeated mistakes. It focuses on specific evidence, causes, effects, and practical improvements.
refactor
Expert code refactoring based on Martin Fowler's catalog — improve maintainability without changing behavior. Covers code smells, composing methods, moving features, organizing data, simplifying conditionals, method calls, and generalization. Triggers on: refactor, 重构, clean up, improve code, code smell, extract…
understand
Review and understand freshly AI-generated code. Scans the current repo's uncommitted/branch changes and builds a Claude-style light-themed two-column webpage — left is the project folder tree of changed files, right is the selected file's syntax-highlighted diff (additions/deletions clearly distinguished from…
arize-annotation
INVOKE THIS SKILL when creating, managing, or using annotation configs or annotation queues on Arize (categorical, continuous, freeform), or applying human annotations to project spans via the Python SDK. Configs are the label schema for human feedback; queues are review workflows that route records to annotators.…
ai-ready
Make any repo AI-ready — analyzes your codebase and generates AGENTS.md, copilot-instructions.md, CI workflows, issue templates, and more. Mines your PR review patterns and creates files customized to your stack. USE THIS SKILL when the user asks to "make this repo ai-ready", "set up AI config", or "prepare this repo…
dotnet-best-practices
Ensure .NET/C# code meets best practices for the solution/project.