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/ThierryN/fire-flowWrote 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/thierryn/fire-flow/fire-update)<a href="https://agentmods.dev/commands/thierryn/fire-flow/fire-update"><img src="https://agentmods.dev/badge/commands/thierryn/fire-flow/fire-update.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.00010 | $0.01814 |
| Opus 5 | $0.00005 | $0.00907 |
| Sonnet 5 | $0.00002 | $0.00363 |
| Haiku 4.5 | $0.00001 | $0.00181 |
Grade A, and why
fire-update 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 3d 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 — 313 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/fire-update
Check for plugin updates, view changelog, and apply updates from GitHub
Purpose
Automatic update system for Dominion Flow plugin that pulls updates from GitHub, maintains version history, and creates backups before updating. Ensures you always have the latest features and fixes.
Commands:
/fire-update check- Check for available updates/fire-update apply- Apply available updates/fire-update history- View update history/fire-update version- Show current version/fire-update rollback- Rollback to previous version
Arguments
arguments:
action:
required: false
type: string
enum: [check, apply, history, version, rollback]
default: check
description: "Update action to perform"
force:
required: false
type: boolean
default: false
description: "Force update even if on modified branch"
examples:
- "/fire-update" - Check for available updates
- "/fire-update check" - Check for updates with details
- "/fire-update apply" - Apply available updates
- "/fire-update history" - View update history
- "/fire-update rollback" - Rollback to previous version
Configuration
GitHub Repository Setup
The plugin must have a GitHub repository configured in plugin.json:
{
"repository": "https://github.com/username/dominion-flow"
}
If repository is not configured:
⚠️ No repository configured for updates
To enable updates, add repository URL to plugin.json:
{
"repository": "https://github.com/username/dominion-flow"
}
Process: Check for Updates
Step 1: Validate Environment
PLUGIN_DIR="$HOME/.claude/plugins/dominion-flow"
VERSION_FILE="$PLUGIN_DIR/version.json"
PLUGIN_JSON="$PLUGIN_DIR/.claude-plugin/plugin.json"
Verify plugin directory exists and is a git repository:
cd "$PLUGIN_DIR"
if [ ! -d ".git" ]; then
echo "Error: Not a git repository"
exit 1
fi
Step 2: Load Current Version
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.
- 3d ago First seen · 313 lines · 10 tokens per session scan A 1f944724a8b8
fire-update is a command published in the GitHub repository ThierryN/fire-flow (77 stars, last pushed 25d ago), licensed MIT. It adds 10 tokens to every session and 1,814 once invoked, about $0.0001 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-09-03.
Other commands, from other repositories
update-documentation
You are a release engineer responsible for maintaining the root-level CHANGELOG.md and verifying plugin READMEs. Analyze git changes, update the single CHANGELOG.md following the Keep a Changelog format organized by plugin, and ensure plugin READMEs accurately reflect their contents.
ship
Pre-ship pipeline — test, review, then prepare a clean commit.
explore-release
This legacy command is a rename notice only. Its workflow is now rpi-explore-release.
ship
Agent mode. Verify, then deliver via scripts/ship.ps1 (repo-agnostic).
release
../../templates/commands/release.md.
t00-git
A Git assistant that explains version-control commands and guides work with commits, branches, merges, pull requests, and conflicts. Git records code changes so developers can review, restore, and share versions.