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 skills/ag0os/rails-dev-plugin/hotwire-patternsnpx skills add ag0os/rails-dev-plugin --skill hotwire-patternsgit clone --depth 1 https://github.com/ag0os/rails-dev-pluginWhat 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.00073 | $0.01286 |
| Opus 5 | $0.00036 | $0.00643 |
| Sonnet 5 | $0.00015 | $0.00257 |
| Haiku 4.5 | $0.00007 | $0.00129 |
Grade A, and why
hotwire-patterns 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hotwire Patterns for Rails
Analyze and recommend Stimulus + Turbo patterns for modern, interactive Rails applications.
Applies on the html delivery axis (Axis B, rails-stack-profiles). An api-delivery project has no server-rendered views and does not use Hotwire — use rails-api-patterns instead.
Quick Reference
| Component | Use When |
|---|---|
| Stimulus | Adding JS behaviors to server-rendered HTML |
| Turbo Drive | Default for all links/forms (no config needed) |
| Turbo Frames | Update a section without full reload |
| Turbo Streams | Update multiple DOM elements from one response |
| ActionCable + Streams | Push real-time updates to connected clients |
Supporting Documentation
- stimulus.md - Stimulus integration patterns and production gotchas
- turbo.md - Turbo Frames, Streams, and version-aware patterns
Core Philosophy
HTML over the wire: Send HTML from the server, not JSON. JavaScript enhances server-rendered HTML.
- Progressive enhancement: Works without JS, better with it
- Server-first: Business logic stays on the server
- Minimal JavaScript: Just enough JS to make HTML interactive
- No client-side state: Server is the source of truth
Decision Guide: Frames vs Streams
| Scenario | Use | Why |
|---|---|---|
| Edit-in-place | Frame | Scoped navigation, replaces itself |
| Form creates item + updates counter | Stream | Multiple targets from one response |
| Lazy sidebar | Frame with loading: :lazy |
Deferred load, single target |
| Real-time chat | ActionCable + Stream | Push from server to all clients |
| Tabs/pagination | Frame | Scoped replacement |
| Flash + content update | Stream | Two targets: flash div + content |
ActionCable + Stimulus Integration
This pattern is non-obvious -- it wires a Stimulus controller to an ActionCable subscription, giving you lifecycle-managed real-time behavior:
// app/javascript/controllers/chat_controller.js
import { Controller } from "@hotwired/stimulus"
import consumer from "../channels/consumer"
export default class extends Controller {
static targets = ["messages", "input"]
static values = { roomId: Number }
connect() {
this.subscription = consumer.subscriptions.create(
{ channel: "ChatChannel", room_id: this.roomIdValue },
{ received: (data) => this.messagesTarget.insertAdjacentHTML("beforeend", data.html) }
)
}
disconnect() { this.subscription?.unsubscribe() }
send(e) {
e.preventDefault()
if (this.inputTarget.value.trim()) {
this.subscription.send({ message: this.inputTarget.value })
this.inputTarget.value = ""
}
}
}
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 141 lines · 73 tokens per session scan A b56bd27e1526
hotwire-patterns is a skill published in the GitHub repository ag0os/rails-dev-plugin (5 stars, last pushed 3mo ago), licensed MIT. It adds 73 tokens to every session and 1,286 once invoked, about $0.0004 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…