hot_reload

A project rule for Dart and Flutter edits that connects to a running app and triggers hot reload. Hot reload applies code changes to a running app without starting it from scratch.

In plain words
What is it for?
Use it after editing Dart or Flutter files to connect through the DTD tool and push the changes with hot reload.
Why use it?
It helps you see code changes immediately during development and makes clear when no app is available to reload.

Cursor rule

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 rules/flutter/agent-plugins/hot_reload
Clone the repo
git clone --depth 1 https://github.com/flutter/agent-plugins
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 101 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.00000 $0.00101
Opus 5 $0.00000 $0.00051
Sonnet 5 $0.00000 $0.00020
Haiku 4.5 $0.00000 $0.00010

Measured yesterday against content hash f0f9a4379571, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

hot_reload 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 yesterday.

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.

rules/hot_reload.mdc · 10 lines

What it actually says

Whenever you make edits to any Dart or Flutter files in this project:

  1. Proactively connect to the running application using the dtd tool and its subcommands. Make sure to read the schema for this tool.
  2. Trigger a hot reload using the hot_reload tool to push the changes immediately.
  3. If no app is running, inform the user but do not let it stop you from completing the code edits.
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. yesterday First seen · 10 lines · 101 tokens per session scan A f0f9a4379571

Subscribe to this mod's changes

hot_reload is a cursor rule published in the GitHub repository flutter/agent-plugins (2,895 stars, last pushed 3d ago), licensed BSD-3-Clause. It costs nothing until one of its globs matches a file; then it loads 101 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.