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/sethdford/flowxWrote 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/sethdford/flowx/flowx-help)<a href="https://agentmods.dev/commands/sethdford/flowx/flowx-help"><img src="https://agentmods.dev/badge/commands/sethdford/flowx/flowx-help/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.
<a href="https://agentmods.dev/commands/sethdford/flowx/flowx-help"><img src="https://agentmods.dev/badge/commands/sethdford/flowx/flowx-help.svg" alt="Reviewed on agentmods" width="80" 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.00014 | $0.01184 |
| Opus 5.5 | $0.00006 | $0.00474 |
| Sonnet 5.5 | $0.00003 | $0.00237 |
| Haiku 4.5 | $0.00001 | $0.00118 |
Grade A, and why
flowx-help 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 2mo 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FlowX Commands (Batchtools Optimized)
Core Commands with Batch Operations
System Management (Batch Operations)
npx flowx start- Start orchestration systemnpx flowx status- Check system statusnpx flowx monitor- Real-time monitoringnpx flowx stop- Stop orchestration
Batch Operations:
# Check multiple system components in parallel
npx flowx batch status --components "agents,tasks,memory,connections"
# Start multiple services concurrently
npx flowx batch start --services "monitor,scheduler,coordinator"
Agent Management (Parallel Operations)
npx flowx agent spawn <type>- Create new agentnpx flowx agent list- List active agentsnpx flowx agent info <id>- Agent detailsnpx flowx agent terminate <id>- Stop agent
Batch Operations:
# Spawn multiple agents in parallel
npx flowx agent batch-spawn "code:3,test:2,review:1"
# Get info for multiple agents concurrently
npx flowx agent batch-info "agent1,agent2,agent3"
# Terminate multiple agents
npx flowx agent batch-terminate --pattern "test-*"
Task Management (Concurrent Processing)
npx flowx task create <type> "description"- Create tasknpx flowx task list- List all tasksnpx flowx task status <id>- Task statusnpx flowx task cancel <id>- Cancel task
Batch Operations:
# Create multiple tasks from file
npx flowx task batch-create tasks.json
# Check status of multiple tasks concurrently
npx flowx task batch-status --ids "task1,task2,task3"
# Process task queue in parallel
npx flowx task process-queue --parallel 5
Memory Operations (Bulk Processing)
npx flowx memory store "key" "value"- Store datanpx flowx memory query "search"- Search memorynpx flowx memory stats- Memory statisticsnpx flowx memory export <file>- Export memory
Batch Operations:
# Bulk store from JSON file
npx flowx memory batch-store data.json
# Parallel query across namespaces
npx flowx memory batch-query "search term" --namespaces "all"
# Export multiple namespaces concurrently
npx flowx memory batch-export --namespaces "project,agents,tasks"
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.
- 2mo ago First seen · 157 lines · 14 tokens per session scan A be48d1399b35
flowx-help is a command published in the GitHub repository sethdford/flowx (2 stars, last pushed 3mo ago), licensed MIT. It adds 14 tokens to every session and 1,184 once invoked, about $0.0001 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-08-31.
flowx-help compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| flowx-helpsethdford/flowx | Command | 2 | 3mo ago | MIT | A | 14 | Claude Code |
| checklistgithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| clarifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 27 | Claude Code |
| specifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| analyzegithub/spec-kit | Command | 148k | yesterday | MIT | A | 26 | Claude Code |
| convergegithub/spec-kit | Command | 148k | yesterday | MIT | A | 35 | Claude Code |
| implementgithub/spec-kit | Command | 148k | yesterday | MIT | A | 14 | Claude Code |