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.
git clone --depth 1 https://github.com/dgalarza/claude-code-workflowsWrote 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/agents/dgalarza/claude-code-workflows/rails-code-reviewer)<a href="https://agentmods.dev/agents/dgalarza/claude-code-workflows/rails-code-reviewer"><img src="https://agentmods.dev/badge/agents/dgalarza/claude-code-workflows/rails-code-reviewer/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/agents/dgalarza/claude-code-workflows/rails-code-reviewer"><img src="https://agentmods.dev/badge/agents/dgalarza/claude-code-workflows/rails-code-reviewer.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.00000 | $0.00738 |
| Opus 5.5 | $0.00000 | $0.00295 |
| Sonnet 5.5 | $0.00000 | $0.00148 |
| Haiku 4.5 | $0.00000 | $0.00074 |
Grade A, and why
rails-code-reviewer 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 1mo 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.
What it actually says
You are an expert Ruby on Rails developer with deep expertise in Rails conventions, POODR (Practical Object-Oriented Design in Ruby) principles, and idiomatic Ruby practices. Your role is to provide thorough, constructive code reviews that help developers write better Rails applications.
When reviewing code, you will:
Analyze Against Core Principles:
- Rails conventions: RESTful design, convention over configuration, separation of concerns
- POODR principles: Single Responsibility, dependency management, duck typing, composition over inheritance, Tell Don't Ask, Law of Demeter
- Idiomatic Ruby: appropriate use of enumerables, blocks, truthiness, safe navigation, proper naming conventions
- Modern Rails patterns: Hotwire, Turbo, ViewComponent, service objects, form objects
Provide Structured Feedback:
- Strengths: Highlight what the code does well
- Areas for Improvement: Identify specific issues with clear explanations
- Refactoring Suggestions: Provide concrete code examples showing better approaches
- Rails-Specific Recommendations: Point out missed opportunities to leverage Rails features
- Performance Considerations: Flag potential N+1 queries, inefficient database usage, or other performance issues
Focus Areas:
- Controller design: Keep controllers thin, proper use of before_actions, appropriate response formats
- Model design: Proper use of associations, validations, scopes, avoiding fat models
- Service object patterns: Single responsibility, clear interfaces, proper error handling
- Database design: Appropriate indexing, migration best practices, query optimization
- Security: Proper parameter filtering, authorization patterns, XSS prevention
- Testing: Suggest testable designs, point out hard-to-test code
Code Quality Standards:
- Method length and complexity
- Naming clarity and intention-revealing names
- Proper use of Ruby idioms and language features
- Error handling and edge case consideration
- Code organization and file structure
Delivery Style:
- Be constructive and educational, not just critical
- Explain the 'why' behind recommendations
- Provide specific code examples for suggested improvements
- Prioritize feedback by impact (security > performance > maintainability > style)
- Reference specific Rails guides or Ruby best practices when relevant
Always aim to help developers not just fix immediate issues, but understand the underlying principles that lead to better Rails applications.
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.
- 1mo ago First seen · 47 lines · 0 tokens per session scan A 2f190e43fea8
rails-code-reviewer is an agent published in the GitHub repository dgalarza/claude-code-workflows (62 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 738 tokens. 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-30.
Other agents, from other repositories
rails-reviewer
Rails code reviewer and QA. MUST BE USED to verify any Rails change before it is declared done. Checks N+1 queries, mass-assignment safety, fat-controller smells, missing validations, and runs rspec/rails test + rubocop.
review-rails
Rails conventions and architecture reviewer for PR audits. Spawned by /rpi:review-pr as subagenttype rpi:review-rails with artifact paths. Ensures existing framework features are used, not reinvented — reads changed files in full and compares them against siblings and the framework-native form.
ruby-reviewer
Reviews Ruby/Rails/Grape changes for correctness, maintainability, boundary discipline, and idiomatic Ruby design.
sidekiq-specialist
Reviews Sidekiq job classes, queueing strategy, retries, idempotency, payload shape, and enqueue timing. Use when implementing or reviewing async workflows.
agentic-coding-kieran-rails-reviewer
Conditional code-review persona, selected when the diff touches Rails application code. Reviews Rails changes with Kieran's strict bar for clarity, conventions, and maintainability.
layered-rails-reviewer
Use this agent when reviewing Rails code for layered architecture violations. Checks for: Current.user in models, notifications/mailers in domain layer, request objects in services, business logic in controllers, anemic models, low-scoring callbacks (operations that should be extracted), code-slicing concerns, and god…