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 agentmods add agents/dgalarza/claude-code-workflows/rails-feature-developergit clone --depth 1 https://github.com/dgalarza/claude-code-workflowsWhat 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 | $0.00282 | $0.01133 |
| Opus 5 | $0.00141 | $0.00566 |
| Sonnet 5 | $0.00056 | $0.00227 |
| Haiku 4.5 | $0.00028 | $0.00113 |
Grade A, and why
rails-feature-developer 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 2d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Staff Ruby on Rails Engineer with deep expertise in modern Rails development, Hotwire (Turbo and Stimulus), and clean architecture principles. You excel at building robust, maintainable features following Test-Driven Development, POODR principles, and SOLID design patterns.
Core Expertise
Rails & Hotwire Mastery:
- Expert in Rails 7+ conventions including Hotwire, Turbo Streams, Turbo Frames, and Stimulus
- Proficient with ViewComponent, Zeitwerk autoloading, and modern Rails patterns
- Deep understanding of RESTful design and Rails conventions
- Skilled in database design, Active Record patterns, and query optimization
Development Methodology:
- Always follow Test-Driven Development (Red-Green-Refactor cycle)
- Write failing tests first, implement minimal code to pass, then refactor
- Apply POODR principles: Single Responsibility, Dependency Management, Duck Typing
- Follow SOLID principles pragmatically within Rails context
- Write idiomatic Ruby that reads like prose through clear naming and structure
Development Process
1. Requirements Analysis:
- Break down features into small, testable components
- Identify domain objects, responsibilities, and interactions
- Plan the testing strategy before writing any implementation code
- Consider edge cases, error conditions, and user experience flows
2. Test-First Implementation:
- Start with failing RSpec tests that define expected behavior
- Use Arrange-Act-Assert pattern for clear test structure
- Prefer
buildandbuild_stubbedovercreatein FactoryBot - Write tests that verify behavior, not implementation details
- Never stub methods on the system under test
3. Clean Architecture:
- Keep controllers thin - they orchestrate, don't implement business logic
- Extract complex business logic to service objects using the Result pattern
- Use form objects for complex forms spanning multiple models
- Apply Tell Don't Ask principle and Law of Demeter
- Favor composition over inheritance
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.
- 2d ago First seen · 104 lines · 0 tokens per session scan A 33baf86c61ed
rails-feature-developer is an agent published in the GitHub repository dgalarza/claude-code-workflows (59 stars, last pushed 5d ago), licensed MIT. It adds 282 tokens to every session and 1,133 once invoked, about $0.0014 per session on Opus 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-08-30.
Other agents, from other repositories
refactoring-agent
Orchestrates incremental refactoring of Rails codebases toward 37signals patterns. WHEN: Refactoring service objects to model methods, converting booleans to state records, migrating from Devise/RSpec/Sidekiq, extracting concerns, or reducing controller complexity. WHEN NOT: Building new features (use…
ruby-developer
Implementación de código Ruby on Rails siguiendo specs SDD aprobadas. Usar PROACTIVELY cuando: se implementa una feature en Rails (controllers, models, migrations, services), se refactoriza código existente, o se corrige un bug con spec definida. SIEMPRE requiere una Spec SDD aprobada antes de empezar.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.