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-react-review-checklistgit 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-react-review-checklist)<a href="https://agentmods.dev/skills/tommyvo/useful-prompts/gh-pr-react-review-checklist"><img src="https://agentmods.dev/badge/skills/tommyvo/useful-prompts/gh-pr-react-review-checklist/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-react-review-checklist"><img src="https://agentmods.dev/badge/skills/tommyvo/useful-prompts/gh-pr-react-review-checklist.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.00048 | $0.04066 |
| Opus 5.5 | $0.00019 | $0.01626 |
| Sonnet 5.5 | $0.00010 | $0.00813 |
| Haiku 4.5 | $0.00005 | $0.00407 |
Grade A, and why
gh-pr-react-review-checklist 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 7d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- react-review-checklist — 86% identical, 233 lines differ
How it starts
The opening of the file, as written. The whole thing — 286 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub PR React Review Checklist
Review a GitHub Pull Request using the gh CLI and check its JavaScript/TypeScript, React, and Next.js changes against the checklists below. This complements gh-pr-code-review (general correctness, security, clarity); it does not repeat that review.
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: Check Scope (MANDATORY)
If the PR diff contains no JavaScript/TypeScript files (.js, .jsx, .ts, .tsx, .mjs, .cjs, next.config.*), output a single line saying there are no JavaScript/TypeScript changes to check, and stop.
Step 6: Decide Which Checklists Apply (MANDATORY)
- TypeScript / JavaScript and Testing - always apply.
- React - apply when the changed files use React (JSX/TSX, hooks,
reactimports). - Next.js - apply only if
nextis a dependency inpackage.json(read it from the workspace, or from the PR diff if it changed). Note the Next.js major version: caching and rendering defaults differ between versions, so judge caching items against the version the project uses. Apply App Router items to files underapp/; for files underpages/, apply only the router-agnostic items.
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.
- 7d ago First seen · 286 lines · 48 tokens per session scan A 610184a24331
gh-pr-react-review-checklist is a skill published in the GitHub repository tommyvo/useful-prompts (3 stars, last pushed 7d ago), licensed Unlicense. It adds 48 tokens to every session and 4,066 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-24.
Other skills, from other repositories
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
react-patterns
React 18/19 patterns including hooks discipline, server/client component boundaries, Suspense + error boundaries, form actions, data fetching, state management decision trees, and accessibility-first composition. Use when writing or reviewing React components.
next-partial-prefetching-optimizer
Optimize what selected Next.js client navigations include before the click under Partial Prefetching. Use after Cache Components and Partial Prefetching are adopted when the user wants selected URL-specific UI to be instant, wants reusable content to wait for navigation, or needs to choose between default, viewport…
compiler-commit
Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits with the [compiler] or [rust-compiler] prefix.
server-side-calls
Call tRPC procedures directly from server code using t.createCallerFactory() and router.createCaller(context) for integration testing, internal server logic, and custom API endpoints. Catch TRPCError and extract HTTP status with getHTTPStatusCodeFromError(). Error handling via onError option.
compiler-port
Port a compiler pass from TypeScript to Rust. Gathers context, plans the port, implements in a subagent with test-fix loop, then reviews.