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 commands/gmickel/flow-next/uninstallgit clone --depth 1 https://github.com/gmickel/flow-nextWrote 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/commands/gmickel/flow-next/uninstall)<a href="https://agentmods.dev/commands/gmickel/flow-next/uninstall"><img src="https://agentmods.dev/badge/commands/gmickel/flow-next/uninstall.svg" alt="Measured on agentmods" 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.00009 | $0.00912 |
| Opus 5 | $0.00005 | $0.00456 |
| Sonnet 5 | $0.00002 | $0.00182 |
| Haiku 4.5 | $0.00001 | $0.00091 |
Grade C, and why
uninstall scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf .flow/bin .flow/templates .flow/usage.md How it starts
The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flow-Next Uninstall
Use AskUserQuestion to confirm:
Question 1: "Remove flow-next from this project?"
- "Yes, uninstall"
- "Cancel"
If cancel → stop.
Question 2: "Keep your .flow/ tasks and specs?"
- "Yes, keep tasks" → partial uninstall
- "No, remove everything" → full uninstall
Generate removal instructions
Based on answers, generate the appropriate commands and print them for the user to run manually.
If keeping tasks:
Setup copies nothing into the repo, so uninstall is marker removal: strip the <!-- BEGIN FLOW-NEXT -->...<!-- END FLOW-NEXT --> block from CLAUDE.md / AGENTS.md (the "Clean up docs" section below does that) and remove the setup_version / setup_mode stamps from .flow/meta.json.
Legacy cleanup — only when those paths actually exist (repos set up before copy-less installs). Print this for the user to run manually; omit it entirely when none exist:
To complete uninstall, run these commands manually:
rm -rf .flow/bin .flow/templates .flow/usage.md
If removing everything:
To complete uninstall, run these commands manually:
rm -rf .flow
Always check for Ralph and add if exists:
# Check if Ralph is installed
if [[ -d scripts/ralph ]]; then
echo "rm -rf scripts/ralph"
fi
Remove Ralph guard hook entries (AI can do this)
Plugin installs no longer ship hooks. Any Ralph guard entries live in project settings, registered by /flow-next:ralph-init. Strip them the same way setup does on "No":
Fingerprint: nested hook command contains scripts/ralph/hooks/ralph-guard.
For each path that exists, Read then Edit (never clobber unrelated hooks; if the file becomes empty hooks-only, delete the file or remove the empty hooks key):
| Host | Path |
|---|---|
| Claude Code / Grok | .claude/settings.json (hooks key) |
| Factory Droid | .factory/hooks.json (primary); also strip under .factory/settings.json hooks if present |
| Codex | .codex/hooks.json |
Do not introduce a flowctl hook-remove command. Agent-driven Read+Edit only.
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 · 91 lines · 9 tokens per session scan C febef9f36864
uninstall is a command published in the GitHub repository gmickel/flow-next (691 stars, last pushed today), licensed MIT. It adds 9 tokens to every session and 912 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other commands, from other repositories
make
Create structured implementation plan in docs/plans/.
speckit.checklist
Generate a custom checklist for the current feature based on user requirements.
speckit.clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
speckit.specify
Create or update the feature specification from a natural language feature description.
speckit.implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.