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 skills add davidteren/hotwire-codex-skills --skill turbo-morphinggit clone --depth 1 https://github.com/davidteren/hotwire-codex-skillsWrote 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/skills/davidteren/hotwire-codex-skills/turbo-morphing)<a href="https://agentmods.dev/skills/davidteren/hotwire-codex-skills/turbo-morphing"><img src="https://agentmods.dev/badge/skills/davidteren/hotwire-codex-skills/turbo-morphing/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/skills/davidteren/hotwire-codex-skills/turbo-morphing"><img src="https://agentmods.dev/badge/skills/davidteren/hotwire-codex-skills/turbo-morphing.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.00108 | $0.00919 |
| Opus 5 | $0.00054 | $0.00460 |
| Sonnet 5 | $0.00022 | $0.00184 |
| Haiku 4.5 | $0.00011 | $0.00092 |
Grade A, and why
turbo-morphing 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 11d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Turbo 8 morphing & page refreshes
Turbo 8 added a second update model alongside targeted Turbo Streams: page refreshes with morphing. Render the current page again (e.g. submit → redirect back) and Turbo morphs only the changed DOM via idiomorph, preserving screen state. It's the simpler "happy path" — but it has sharp edges. This skill helps you pick the right tool and avoid the footguns.
Full background: references/morphing-guide.md. Real-world note:
piazza-web/wip/analysis/08-turbo8-morphing-refreshes.md.
When to use
- Adding
turbo_refreshes_with method: :morph, scroll: :preserve. - Broadcasting live updates and considering
broadcasts_refreshesvs targeted streams. - Morphing resets UI state (a
<details>reopens for everyone, a popover closes, scroll jumps, a JS-initialized widget breaks) after a refresh/broadcast. - Reviewing a PR that enables morphing, especially in the global layout.
Decision guide
| Need | Use |
|---|---|
| Submit-and-redirect-back with many small scattered changes | morph page refresh: turbo_refreshes_with method: :morph |
| Live multi-user updates, simplest server code, "good enough" fidelity | broadcasts_refreshes + turbo_stream_from @record |
| High-fidelity append/prepend (chat), surgical control | targeted streams (broadcast_append_to, etc.) |
Reload one region during a full-page refresh / explicit .reload() |
frame with refresh="morph" |
| Morph a single element instead of replacing it | turbo_stream.replace id, ..., method: :morph |
Mantra (37signals): morphing is an implementation detail of a page refresh, not a new partial-update tool. Use targeted streams when you need precision.
broadcasts_refreshes (the simplification)
class Listing < ApplicationRecord
broadcasts_refreshes # after create/update/destroy → <turbo-stream action="refresh">
end
<%= turbo_stream_from @listing %>
<%= turbo_refreshes_with method: :morph, scroll: :preserve %>
Async via Turbo::Streams::BroadcastJob (needs a job backend), auto-debounced
(only the last of a burst), and self-refreshes are deduped via X-Turbo-Request-Id.
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.
- 11d ago First seen · 75 lines · 108 tokens per session scan A b8765992eca9
turbo-morphing is a skill published in the GitHub repository davidteren/hotwire-codex-skills (3 stars, last pushed 2mo ago), licensed MIT. It adds 108 tokens to every session and 919 once invoked, about $0.0005 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
create-mobile-app
Use when the user wants to start a new Power Apps mobile app (Expo / React Native / TypeScript, targeting iOS and Android) from scratch.
app-builder
(Preview) Builds and edits a model-driven Power Apps app from a natural-language intent — tables, columns, relationships, adaptive forms with sub-grids, views, Choice-column charts, business rules, business process flows, generative page intents for overview/dashboard surfaces (page .tsx generated in generate-pages…
create-site
Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…
genpage
Creates, updates, and deploys Power Apps generative pages for model-driven apps using React v17, TypeScript, and Fluent UI V9. Orchestrates specialist agents for planning, entity creation, and code generation. Use it when user asks to build, retrieve, or update a page in an existing Microsoft Power Apps model-driven…
migrate-bootstrap
Migrates a traditional Power Pages site from Bootstrap 3 to Bootstrap 5. Downloads the site, runs the pac pages bootstrap-migrate engine, reviews the change report, applies AI-assisted fixes for the residual hierarchy/CSS changes the engine only flags, uploads the migrated site (which auto-enables the Bootstrap 5…
canvas-app
Creates or edits a Power Apps Canvas App through the Canvas Authoring MCP coauthoring session. Handles new app generation, direct targeted edits, complex multi-screen changes, responsive layout, per-screen self-QA, and compile-error convergence. Trigger on requests to create, build, generate, modify, update, change…