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-feature-developer)<a href="https://agentmods.dev/agents/dgalarza/claude-code-workflows/rails-feature-developer"><img src="https://agentmods.dev/badge/agents/dgalarza/claude-code-workflows/rails-feature-developer/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-feature-developer"><img src="https://agentmods.dev/badge/agents/dgalarza/claude-code-workflows/rails-feature-developer.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.01133 |
| Opus 5.5 | $0.00000 | $0.00453 |
| Sonnet 5.5 | $0.00000 | $0.00227 |
| Haiku 4.5 | $0.00000 | $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 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.
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.
- 1mo 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 (62 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,133 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-expert
Build scalable Rails applications with modern patterns and best practices. Implements service objects, background jobs, and API design. Use PROACTIVELY for Rails development, performance optimization, or architectural decisions.
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.
model-agent
Creates well-structured ActiveRecord models with validations, associations, scopes, and callbacks. Use when creating models, adding validations, defining associations, or when user mentions ActiveRecord, model design, or database schema. WHEN NOT: Adding business logic beyond data/persistence (use service-agent)…
mailer-agent
Creates Action Mailer emails with previews, templates, and delivery tests following Rails conventions. Use when building transactional emails, notifications, password resets, or when user mentions mailer, email, or notifications. WHEN NOT: Real-time notifications (use Action Cable), background processing logic (use…
backend-developer
Implement server-side logic across languages/stacks; enforce clean architecture and boundaries.
rails-builder
Ruby on Rails implementation specialist. Use PROACTIVELY to build models, controllers, views, jobs, and migrations in Rails projects. Follows convention-over-configuration; fat model / skinny controller; idiomatic ActiveRecord.