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-rails-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-rails-review-checklist)<a href="https://agentmods.dev/skills/tommyvo/useful-prompts/gh-pr-rails-review-checklist"><img src="https://agentmods.dev/badge/skills/tommyvo/useful-prompts/gh-pr-rails-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-rails-review-checklist"><img src="https://agentmods.dev/badge/skills/tommyvo/useful-prompts/gh-pr-rails-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.00042 | $0.03526 |
| Opus 5.5 | $0.00017 | $0.01410 |
| Sonnet 5.5 | $0.00008 | $0.00705 |
| Haiku 4.5 | $0.00004 | $0.00353 |
Grade A, and why
gh-pr-rails-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 8d 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 — 276 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub PR Rails Review Checklist
Review a GitHub Pull Request using the gh CLI and check its Ruby and Rails 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 Ruby/Rails files (.rb, .rake, .erb, Gemfile, db/migrate/, config/ for a Rails app), output a single line saying there are no Ruby/Rails changes to check, and stop.
Step 6: 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.
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.
- 8d ago First seen · 276 lines · 42 tokens per session scan A bebded437a0e
gh-pr-rails-review-checklist is a skill published in the GitHub repository tommyvo/useful-prompts (3 stars, last pushed 8d ago), licensed Unlicense. It adds 42 tokens to every session and 3,526 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
rspec-conventions
Rootstrap RSpec conventions. Use when writing, reviewing, or editing RSpec test files (spec//spec.rb, spec/railshelper.rb, spec/spechelper.rb, spec/support//.rb) or factories. Covers describe/context structure, let/subject, matchers, factories, mocking/stubbing, shared examples, and spec types (model, request…
testunit-skill
Generates Test::Unit tests in Ruby. Classic xUnit-style testing with assert methods and test case classes. Use when user mentions "Test::Unit", "assertequal Ruby", "Ruby test-unit". Triggers on: "Test::Unit", "Ruby test-unit", "assertequal Ruby" (not RSpec).
ruby
Ruby development guidelines covering idiomatic code style, Ruby 3.x features, testing with RSpec, and best practices for building maintainable Ruby applications.
rspec
RSpec testing best practices for Ruby and Rails applications, covering test organization, data management, and isolation patterns.
ruby-rails
Use this skill when building Ruby on Rails applications — MVC, ActiveRecord, service objects, API mode, background jobs, and testing. This skill enforces: thin controllers, service objects for business logic, ActiveRecord query best practices, Rails API mode conventions, and RSpec testing patterns. Requires Rails 7+…
test-service
Use when writing RSpec for a service object under spec/services/. Test the public .call contract. Trigger words: service spec, test service object, spec/services.