fire-update

fire-update is a command for Claude Code from ThierryN/fire-flow. It costs 10 tokens per session (1,814 once invoked), scanned A, original, MIT.

A command for checking, applying, reviewing, and rolling back updates to a plugin downloaded from GitHub. GitHub is a service used to host and distribute source code.

In plain words
What is it for?
Use it to check available updates, apply them, view the current version or update history, and roll back to an earlier version.
Why use it?
It gives you a way to update the plugin while keeping version history and backups for recovery.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions .claude-plugin.

Part of the dominion-flow plugin — 5 skills, 51 commands, 13 agents shipped together

Good fit Use it to check available updates, apply them, view the current version or update history, and roll back to an earlier version.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/thierryn/fire-flow/fire-update
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.

Clone the repo
git clone --depth 1 https://github.com/ThierryN/fire-flow

Made for: Claude Code.

Or install dominion-flow, the plugin that ships this one along with the rest of its 5 skills, 51 commands, 13 agents.

Wrote 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.

agentmods badge for fire-update

README.md
[![agentmods](https://agentmods.dev/badge/commands/thierryn/fire-flow/fire-update/github.svg)](https://agentmods.dev/commands/thierryn/fire-flow/fire-update)
Your own site
<a href="https://agentmods.dev/commands/thierryn/fire-flow/fire-update"><img src="https://agentmods.dev/badge/commands/thierryn/fire-flow/fire-update/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.

agentmods 80×15 button for fire-update

Your own site · 80×15
<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="Reviewed on agentmods" width="80" height="20"></a>
Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,814 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00010 $0.01814
Opus 5.5 $0.00004 $0.00726
Sonnet 5.5 $0.00002 $0.00363
Haiku 4.5 $0.00001 $0.00181

Measured 1mo ago against content hash 1f944724a8b8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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.

commands/fire-update.md · 313 lines

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

Read the full file on GitHub · 313 lines

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. 1mo ago First seen · 313 lines · 10 tokens per session scan A 1f944724a8b8

Subscribe to this mod's changes

fire-update is a command published in the GitHub repository ThierryN/fire-flow (78 stars, last pushed 2mo ago), licensed MIT. It adds 10 tokens to every session and 1,814 once invoked, about $0.0000 per session on Opus 5.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.

Related

Other commands, from other repositories

release-sync

Syncs latest release content to NotebookLM and HQ Knowledge Base after version tagging. Reads CHANGELOG, CLAUDE.md, and hook README, updates notebook sources, and ingests release digest. Optionally generates podcast from updated knowledge base. Use after tagging a new version to propagate release knowledge.

yonatangross/orchestkit · 62 tokens

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.

closedloop-ai/claude-plugins · 0 tokens

release

Prepara e pubblica una nuova release del plugin mcp-legal-it. Bumpa la versione in tutti i manifest, aggiorna i changelog e la description con il conteggio tool corretto, crea il release branch, merge in main e tagga.

capazme/mcp-legal-it · 56 tokens

ship

Pre-ship pipeline — test, review, then prepare a clean commit.

dshakes/compass · 14 tokens

rebase_prompt

You are a git rebase assistant. Your job is to rebase the current branch onto origin/ and intelligently resolve any merge conflicts that arise. The repository has already been fetched and the base branch is ; you may assume origin/ is up-to-date.

fotoetienne/gru · 0 tokens

release-train

Autonomous multi-PR release train — plan stacked single-concern PRs, open each on its own branch, monitor CI, rebase on conflicts, and ship in dependency order while you sleep. Driven by report.html horizon item 'Autonomous Multi-PR Release Trains'.

naimkatiman/continuous-improvement · 60 tokens