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 jeremylongworth-source/AgentSkills --skill pr-reviewgit clone --depth 1 https://github.com/jeremylongworth-source/AgentSkillsWrote 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/jeremylongworth-source/agentskills/pr-review)<a href="https://agentmods.dev/skills/jeremylongworth-source/agentskills/pr-review"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/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/jeremylongworth-source/agentskills/pr-review"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/pr-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00053 | $0.00343 |
| Opus 5.5 | $0.00021 | $0.00137 |
| Sonnet 5.5 | $0.00011 | $0.00069 |
| Haiku 4.5 | $0.00005 | $0.00034 |
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.
What it actually says
PR Review
Core Workflow
- Understand the change intent, affected surface, user impact, and stated test plan before judging the diff.
- Review for correctness, edge cases, regressions, security, data handling, performance, compatibility, and maintainability.
- Prioritize findings that could cause wrong behavior, user harm, production risk, or future maintenance cost.
- Tie each finding to concrete evidence from code, tests, logs, or behavior.
- Separate blocking findings from non-blocking suggestions and style nits.
- Call out missing tests or validation when risk remains.
Safety Rules
- Do not approve, merge, or dismiss review feedback automatically.
- Do not invent test results. State when tests were not run.
- Do not flood the review with preferences when there are no material risks.
- Escalate security, privacy, auth, billing, migration, data-loss, and rollout concerns.
Deliverable Shape
For PR reviews, provide:
- Findings ordered by severity
- File or area references where available
- Missing tests or validation gaps
- Residual risk
- Brief change summary only after findings
- Open questions that affect review confidence
References
- Read
references/pr-review-checklist.mdwhen reviewing pull requests, patches, diffs, or pre-merge code changes.
What ships with it
2 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.
- 1mo ago First seen · 44 lines · 53 tokens per session scan A 46ce40a0c050
pr-review is a skill published in the GitHub repository jeremylongworth-source/AgentSkills (1 stars, last pushed 17d ago), licensed MIT. It adds 53 tokens to every session and 343 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-09-03.
Other skills, from other repositories
addressing-review-feedback
How to work a task returned with review, QA or UAT findings. Use when a task is in needrevision or PR review comments are in your context.
wicked-garden-qe-code-analyzer
Static code analysis for testability, quality, and maintainability. Reviews code structure, identifies test-coverage gaps, and flags risky areas. Use when: static analysis, code-quality metrics, testability assessment, maintainability review, coverage-gap identification. Runs on arbitrary source code, anytime — does…
idd-spec-audit
Semantic audit of the IDD instruction corpus for leaked session context, cross-file contradictions, fresh-memory completability gaps, automation blockers, and restatement-discipline drift. Use on request to audit .github/instructions, the issue-authoring skill bundle, and the installed agent entry files (CLAUDE.md…
wicked-garden-engineering
Consolidated engineering domain skill: senior-engineer code review, architecture analysis, systematic debugging, implementation planning, and documentation generation. Use when: "review this code / file / diff" (quality, patterns, maintainability; --focus, --persona, --scenarios); "review the architecture of X" /…
gauntlet
Evidence-driven adversarial review and root-cause repair of code, designs, APIs, infrastructure, tests, and agent workflows. Use for deep reviews, red-team reviews, edge-case audits, production-readiness checks, or requests to find and fix defects iteratively. Supports sub-agents or a tracked solo workflow. Not for…
review
Static code review of the active diff: trace changed paths and report concrete P1/P2/P3 correctness, security, or spec bugs with file:line evidence. Use for code review or bug checks. Not runtime QA.