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/hgahlot/claude-flow/updategit clone --depth 1 https://github.com/hgahlot/claude-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/hgahlot/claude-flow/update)<a href="https://agentmods.dev/commands/hgahlot/claude-flow/update"><img src="https://agentmods.dev/badge/commands/hgahlot/claude-flow/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 | $0.00000 | $0.00604 |
| Opus 5 | $0.00000 | $0.00302 |
| Sonnet 5 | $0.00000 | $0.00121 |
| Haiku 4.5 | $0.00000 | $0.00060 |
Grade A, and why
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 5d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the update manager for the claude-flow development environment. Your job is to update all underlying tools to their latest versions and re-apply the flow integration layer.
How to respond
Step 1: Run the update script
If the user wants to check for updates without applying:
bash /tmp/claude-flow/update.sh --check
If the user wants to update everything:
bash /tmp/claude-flow/update.sh
If the user wants to update a specific tool:
bash /tmp/claude-flow/update.sh --tool <name>
Valid tool names: gsd, gstack, superpowers, claude-mem, uipro, ralph, flow
If /tmp/claude-flow doesn't exist, clone it first:
git clone --depth 1 https://github.com/hgahlot/claude-flow.git /tmp/claude-flow && bash /tmp/claude-flow/update.sh
Step 2: Report results
Present the output clearly. If any tools failed, explain what went wrong and how to fix it manually.
Step 3: If tools were updated, verify integration
After updates, run the health check to verify everything still works:
node .claude/hooks/session-health-check.js
If the health check reports issues, help fix them.
What gets updated
| Tool | Update method | Location |
|---|---|---|
| GSD | npx get-shit-done-cc@latest |
.claude/commands/gsd/ |
| gstack | git pull |
~/.claude/skills/gstack/ |
| Superpowers | git pull |
~/.claude/plugins/obra/superpowers/ |
| Claude-Mem | git pull + bun install |
~/.claude/plugins/marketplaces/thedotmack/ |
| UI/UX Pro Max | npx uipro-cli init |
.claude/skills/ui-ux-pro-max/ |
| ralph-wiggum | bun add -g |
~/.bun/bin/ralph |
| flow | git pull + re-copy commands/hooks |
.claude/commands/, .claude/hooks/ |
Integration safety
After tool updates, the script automatically:
- Re-copies flow commands (
/flow,/plan,/tdd, etc.) if the upstream versions changed - Re-copies the session health check hook if updated
- Warns if
CLAUDE.mdtemplate has new routing rules (won't overwrite your customized version) - Ensures settings.json still has the health check hook registered
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.
- 5d ago First seen · 65 lines · 0 tokens per session scan A 97889e8e7d9b
update is a command published in the GitHub repository hgahlot/claude-flow (54 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 604 tokens. 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
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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.