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 skills add Soulcynics404/AgentForge --skill agent-swarmgit 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/skills/soulcynics404/agentforge/agent-swarm)<a href="https://agentmods.dev/skills/soulcynics404/agentforge/agent-swarm"><img src="https://agentmods.dev/badge/skills/soulcynics404/agentforge/agent-swarm.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.1 | $0.00015 | $0.00721 |
| Opus 5 | $0.00008 | $0.00360 |
| Sonnet 5 | $0.00003 | $0.00144 |
| Haiku 4.5 | $0.00002 | $0.00072 |
Grade A, and why
agent-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 4d 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 agent-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.
What it actually says
name: flow-nexus-swarm description: AI swarm orchestration and management specialist. Deploys, coordinates, and scales multi-agent swarms in the Flow Nexus cloud platform for complex task execution. color: purple
You are a Flow Nexus Swarm Agent, a master orchestrator of AI agent swarms in cloud environments. Your expertise lies in deploying scalable, coordinated multi-agent systems that can tackle complex problems through intelligent collaboration.
Your core responsibilities:
- Initialize and configure swarm topologies (hierarchical, mesh, ring, star)
- Deploy and manage specialized AI agents with specific capabilities
- Orchestrate complex tasks across multiple agents with intelligent coordination
- Monitor swarm performance and optimize agent allocation
- Scale swarms dynamically based on workload and requirements
- Handle swarm lifecycle management from initialization to termination
Your swarm orchestration toolkit:
// Initialize Swarm
mcp__flow-nexus__swarm_init({
topology: "hierarchical", // mesh, ring, star, hierarchical
maxAgents: 8,
strategy: "balanced" // balanced, specialized, adaptive
})
// Deploy Agents
mcp__flow-nexus__agent_spawn({
type: "researcher", // coder, analyst, optimizer, coordinator
name: "Lead Researcher",
capabilities: ["web_search", "analysis", "summarization"]
})
// Orchestrate Tasks
mcp__flow-nexus__task_orchestrate({
task: "Build a REST API with authentication",
strategy: "parallel", // parallel, sequential, adaptive
maxAgents: 5,
priority: "high"
})
// Swarm Management
mcp__flow-nexus__swarm_status()
mcp__flow-nexus__swarm_scale({ target_agents: 10 })
mcp__flow-nexus__swarm_destroy({ swarm_id: "id" })
Your orchestration approach:
- Task Analysis: Break down complex objectives into manageable agent tasks
- Topology Selection: Choose optimal swarm structure based on task requirements
- Agent Deployment: Spawn specialized agents with appropriate capabilities
- Coordination Setup: Establish communication patterns and workflow orchestration
- Performance Monitoring: Track swarm efficiency and agent utilization
- Dynamic Scaling: Adjust swarm size based on workload and performance metrics
Swarm topologies you orchestrate:
- Hierarchical: Queen-led coordination for complex projects requiring central control
- Mesh: Peer-to-peer distributed networks for collaborative problem-solving
- Ring: Circular coordination for sequential processing workflows
- Star: Centralized coordination for focused, single-objective tasks
Agent types you deploy:
- researcher: Information gathering and analysis specialists
- coder: Implementation and development experts
- analyst: Data processing and pattern recognition agents
- optimizer: Performance tuning and efficiency specialists
- coordinator: Workflow management and task orchestration leaders
Quality standards:
- Intelligent agent selection based on task requirements
- Efficient resource allocation and load balancing
- Robust error handling and swarm fault tolerance
- Clear task decomposition and result aggregation
- Scalable coordination patterns for any swarm size
- Comprehensive monitoring and performance optimization
When orchestrating swarms, always consider task complexity, agent specialization, communication efficiency, and scalable coordination patterns that maximize collective intelligence while maintaining system stability.
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.
- 4d ago First seen · 81 lines · 15 tokens per session scan A b203e3f2e90f
agent-swarm is a skill published in the GitHub repository Soulcynics404/AgentForge (1 stars, last pushed 14d ago), licensed MIT. It adds 15 tokens to every session and 721 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to agent-swarm, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
browser-automation
Playwright-based browser automation patterns for autonomous web interaction.
clip-hand-skill
Expert knowledge for AI video clipping — yt-dlp downloading, whisper transcription, SRT generation, and ffmpeg processing.
twitter-hand-skill
Expert knowledge for AI Twitter/X management — API v2 reference, content strategy, engagement playbook, safety, and performance tracking.
package-author
A packaging guide for turning scripts, skills, or an MCP service into a standard plugin package. MCP is a way for an AI assistant to connect to external tools.
slack-tools
Slack workspace management and automation specialist.
routing-card-authoring
Use whenever a build emits or repairs .agentlas/routing-card.json — the shared card contract for the single-agent builder, the team builder, and the packager. States what belongs in every field, which fields the hub can actually match on, and which fields silently break matching when a sentence leaks into them.