Borrowing it
Nothing to install: this file belongs to proffesor-for-testing/agentic-qe. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/proffesor-for-testing/agentic-qe/main/.agents/skills/ruflo/.agents/skills/swarm-orchestration/SKILL.mdgit clone --depth 1 https://github.com/proffesor-for-testing/agentic-qeWrote 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/proffesor-for-testing/agentic-qe/swarm-orchestration)<a href="https://agentmods.dev/skills/proffesor-for-testing/agentic-qe/swarm-orchestration"><img src="https://agentmods.dev/badge/skills/proffesor-for-testing/agentic-qe/swarm-orchestration/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/skills/proffesor-for-testing/agentic-qe/swarm-orchestration"><img src="https://agentmods.dev/badge/skills/proffesor-for-testing/agentic-qe/swarm-orchestration.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.00096 | $0.00722 |
| Opus 5 | $0.00048 | $0.00361 |
| Sonnet 5 | $0.00019 | $0.00144 |
| Haiku 4.5 | $0.00010 | $0.00072 |
Grade A, and why
swarm-orchestration 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 5d 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 swarm-orchestration — 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Swarm Orchestration Skill
Purpose
Multi-agent swarm coordination for complex tasks. Uses hierarchical topology with specialized agents to break down and execute complex work across multiple files and modules.
When to Trigger
- 3+ files need changes
- new feature implementation
- cross-module refactoring
- API changes with tests
- security-related changes
- performance optimization across codebase
- database schema changes
When to Skip
- single file edits
- simple bug fixes (1-2 lines)
- documentation updates
- configuration changes
- quick exploration
Commands
Initialize Swarm
Start a new swarm with hierarchical topology (anti-drift)
npx @claude-flow/cli swarm init --topology hierarchical --max-agents 8 --strategy specialized
Example:
npx @claude-flow/cli swarm init --topology hierarchical --max-agents 6 --strategy specialized
Route Task
Route a task to the appropriate agents based on task type
npx @claude-flow/cli hooks route --task "[task description]"
Example:
npx @claude-flow/cli hooks route --task "implement OAuth2 authentication flow"
Spawn Agent
Spawn a specific agent type
npx @claude-flow/cli agent spawn --type [type] --name [name]
Example:
npx @claude-flow/cli agent spawn --type coder --name impl-auth
Monitor Status
Check the current swarm status
npx @claude-flow/cli swarm status --verbose
Orchestrate Task
Orchestrate a task across multiple agents
npx @claude-flow/cli task orchestrate --task "[task]" --strategy adaptive
Example:
npx @claude-flow/cli task orchestrate --task "refactor auth module" --strategy parallel --max-agents 4
List Agents
List all active agents
npx @claude-flow/cli agent list --filter active
Scripts
| Script | Path | Description |
|---|---|---|
swarm-start |
.agents/scripts/swarm-start.sh |
Initialize swarm with default settings |
swarm-monitor |
.agents/scripts/swarm-monitor.sh |
Real-time swarm monitoring dashboard |
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.
- 5d ago First seen · 115 lines · 96 tokens per session scan A 6a9ee0ac32c2
swarm-orchestration is a skill published in the GitHub repository proffesor-for-testing/agentic-qe (475 stars, last pushed yesterday), licensed MIT. It adds 96 tokens to every session and 722 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to swarm-orchestration, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
style-refresh
Refresh CocoStyle conventions from project evidence.
style-show
Show CocoStyle conventions for the current project.
stitch
Clean, high-contrast enterprise design for data-driven workflows with intuitive drag-and-drop patterns and structured layouts.
agentos
Use before and during AgentOS code, UX, integration, or release work so changes stay OpenClaw-first, observable, and release-safe.
project
GitHub Issues as PLAN.md replacement — agents read/update them. Auto-invoke on issue-linked branches. Triggers "what's the plan", "project status", "sync with github", "close the issue".