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-skills-rollback)<a href="https://agentmods.dev/commands/thierryn/fire-flow/fire-skills-rollback"><img src="https://agentmods.dev/badge/commands/thierryn/fire-flow/fire-skills-rollback.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.00013 | $0.02518 |
| Opus 5 | $0.00006 | $0.01259 |
| Sonnet 5 | $0.00003 | $0.00504 |
| Haiku 4.5 | $0.00001 | $0.00252 |
Grade A, and why
power-skills-rollback 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 7d 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 — 409 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/fire-skills-rollback - Rollback Skill to Previous Version
Restore a skill to a previous version from the git-backed skills library.
Purpose
- Revert problematic changes to a skill
- Restore a preferred earlier version
- Undo accidental modifications
- Recover from sync conflicts
- Test against older skill patterns
Prerequisites
The skills library must be git-versioned:
~/.claude/plugins/dominion-flow/skills-library/.git/
Arguments
| Argument | Required | Description |
|---|---|---|
skill |
Yes | Skill path: {category}/{skill-name} |
version |
Yes | Target version: semantic version (e.g., 1.2.0) or commit hash |
Usage Examples
# Rollback to specific version
/fire-skills-rollback database-solutions/n-plus-1 1.2.0
# Rollback using commit hash
/fire-skills-rollback security/jwt-auth abc1234
# Rollback with confirmation skip
/fire-skills-rollback api-patterns/pagination 2.0.0 --yes
# Rollback in global library
/fire-skills-rollback performance/caching 1.0.0 --global
# Preview rollback without applying
/fire-skills-rollback testing/snapshot 1.1.0 --dry-run
Process
Verify skill and version exist:
# Check skill exists
ls ~/.claude/plugins/dominion-flow/skills-library/{category}/{skill-name}.md
# Find version in git history
cd ~/.claude/plugins/dominion-flow/skills-library
git log --oneline -- {category}/{skill-name}.md | grep -i "v{version}"
If version not found, search by semantic version in frontmatter:
# Search commits for version tag
for commit in $(git log --format=%H -- {category}/{skill-name}.md); do
version_line=$(git show $commit:{category}/{skill-name}.md 2>/dev/null | grep "^version:")
if [[ "$version_line" == *"{target-version}"* ]]; then
echo "Found: $commit"
break
fi
done
Error if not found:
Error: Version {version} not found for skill {category}/{skill-name}
Available versions:
v2.1.0 (2026-01-22) - abc1234
v2.0.0 (2026-01-15) - def5678
v1.2.0 (2026-01-08) - ghi9012
v1.1.0 (2025-12-20) - jkl3456
v1.0.0 (2025-12-15) - mno7890
Usage: /fire-skills-rollback {skill} {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.
- 7d ago First seen · 409 lines · 13 tokens per session scan A 11569ac3d5d0
power-skills-rollback is a command published in the GitHub repository ThierryN/fire-flow (77 stars, last pushed 24d ago), licensed MIT. It adds 13 tokens to every session and 2,518 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-08-30.
Other commands, from other repositories
skill-create
Generate skills from git history analysis.
epic-sync
Sync epic issue bodies, labels, and local coordination snapshots from GitHub.
explore-remote
Explore and analyze a remote GitHub repository.
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.
pack-remote
Pack and analyze a remote GitHub repository.
dev
Developer tools — debug, commit, PR, code review, refactoring.