Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/JeremyDev87/codingbuddynpx agentmods add skills/jeremydev87/codingbuddy/pr-reviewWrote 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/jeremydev87/codingbuddy/pr-review)<a href="https://agentmods.dev/skills/jeremydev87/codingbuddy/pr-review"><img src="https://agentmods.dev/badge/skills/jeremydev87/codingbuddy/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/jeremydev87/codingbuddy/pr-review"><img src="https://agentmods.dev/badge/skills/jeremydev87/codingbuddy/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.00032 | $0.06887 |
| Opus 5.5 | $0.00013 | $0.02755 |
| Sonnet 5.5 | $0.00006 | $0.01377 |
| Haiku 4.5 | $0.00003 | $0.00689 |
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 — 775 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Review
Overview
Systematic, evidence-based pull request review with anti-sycophancy principles. Critique-first ordering ensures critical issues are identified before any positive observations.
Core principle: Review what changed, not what it's called. Labels lie. Tests verify author's assumptions—review catches flawed assumptions.
Violating the letter of this process is violating the spirit of code review.
Table of Contents
- When to Use
- The Iron Law
- Quick Reference
- Review Efficiency Framework
- Change-Type Quick Guides
- Review Process
- Review Dimensions
- Security Quick Scan
- Accessibility Quick Scan
- Devil's Advocate Analysis
- Impact Radius Analysis
- Refactoring Verification
- Anti-Sycophancy Guide
- Constructive Feedback Patterns
- Output Format
- Common Rationalizations
- Red Flags - STOP
- When Stuck
- Verification Checklist
- Knowledge Sharing
- Review Metrics
- Specialist Escalation
When to Use
Always use for:
- New feature PRs
- Bug fix PRs
- Refactoring PRs
- Security-related changes
- API changes
- Database schema changes
Lighter review acceptable for:
- Documentation-only changes
- Configuration tweaks (still check security)
- Dependency updates (still check security + breaking changes)
Never skip:
- Security Quick Scan (4 critical items, ~2 min)
The Iron Law
NO APPROVAL WITHOUT COMPLETING ALL CRITICAL DIMENSIONS
Security, Correctness, and Test Coverage must ALWAYS be reviewed. No exceptions.
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 · 775 lines · 32 tokens per session scan A 34ffb2d016ec
pr-review is a skill published in the GitHub repository JeremyDev87/codingbuddy (31 stars, last pushed 6mo ago), licensed MIT. It adds 32 tokens to every session and 6,887 once invoked, about $0.0001 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
ring:migrating-to-lib-observability
Migrating a Lerian Go app off lib-commons observability imports (deprecated shims or removed APIs) to lib-observability via a fixed mapping table, then bumps go.mod and validates the build; ring:backend-go applies the edits. Covers log/zap/runtime/assert, opentelemetry/tracing, HTTP middleware, context helpers, and…
ring:using-lib-systemplane
Using lib-systemplane, the hot-reload runtime-config plane (Postgres LISTEN/NOTIFY or MongoDB change streams), in two modes. Sweep Mode detects DIY config reload (SIGHUP, fsnotify, viper, pgx LISTEN), manual tenant-scoping, hand-built admin CRUD, and v4 residue. Reference Mode catalogs client lifecycle and…
ring:applying-composition-patterns
React composition patterns that scale. Avoid boolean prop proliferation by using compound components, lifting state, and composing internals. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or during architecture review. Skip for simple components with 1-2 props…
ring:using-lib-observability
Using lib-observability v1.1.0, Lerian's OpenTelemetry foundation (lib-commons, lib-systemplane, lib-streaming depend on it), in two modes. Sweep Mode detects DIY zap/slog logging, raw OTel metrics, hand-rolled redaction, and hard-coded attribute strings. Reference Mode catalogs the log, metrics, zap, redaction, and…
ring:using-outbox
Using the transactional-outbox pattern across lib-streaming (writer) and lib-commons/v5/commons/outbox (repository + relay), in two modes. Sweep Mode detects DIY outbox tables, hand-rolled relay loops, send-and-pray emits, missing WithOutboxTx wrapping, and broker calls inside DB transactions. Reference Mode catalogs…
ring:adopting-lib-commons-huma-wrapper
Adopting the lib-commons/v5 shared Huma (OAS 3.1) OpenAPI wrapper + RFC 9457 problem model (commons/net/http/{openapi,problem}) in a Lerian Go service: wire openapi.New/ServeSpec + problem.Install (central >=500 scrub) on BOTH runtime and spec-gen paths, the per-rail problem.MapError flex seam, and rename-only spec…