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/f-amine/vibe-stackWrote 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/f-amine/vibe-stack/claude-flow-swarm)<a href="https://agentmods.dev/commands/f-amine/vibe-stack/claude-flow-swarm"><img src="https://agentmods.dev/badge/commands/f-amine/vibe-stack/claude-flow-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/f-amine/vibe-stack/claude-flow-swarm"><img src="https://agentmods.dev/badge/commands/f-amine/vibe-stack/claude-flow-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.00014 | $0.01225 |
| Opus 5.5 | $0.00006 | $0.00490 |
| Sonnet 5.5 | $0.00003 | $0.00245 |
| Haiku 4.5 | $0.00001 | $0.00122 |
Grade A, and why
claude-flow-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 1mo 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.
This is a copy
100% identical to claude-flow-swarm — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🐝 Claude-Flow Swarm Coordination
Advanced multi-agent coordination system with timeout-free execution, distributed memory sharing, and intelligent load balancing.
Basic Usage
./claude-flow swarm "your complex task" --strategy <type> [options]
🎯 Swarm Strategies
- auto - Automatic strategy selection based on task analysis
- development - Code implementation with review and testing
- research - Information gathering and synthesis
- analysis - Data processing and pattern identification
- testing - Comprehensive quality assurance
- optimization - Performance tuning and refactoring
- maintenance - System updates and bug fixes
🤖 Agent Types
- coordinator - Plans and delegates tasks to other agents
- developer - Writes code and implements solutions
- researcher - Gathers and analyzes information
- analyzer - Identifies patterns and generates insights
- tester - Creates and runs tests for quality assurance
- reviewer - Performs code and design reviews
- documenter - Creates documentation and guides
- monitor - Tracks performance and system health
- specialist - Domain-specific expert agents
🔄 Coordination Modes
- centralized - Single coordinator manages all agents (default)
- distributed - Multiple coordinators share management
- hierarchical - Tree structure with nested coordination
- mesh - Peer-to-peer agent collaboration
- hybrid - Mixed coordination strategies
⚙️ Common Options
--strategy <type>- Execution strategy--mode <type>- Coordination mode--max-agents <n>- Maximum concurrent agents (default: 5)--timeout <minutes>- Timeout in minutes (default: 60)--background- Run in background for tasks > 30 minutes--monitor- Enable real-time monitoring--ui- Launch terminal UI interface--parallel- Enable parallel execution--distributed- Enable distributed coordination--review- Enable peer review process--testing- Include automated testing--encryption- Enable data encryption--verbose- Detailed logging output--dry-run- Show configuration without executing
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.
- 1mo ago First seen · 206 lines · 14 tokens per session scan A 14778c8413d9
claude-flow-swarm is a command published in the GitHub repository f-amine/vibe-stack (21 stars, last pushed 3mo ago), licensed MIT. It adds 14 tokens to every session and 1,225 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to claude-flow-swarm, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
add
Add addons or a workspace package to the current Better-T-Stack project. Plans the change, confirms it with you, then applies it.
new
Scaffold a new Better-T-Stack project. Plans a validated stack, confirms it with you, then generates it.
plan
PM planning workflow that gathers requirements, decomposes them into prioritized tasks, defines API contracts, and produces both a machine-readable plan and a human-readable tracker in docs/plans/.
tools
Manage MCP tools with natural language commands to list, enable, and disable tools and tool groups.
audit-code
When /audit-code [target] is invoked, immediately execute the following steps to analyze code quality, security, and adherence to project standards.
checklist
Generate a custom checklist for the current feature based on user requirements.