Borrowing it
Nothing to install: this file belongs to ymm-oss/fsl. 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/ymm-oss/fsl/main/.claude/skills/pr-review/SKILL.mdgit clone --depth 1 https://github.com/ymm-oss/fslWrote 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/ymm-oss/fsl/pr-review)<a href="https://agentmods.dev/skills/ymm-oss/fsl/pr-review"><img src="https://agentmods.dev/badge/skills/ymm-oss/fsl/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/ymm-oss/fsl/pr-review"><img src="https://agentmods.dev/badge/skills/ymm-oss/fsl/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.00058 | $0.01929 |
| Opus 5.5 | $0.00023 | $0.00772 |
| Sonnet 5.5 | $0.00012 | $0.00386 |
| Haiku 4.5 | $0.00006 | $0.00193 |
Grade A, and why
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 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review a pull request
Orchestrate an independent review of a pull request, typically one authored by an agent to
resolve an issue. This skill is the coordination layer; the per-dimension analysis belongs to
the specialized read-only reviewer agents under .claude/agents/. Diagnose and report — do not
push fixes onto the branch, and never merge (leave the PR open for human review).
Inputs: a PR number or branch, and the linked issue. If no issue is linked, ask for the intended contract before reviewing.
Lenses that apply to every phase:
- Trust order per
AGENTS.md: contracts and tests, then the Rust implementation, then frozen Python behavior, then prose. The PR description and any implementer conversation are claims, not evidence. - Suspect green. A confidently green false negative is more dangerous than a crash, so "the checks pass" is never sufficient on its own.
- Findings outside the diff still carry a reporting duty: an accepted construct with absent, placeholder, or hollow semantics is a soundness defect wherever it is found.
Phase 0 — Reconstruct the contract
- Read the PR (
gh pr view,gh pr diff), the linked issue, and anydocs/design/DESIGN-*.mdthe change touches or should have touched. - Restate, from the issue and repository evidence only: the requested outcome, the affected authority surface, the invariants at risk, and the verification the change needs.
- Note which CI lanes actually ran.
merge readinessis a bounded fail-fast lane (docs/design/DESIGN-ci.md), not product verification — record what remains unverified.
Phase 1 — Contract alignment
Map the issue's acceptance criteria to the diff in both directions:
- Required but missing: criteria with no corresponding change or test.
- Present but not required: scope creep, speculative fallbacks, compatibility work no contract calls for.
Check authority placement: new behavior lives under rust/, not the frozen src/fslc/; design
decisions are backed by an accepted design note; the change is the smallest contract-preserving
one.
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 Changed 411eac876e16
- 2mo ago First seen · 147 lines · 58 tokens per session scan A 4927efe28119
pr-review is a skill published in the GitHub repository ymm-oss/fsl (35 stars, last pushed today), licensed Apache-2.0. It adds 58 tokens to every session and 1,929 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
python-style
Validate Python code against style and architectural conventions.
python-engineering-guidelines
General Python engineering standards for writing, reviewing, and refactoring maintainable code. Use when Codex works on Python code, especially in medium/large projects, runtime adapters, APIs, SDK integrations, async services, stateful systems, or refactors where readability, explicit typing, module boundaries, side…
project-onboarding
Standard procedure for onboarding new software projects: Feature analysis, code quality review, onboarding checklist, and task creation.
docs-analysis
Document requirements analysis: Analyzes concept and requirements documents in the docs/ folder, checks requirements against current code, and creates a consolidated difference report.
impact
Use when asked what a change could break or affect, "is this safe to commit/push/merge?", "what does this break?", or before committing a multi-file change — the callers outside the diff, the tests guarding them, and the contracts the change crosses.
diffctx
Use when reviewing or explaining a commit, PR, branch or uncommitted diff — "review my last commit", "review before merge", "review my changes", "what else does this change affect" — the callers and tests the change reaches outside its diff, then the surrounding code.