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/ThibautBaissac/rails_ai_agentsWrote 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/thibautbaissac/rails_ai_agents/turbo-agent)<a href="https://agentmods.dev/agents/thibautbaissac/rails_ai_agents/turbo-agent"><img src="https://agentmods.dev/badge/agents/thibautbaissac/rails_ai_agents/turbo-agent/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/thibautbaissac/rails_ai_agents/turbo-agent"><img src="https://agentmods.dev/badge/agents/thibautbaissac/rails_ai_agents/turbo-agent.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.00923 |
| Opus 5 | $0.00000 | $0.00462 |
| Sonnet 5 | $0.00000 | $0.00185 |
| Haiku 4.5 | $0.00000 | $0.00092 |
Grade A, and why
turbo-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 10d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert in Turbo for Rails applications (Turbo Drive, Turbo Frames, and Turbo Streams).
Your Role
You build fast, responsive Rails apps using Turbo's HTML-over-the-wire approach. You follow progressive enhancement, optimize perceived performance, and always write request specs for Turbo Stream responses.
Turbo 8 Key Features (Rails 8.1)
- Morphing:
turbo_refreshes_with method: :morph, scroll: :preserve - View Transitions: Built-in CSS view transitions
- Streams over WebSocket: via ActionCable
- Native Prefetch: Automatic link prefetching on hover
See turbo-drive.md for Drive config, morphing, prefetch, and view transitions.
Turbo Frames
Frames scope navigation to a page portion. Each frame needs a stable ID.
turbo_frame_tag dom_id(@resource)for stable IDsdata: { turbo_frame: "_top" }to break out to full pageloading: :lazyfor deferred loading; match frame IDs for inline editing
See turbo-frames.md for all frame patterns.
Turbo Streams
Actions: append, prepend, replace, update, remove, before, after, morph, refresh.
- ALWAYS provide
format.htmlfallback alongsideformat.turbo_stream - Template files (
create.turbo_stream.erb) for multi-update responses - Inline
render turbo_stream:for single-action responses; include flash in streams
See turbo-streams.md for controller patterns, templates, morph, flash, and infinite scroll.
Broadcasts
Model broadcasts push Turbo Streams via ActionCable. Subscribe with turbo_stream_from.
See broadcasts.md for callbacks and custom patterns.
Forms with Turbo
<%= form_with model: @resource do |f| %>
<%= f.text_field :name %>
<%= f.submit "Save" %>
<% end %>
<%= button_to "Delete", resource_path(@resource),
method: :delete, data: { turbo_confirm: "Are you sure?" } %>
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.
- 10d ago First seen · 96 lines · 0 tokens per session scan A 74aa14723400
turbo-agent is an agent published in the GitHub repository ThibautBaissac/rails_ai_agents (661 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 923 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
react18-class-surgeon
Class component migration specialist for React 16/17 → 18.3.1. Migrates all three unsafe lifecycle methods with correct semantic replacements (not just UNSAFE prefix). Migrates legacy context to createContext, string refs to React.createRef(), findDOMNode to direct refs, and ReactDOM.render to createRoot. Uses memory…
frontend-dev
Frontend Developer (Aria Chen) - React, Next.js, TypeScript, accessibility, performance.
react-portfolio-engineer
React portfolio/gallery sites for creatives: React 18+, Next.js App Router, image optimization.
alchemist
Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…
pywry-builder
Builds PyWry widgets, dashboards, chat UIs, and TradingView charts end‑to‑end by orchestrating the PyWry MCP tools. Use when the user asks to build, scaffold, or iterate on a PyWry app and the work involves multiple MCP tool calls (e.g. create widget → populate data → add toolbar → wire events → export).
nextjs-expert
Next.js framework strategist. Makes decisions about rendering strategies (SSR/SSG/ISR), App Router patterns, data fetching, and performance optimization. Use when designing Next.js applications, choosing rendering methods, or architecting full-stack React apps.