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 Gerg/ai_agent_skills --skill pr-reviewgit clone --depth 1 https://github.com/Gerg/ai_agent_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/gerg/ai_agent_skills/pr-review)<a href="https://agentmods.dev/skills/gerg/ai_agent_skills/pr-review"><img src="https://agentmods.dev/badge/skills/gerg/ai_agent_skills/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/gerg/ai_agent_skills/pr-review"><img src="https://agentmods.dev/badge/skills/gerg/ai_agent_skills/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.00037 | $0.02784 |
| Opus 5 | $0.00018 | $0.01392 |
| Sonnet 5 | $0.00007 | $0.00557 |
| Haiku 4.5 | $0.00004 | $0.00278 |
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 10d 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 — 348 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Review
Conduct thorough, systematic code reviews using test-driven validation and issue tracking.
When using this skill, begin by stating: "I'm using the pr-review skill to conduct a systematic code review with empirical validation and issue tracking."
Using This Skill
This skill provides the core PR review process. Load references when you need detailed guidance:
When validating against acceptance criteria:
- references/scope-validation.md - Map implementation to ticket requirements
When checking code consistency:
- references/consistency-patterns.md - Compare with existing patterns
When validating suspected bugs:
- references/test-validation.md - Write tests to confirm bugs empirically
When validating user workflows:
- references/end-to-end-validation.md - Verify features work end-to-end
When consolidating review findings:
- references/deduplicating-findings.md - Identify and merge duplicate tickets
When evaluating code quality:
- references/code-quality.md - Check comments, naming, and redundancy
Prerequisites
- Access to codebase and related documentation
- Test environment accessible (if validating bugs empirically)
- Issue tracking system available (see: ../agent-issue-tracking/SKILL.md for agent-based tracking)
When reviewing against requirements:
- Requirements must be accessible before starting review
- If requirements are referenced but unavailable (auth failure, network error, missing ticket), stop and notify user
- Don't proceed with partial review based on code inference or similar patterns
Process
1. Initialize Review Tracking
Create a main review tracking item with:
- Description of what's being reviewed
- Link to external ticket/PR
- Relevant tags for searchability
Example structure:
- Title: "Review PR #123 - Add user authentication"
- Type: Task
- Priority: High
- Description: "Thorough review of authentication implementation"
- Tags: review, security, authentication
- External Reference: Link to PR or ticket
What ships with it
6 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.
- 10d ago First seen · 348 lines · 37 tokens per session scan A e65e7c575bfe
pr-review is a skill published in the GitHub repository Gerg/ai_agent_skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 37 tokens to every session and 2,784 once invoked, about $0.0002 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-31.
Other skills, from other repositories
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
engram-branch-pr
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
verify-behavior
Verify or reproduce visible product behavior by driving the real UI with pi-computer-use's checked tools, requiring verified expect postconditions and durable state evidence for meaningful UI flows. Use when triage needs visual reproduction, implementation needs behavioral proof, review needs interactive confirmation…
github-contributor
End-to-end playbook for shipping high-quality pull requests to open-source projects you don't maintain — discovery, CONTRIBUTING compliance, PR-size check, minimal-diff implementation, PR description with AI-assisted disclosure, conflict resolution, and post-submission maintainer interaction. Use whenever creating…
revdiff
Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…
write-pr
Reference standards for writing pull request titles and descriptions in the tldraw repository, plus the pre-flight comment sweep over the diff. Use as supporting guidance when another skill or workflow needs PR content standards, not as the user-facing create/update PR workflow.