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/soulcynics404/agentforge/swarm-initgit clone --depth 1 https://github.com/Soulcynics404/AgentForgeWrote 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/soulcynics404/agentforge/swarm-init)<a href="https://agentmods.dev/commands/soulcynics404/agentforge/swarm-init"><img src="https://agentmods.dev/badge/commands/soulcynics404/agentforge/swarm-init.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.00482 |
| Opus 5 | $0.00000 | $0.00241 |
| Sonnet 5 | $0.00000 | $0.00096 |
| Haiku 4.5 | $0.00000 | $0.00048 |
Grade A, and why
swarm-init 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 yesterday.
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 swarm-init — 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
swarm init
Initialize a Claude Flow swarm with specified topology and configuration.
Usage
npx claude-flow swarm init [options]
Options
--topology, -t <type>- Swarm topology: mesh, hierarchical, ring, star (default: hierarchical)--max-agents, -m <number>- Maximum number of agents (default: 8)--strategy, -s <type>- Execution strategy: balanced, parallel, sequential (default: parallel)--auto-spawn- Automatically spawn agents based on task complexity--memory- Enable cross-session memory persistence--github- Enable GitHub integration features
Examples
Basic initialization
npx claude-flow swarm init
Mesh topology for research
npx claude-flow swarm init --topology mesh --max-agents 5 --strategy balanced
Hierarchical for development
npx claude-flow swarm init --topology hierarchical --max-agents 10 --strategy parallel --auto-spawn
GitHub-focused swarm
npx claude-flow swarm init --topology star --github --memory
Topologies
Mesh
- All agents connect to all others
- Best for: Research, exploration, brainstorming
- Communication: High overhead, maximum information sharing
Hierarchical
- Tree structure with clear command chain
- Best for: Development, structured tasks, large projects
- Communication: Efficient, clear responsibilities
Ring
- Agents connect in a circle
- Best for: Pipeline processing, sequential workflows
- Communication: Low overhead, ordered processing
Star
- Central coordinator with satellite agents
- Best for: Simple tasks, centralized control
- Communication: Minimal overhead, clear coordination
Integration with Claude Code
Once initialized, use MCP tools in Claude Code:
mcp__claude-flow__swarm_init { topology: "hierarchical", maxAgents: 8 }
See Also
agent spawn- Create swarm agentstask orchestrate- Coordinate task executionswarm status- Check swarm stateswarm monitor- Real-time monitoring
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.
- yesterday First seen · 86 lines · 0 tokens per session scan A adb339d92778
swarm-init is a command published in the GitHub repository Soulcynics404/AgentForge (1 stars, last pushed 11d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 482 tokens. A static security scan graded it A with 0 findings. It is 100% identical to swarm-init, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
agentos-status
Show AgentOS system status — agents, workers, health.
agentos-tui
Launch the AgentOS TUI dashboard.
specsync-create-spec
Create a new spec-sync module spec.
create-change
Create and guide a verified spec-sync SDD change through its deterministic interview.
agentos-evolve
Quick evolve a function — generate, register, and evaluate.
agentos-chat
Send a message to an AgentOS agent.