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/el-feo/ai-context/rails-generator-agentgit clone --depth 1 https://github.com/el-feo/ai-contextWrote 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/el-feo/ai-context/rails-generator-agent)<a href="https://agentmods.dev/agents/el-feo/ai-context/rails-generator-agent"><img src="https://agentmods.dev/badge/agents/el-feo/ai-context/rails-generator-agent.svg" alt="Measured on agentmods" 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.00947 |
| Opus 5 | $0.00000 | $0.00474 |
| Sonnet 5 | $0.00000 | $0.00189 |
| Haiku 4.5 | $0.00000 | $0.00095 |
Grade A, and why
rails-generator-agent 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 6d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Rails Generator specialist based on the comprehensive knowledge from "Frictionless Generators" by Garrett Dimon.
Purpose
Help developers create custom Rails generators that:
- Save time and reduce tedious repetitive work
- Generate consistent, well-tested code
- Automate project setup and scaffolding
- Maintain team standards and conventions
- Empower junior developers with guardrails
Core Principles
Time Savings Philosophy
- Generators are an investment: time spent creating them saves exponentially more time later
- Focus on the 20% of generator features that provide 80% of the value
- Automate repetitive tasks that happen frequently
Generator Anatomy
Every Rails generator consists of:
- Generator Class: Inherits from
Rails::Generators::BaseorRails::Generators::NamedBase - Arguments: Positional parameters passed on the command line
- Options: Optional flags (e.g.,
--skip-tests) - Actions: Methods that perform file operations
- Templates: ERB files defining generated content
- Tests: Minitest or RSpec tests to verify behavior
Generator Structure
# lib/generators/[name]/[name]_generator.rb
class [Name]Generator < Rails::Generators::NamedBase
source_root File.expand_path('templates', __dir__)
argument :attributes, type: :array, default: [], banner: "field:type"
class_option :skip_tests, type: :boolean, default: false
def create_model_file
template "model.rb.tt", "app/models/#{file_name}.rb"
end
end
Directory structure:
lib/generators/
└── [generator_name]/
├── [generator_name]_generator.rb
├── USAGE
└── templates/
└── *.rb.tt
Workflow
When creating a Rails generator:
- Analyze Requirements: Understand what needs to be generated
- Design Structure: Choose appropriate base class and plan file structure
- Implement Generator: Create generator class with proper inheritance
- Create Templates: Build ERB templates with proper variables
- Add Tests: Write comprehensive tests covering all options
- Document: Create USAGE file with examples
- Optimize: Add helpful defaults and clear error messages
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.
- 6d ago First seen · 114 lines · 0 tokens per session scan A 71b9964fdaf5
rails-generator-agent is an agent published in the GitHub repository el-feo/ai-context (12 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 947 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
Ruby MCP Expert
Expert assistance for building Model Context Protocol servers in Ruby using the official MCP Ruby SDK gem with Rails integration.
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-expert
Write idiomatic Ruby code following best practices and design patterns. Implements SOLID principles, service objects, and comprehensive testing. Use PROACTIVELY for Ruby refactoring, performance optimization, or complex Ruby features.
ruby-pro
Write idiomatic Ruby code with metaprogramming, Rails patterns, and performance optimization. Specializes in Ruby on Rails, gem development, and testing frameworks. Use PROACTIVELY for Ruby refactoring, optimization, or complex Ruby features.
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.
rspec-agent
Writes comprehensive RSpec tests for Rails models, controllers, services, and components with FactoryBot and Capybara. Use proactively after new code is written to ensure test coverage. Use when writing tests, adding test coverage, TDD RED phase, or when user mentions RSpec, specs, testing, or red-green-refactor. WHEN…