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 tommyvo/useful-prompts --skill gh-pr-code-reviewgit clone --depth 1 https://github.com/tommyvo/useful-promptsWrote 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/tommyvo/useful-prompts/gh-pr-code-review)<a href="https://agentmods.dev/skills/tommyvo/useful-prompts/gh-pr-code-review"><img src="https://agentmods.dev/badge/skills/tommyvo/useful-prompts/gh-pr-code-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/tommyvo/useful-prompts/gh-pr-code-review"><img src="https://agentmods.dev/badge/skills/tommyvo/useful-prompts/gh-pr-code-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.00024 | $0.02419 |
| Opus 5.5 | $0.00010 | $0.00968 |
| Sonnet 5.5 | $0.00005 | $0.00484 |
| Haiku 4.5 | $0.00002 | $0.00242 |
Grade A, and why
gh-pr-code-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 24d 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 — 252 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review GitHub Pull Request
Review a GitHub Pull Request using the gh CLI and provide a comprehensive report with suggestions.
CRITICAL: MANDATORY FIRST STEPS
YOU MUST follow these steps IN ORDER. DO NOT skip any step:
Step 1: Get PR Details (MANDATORY)
Use the gh CLI to gather PR information:
- IF user provides a PR number → Run
gh pr view <number> --json title,body,changedFiles,reviews,comments - IF no PR number provided → Run
gh pr view --json title,body,changedFiles,reviews,commentsto get the current branch's PR
DO NOT proceed without PR metadata.
Step 2: Get Code Diff (MANDATORY)
Get the actual code changes using git:
- Run
gh pr view <number> --json baseRefName,headRefNameto get the base and head branch names - Run
git fetch originto ensure remote refs are up to date - Run
git diff origin/<baseRefName>...origin/<headRefName>to get all code changes
This is your primary source of truth for the actual code changes.
Step 3: Get CI/CD Status (MANDATORY)
Run gh pr checks <number> to get CI/CD status.
CRITICAL WARNINGS:
- DO NOT attempt to review the PR without completing Steps 1-3 first
- DO NOT use context or memory — use ONLY the output from these commands
- DO NOT modify the PR
Step 4: Additional Context (Optional)
You MAY read relevant files in the workspace for additional context if needed.
Step 5: Choose Review Mode (MANDATORY)
Check the size of the PR: count the changed files and lines, for example with --shortstat on the git diff command you used, or with gh pr view <number> --json additions,deletions,changedFiles. If it touches more than 15 files or more than 800 changed lines, or the user asked for subagents, use parallel subagents as described in Large Reviews: Parallel Subagents below. Otherwise, or if the user asked not to use subagents, review it yourself in a single pass.
Step 6: Generate Report (MANDATORY)
Provide the review report directly in the chat (do NOT create files).
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.
- 24d ago Changed 4b37a01f0f3a
- 1mo ago Changed · +63 lines 50f8b513bf4f
- 2mo ago First seen · 189 lines · 24 tokens per session scan A b7a20ef6368a
gh-pr-code-review is a skill published in the GitHub repository tommyvo/useful-prompts (4 stars, last pushed 2d ago), licensed Unlicense. It adds 24 tokens to every session and 2,419 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-31.
Other skills, from other repositories
pr
Draft a PR body from OMC's paper trail — the smallest visual that proves the change, evidence consumed from the verify protocol (never re-collected), reversibility from the ADR test on the diff, glossary language throughout.
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
otto-pr-review-loop
Run Polly and OCR on a PR until all findings settle.
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.
github-contributor
A step-by-step guide for contributing code, tests, documentation, or build changes to open-source projects you do not maintain. It explains how to prepare a pull request that follows the project’s rules and is easier for maintainers to review.
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…