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 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/rails-review-checklist)<a href="https://agentmods.dev/skills/tommyvo/useful-prompts/rails-review-checklist"><img src="https://agentmods.dev/badge/skills/tommyvo/useful-prompts/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/rails-review-checklist"><img src="https://agentmods.dev/badge/skills/tommyvo/useful-prompts/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.00032 | $0.03140 |
| Opus 5.5 | $0.00013 | $0.01256 |
| Sonnet 5.5 | $0.00006 | $0.00628 |
| Haiku 4.5 | $0.00003 | $0.00314 |
Grade A, and why
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 25d 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rails Review Checklist
Goal
Provide a focused second-pass report for uncommitted Ruby and Rails changes, checking them against the Ruby and Rails checklists below. This complements local-code-review (general correctness, security, clarity); it does not repeat that review. The report lists checklist items the developer should address.
CRITICAL: MANDATORY FIRST STEP
YOU MUST run git diff HEAD as your ABSOLUTE FIRST action before doing ANYTHING else.
- DO NOT attempt to review code from context or memory
- DO NOT skip this step under any circumstances
- DO NOT proceed to the next step without running this command first
- DO NOT assume you know what changed
If you do not run git diff HEAD first, you are failing to follow instructions.
Process
Follow these steps IN ORDER. DO NOT skip any step:
- STEP 1 - Get Changes via Git (MANDATORY): Run
git diff HEADin the terminal to retrieve ALL uncommitted changes. This is your primary source of truth for what to review. You can read existing files in the current directory for additional context if needed. - STEP 2 - Check Scope: If the 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 3 - Choose Review Mode: Check the size of the diff with
git diff HEAD --shortstat. 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 4 - Generate The Report: Review the changes against BOTH checklists below and generate the report in markdown format. Only report items that actually appear in the diff. Rate each finding in terms of priority using the emoji system. Do not save the report in the filesystem. You should only output to chat.
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.
- 25d ago First seen · 183 lines · 32 tokens per session scan A e3551d0939f7
rails-review-checklist is a skill published in the GitHub repository tommyvo/useful-prompts (4 stars, last pushed 14d ago), licensed Unlicense. It adds 32 tokens to every session and 3,140 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-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.