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-swarm)<a href="https://agentmods.dev/commands/sethdford/flowx/flowx-swarm"><img src="https://agentmods.dev/badge/commands/sethdford/flowx/flowx-swarm/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-swarm"><img src="https://agentmods.dev/badge/commands/sethdford/flowx/flowx-swarm.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.00017 | $0.02007 |
| Opus 5.5 | $0.00007 | $0.00803 |
| Sonnet 5.5 | $0.00003 | $0.00401 |
| Haiku 4.5 | $0.00002 | $0.00201 |
Grade A, and why
flowx-swarm 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 — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FlowX Swarm Coordination (Batchtools Optimized)
Swarm mode with batchtools enables massively parallel multi-agent coordination for complex tasks with enhanced efficiency.
Enhanced Basic Usage
# Traditional single swarm
npx flowx swarm "your complex task" --strategy <type> [options]
# Batch swarm operations
npx flowx swarm batch --tasks "frontend:dev,backend:dev,database:architect" --parallel
Parallel Strategy Execution
# Execute multiple strategies concurrently
npx flowx swarm multi-strategy --config '{
"frontend": { "strategy": "development", "agents": 3 },
"backend": { "strategy": "development", "agents": 4 },
"testing": { "strategy": "testing", "agents": 2 },
"docs": { "strategy": "documentation", "agents": 1 }
}' --parallel --monitor
Enhanced Strategies with Batch Operations
development- Parallel code implementation across modulesresearch- Concurrent information gathering from multiple sourcesanalysis- Parallel data processing pipelinestesting- Concurrent test suite executionoptimization- Parallel performance analysismaintenance- Batch system updatessecurity- Parallel vulnerability scanningdeployment- Concurrent multi-environment deployment
Advanced Batch Options
--parallel-tasks <n>- Number of concurrent tasks--batch-size <n>- Task batch size for processing--pipeline- Enable pipeline parallelization--shard- Distribute work across shards--replicate <n>- Replicate critical tasks--failover- Enable automatic failover--load-balance- Dynamic load balancing--auto-scale- Automatic agent scaling
Batch Examples
Parallel Development Swarm
# Develop multiple microservices concurrently
npx flowx swarm batch-dev --services '{
"auth-service": { "agents": 3, "priority": "high" },
"user-service": { "agents": 2, "priority": "medium" },
"order-service": { "agents": 3, "priority": "high" },
"payment-service": { "agents": 2, "priority": "critical" }
}' --parallel --monitor --auto-scale
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 · 225 lines · 17 tokens per session scan A 5df92a9a2afb
flowx-swarm is a command published in the GitHub repository sethdford/flowx (2 stars, last pushed 3mo ago), licensed MIT. It adds 17 tokens to every session and 2,007 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-swarm compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| flowx-swarmsethdford/flowx | Command | 2 | 3mo ago | MIT | A | 17 | 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 |