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-security-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-security-review-checklist)<a href="https://agentmods.dev/skills/tommyvo/useful-prompts/gh-pr-security-review-checklist"><img src="https://agentmods.dev/badge/skills/tommyvo/useful-prompts/gh-pr-security-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-security-review-checklist"><img src="https://agentmods.dev/badge/skills/tommyvo/useful-prompts/gh-pr-security-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.00080 | $0.15751 |
| Opus 5.5 | $0.00032 | $0.06300 |
| Sonnet 5.5 | $0.00016 | $0.03150 |
| Haiku 4.5 | $0.00008 | $0.01575 |
Grade C, and why
gh-pr-security-review-checklist scanned grade C with 3 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 13d 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.
Downloads and executes remote codemediumSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
7. **Remote script execution** - `curl | bash` or downloading and running scripts in Dockerfiles, CI, or setup scripts. A checksum downloaded from the same place as the script proves nothing. Fix: pin the version and ver Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Cloud metadata endpointmediumServer-side request forgery
One request to 169.254.169.254 can return temporary IAM credentials.
9. **SSRF** - The server fetching a user-supplied URL (webhooks, imports, previews, notification callbacks), including after redirects, DNS rebinding, or URL parser differences. Fix: allowlist hosts, re-check the resolve Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
7. **Remote script execution** - `curl | bash` or downloading and running scripts in Dockerfiles, CI, or setup scripts. A checksum downloaded from the same place as the script proves nothing. Fix: pin the version and ver How it starts
The opening of the file, as written. The whole thing — 631 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub PR Security Review Checklist
Review a GitHub Pull Request using the gh CLI and check it against the security checklists below: secrets and obvious exposures, application security, authentication and sessions, client-side and browser, data isolation and lifecycle, messaging and background jobs, resource exhaustion, AI and LLM features, supply chain, infrastructure (Terraform/Atmos on AWS), CI/CD and containers, and optionally compliance and data handling. Every finding must name a real trust boundary and a concrete result, checked against the source; anything that depends on a fact the repository cannot show is reported as a lead to validate, not as a vulnerability. This complements gh-pr-code-review, which only covers security at a general level.
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.
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.
- 13d ago Changed · +240 lines · +29 tokens per session ee271b482e48
- 25d ago First seen · 391 lines · 51 tokens per session scan C 4d579916c0d4
gh-pr-security-review-checklist is a skill published in the GitHub repository tommyvo/useful-prompts (4 stars, last pushed 14d ago), licensed Unlicense. It adds 80 tokens to every session and 15,751 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it C with 3 findings (downloads and executes remote code, cloud metadata endpoint, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-24.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…