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/thierryn/fire-flow/fire-loop-resumegit clone --depth 1 https://github.com/ThierryN/fire-flowWhat 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 | $0.00010 | $0.01651 |
| Opus 5 | $0.00005 | $0.00826 |
| Sonnet 5 | $0.00002 | $0.00330 |
| Haiku 4.5 | $0.00001 | $0.00165 |
Grade B, and why
fire-loop-resume scanned grade B 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 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
LOOP_ID=$(grep "Loop ID:" .claude/dominion-flow.local.md | head -1 | cut -d: -f2 | xargs) How it starts
The opening of the file, as written. The whole thing — 273 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/fire-loop-resume
Resume Power Loop from Sabbath Rest snapshot with full context restoration
Purpose
Resume a Power Loop that was:
- Paused due to Sabbath Rest (context rot warning)
- Stopped by user via
/fire-loop-stop - Interrupted by session end
This command restores context from the Sabbath Rest snapshot and continues the loop with fresh context.
Arguments
arguments:
loop_id:
required: false
type: string
description: "Loop ID to resume (omit to resume most recent)"
example: "/fire-loop-resume 20260123-143052"
Process
Step 1: Find Loop to Resume
If LOOP_ID provided:
SABBATH_FILE=$(ls .planning/loops/sabbath-${LOOP_ID}*.md 2>/dev/null | head -1)
If no LOOP_ID (resume most recent):
# Check Sabbath Rest state first
if [ -f ".claude/dominion-flow.local.md" ]; then
LOOP_ID=$(grep "Loop ID:" .claude/dominion-flow.local.md | head -1 | cut -d: -f2 | xargs)
fi
# Or find most recent sabbath file
SABBATH_FILE=$(ls -t .planning/loops/sabbath-*.md 2>/dev/null | head -1)
Step 2: Validate Sabbath File Exists
if [ ! -f "$SABBATH_FILE" ]; then
echo "No Sabbath Rest snapshot found for loop ${LOOP_ID}"
echo "Available loops:"
ls .planning/loops/*.md
exit 1
fi
Step 3: Load Sabbath Rest Context
Read the Sabbath snapshot and extract:
From sabbath file:
- loop_id
- iteration (where we stopped)
- original prompt
- files modified
- hypotheses tested
- next steps
- key context to restore
Step 4: Display Context Restoration
+------------------------------------------------------------------------------+
| POWER LOOP RESUME |
+------------------------------------------------------------------------------+
| |
| Restoring Loop: ${LOOP_ID} |
| Paused At: Iteration [N] |
| Reason: [context_rot | user_stop | session_end] |
| |
| Sabbath Rest Snapshot: |
| ${SABBATH_FILE} |
| |
+------------------------------------------------------------------------------+
| RESTORED CONTEXT |
+------------------------------------------------------------------------------+
| |
| Progress Summary: |
| [from sabbath file] |
| |
| Files Modified: |
| - [file]: [change] |
| - [file]: [change] |
| |
| Key Context: |
| [critical information from sabbath file] |
| |
| Immediate Next Step: |
| [exactly what to do] |
| |
+------------------------------------------------------------------------------+
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 · 273 lines · 10 tokens per session scan B 4c5b3ec5a638
fire-loop-resume is a command published in the GitHub repository ThierryN/fire-flow (77 stars, last pushed 21d ago), licensed MIT. It adds 10 tokens to every session and 1,651 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
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.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.