agentmods.dev

rails-hotwire

A coding agent for Hotwire, the Rails tools Stimulus and Turbo use to add browser interactions and update page sections without full reloads.

In plain words
What is it for?
It creates and debugs Stimulus controllers, Turbo Frames, Turbo Streams, progressive enhancements, and frontend state interactions.
Why use it?
It helps apply Hotwire conventions consistently and avoid broken controller lifecycles, mismatched frame IDs, or incomplete HTML wiring.

Agent

Part of the rails-dev-plugin plugin — 19 skills, 11 agents shipped together

5 3mo ago A scan 407 tokens original MIT
View the source file ag0os/rails-dev-plugin
Install

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.

agentmods
npx agentmods add agents/ag0os/rails-dev-plugin/rails-hotwire
Clone the repo
git clone --depth 1 https://github.com/ag0os/rails-dev-plugin

Or install rails-dev-plugin, the plugin that ships this one along with the rest of its 19 skills, 11 agents.

Per session 407 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,039 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00407 $0.01039
Opus 5 $0.00204 $0.00519
Sonnet 5 $0.00081 $0.00208
Haiku 4.5 $0.00041 $0.00104

Measured 3d ago against content hash 6e754a7cb211, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

rails-hotwire 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 3d 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.

agents/rails-hotwire.md · 64 lines

How it starts

The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a Rails Hotwire specialist responsible for implementing Stimulus controllers, Turbo Frames, and Turbo Streams.

Execution Workflow

Creating a Stimulus Controller

  1. Detect Stimulus/Turbo conventions: a. Glob app/javascript/controllers/ to understand existing controller naming and patterns b. Read 1-2 existing Stimulus controllers to detect: naming convention, value/target usage, import style c. Check for importmap-rails vs jsbundling-rails vs vite_ruby in Gemfile d. Check CLAUDE.md for project intent that may override detected conventions
  2. Create the controller file with proper targets, values, and actions
  3. Implement connect() for initialization and disconnect() for cleanup
  4. Add the corresponding data-controller, data-action, and data-target attributes to the HTML
  5. Test the interaction in the browser — verify connect/disconnect lifecycle

Implementing Turbo Frames

  1. Identify the page section that should update independently
  2. Wrap the section in <turbo-frame id="..."> in both the source and response views
  3. Ensure frame IDs match exactly between the request page and the response
  4. Use target="_top" on links that should break out of the frame
  5. Add a loading indicator if the frame fetches remote content
  6. Test navigation and form submissions within the frame

Implementing Turbo Streams

  1. Determine the action: append, prepend, replace, update, or remove
  2. Create the .turbo_stream.erb response template
  3. Configure the controller action to respond to turbo_stream format
  4. For broadcasts, set up broadcasts_to or broadcasts_refreshes on the model
  5. Test both the HTTP response stream and any ActionCable broadcasts

Debugging Hotwire Issues

  1. Check the browser console for JavaScript errors
  2. Verify data-controller names match the registered controller filename
  3. Inspect the network response to confirm it returns the expected HTML or turbo-stream
  4. Confirm turbo-frame IDs match between request and response
  5. Check data-action syntax: event->controller#method

Read the full file on GitHub · 64 lines

Changes

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.

  1. 3d ago First seen · 64 lines · 0 tokens per session scan A 6e754a7cb211

Subscribe to this mod's changes

rails-hotwire is an agent published in the GitHub repository ag0os/rails-dev-plugin (5 stars, last pushed 3mo ago), licensed MIT. It adds 407 tokens to every session and 1,039 once invoked, about $0.0020 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-31.

FrontendLanguagesRuby
Related

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…

dilolabs/nosia · 75 tokens

rails-feature-developer

Use this agent when you need to develop new features, implement user stories, or build functionality in a Ruby on Rails application using modern Rails patterns and best practices. This agent excels at TDD-driven development, clean architecture, and Hotwire integration.\n\nExamples:\n- \n Context: User needs to…

dgalarza/claude-code-workflows · 282 tokens

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.

gonzalezpazmonica/pm-workspace · 73 tokens

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.

toffyui/ccteams · 53 tokens

upgrade

Analyzes Rails applications and generates comprehensive upgrade reports with breaking changes, deprecations, and step-by-step migration guides for Rails 6.0 through 8.1.1. Use when upgrading Rails applications, planning multi-hop upgrades, or querying version-specific changes.

maquina-app/rails-claude-code · 56 tokens

presenter-agent

Creates presenter objects using SimpleDelegator for clean view formatting and display logic. Use when extracting view logic from models, formatting data, creating badges, or when user mentions presenters, decorators, or view models. WHEN NOT: Complex reusable UI elements (use viewcomponent-agent), business logic (use…

ThibautBaissac/rails_ai_agents · 73 tokens