V3 Swarm Coordination

V3 Swarm Coordination is a skill for Claude Code from proffesor-for-testing/agentic-qe. It costs 40 tokens per session (2,941 once invoked), scanned A, a copy of V3 Swarm Coordination, MIT.

A coordination plan for having 15 specialised agents work together on a version 3 implementation.

In plain words
What is it for?
It is for coordinating large multi-part implementation projects with separate agents and defined work areas.
Why use it?
It organizes parallel work across security, core features, and integrations while keeping dependencies and milestones aligned.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: installed under .agents/ (shared by several agents).

Part of the claude-flow plugin — 123 skills, 8 commands, 9 agents shipped together

Good fit It is for coordinating large multi-part implementation projects with separate agents and defined work areas.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/proffesor-for-testing/agentic-qe/v3-swarm-coordination
Install

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.

Any agent
npx skills add proffesor-for-testing/agentic-qe --skill v3-swarm-coordination
Clone the repo
git clone --depth 1 https://github.com/proffesor-for-testing/agentic-qe

Made for: Claude Code.

Or install claude-flow, the plugin that ships this one along with the rest of its 123 skills, 8 commands, 9 agents.

Wrote 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.

agentmods badge for V3 Swarm Coordination

README.md
[![agentmods](https://agentmods.dev/badge/skills/proffesor-for-testing/agentic-qe/v3-swarm-coordination/github.svg)](https://agentmods.dev/skills/proffesor-for-testing/agentic-qe/v3-swarm-coordination)
Your own site
<a href="https://agentmods.dev/skills/proffesor-for-testing/agentic-qe/v3-swarm-coordination"><img src="https://agentmods.dev/badge/skills/proffesor-for-testing/agentic-qe/v3-swarm-coordination/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.

agentmods 80×15 button for V3 Swarm Coordination

Your own site · 80×15
<a href="https://agentmods.dev/skills/proffesor-for-testing/agentic-qe/v3-swarm-coordination"><img src="https://agentmods.dev/badge/skills/proffesor-for-testing/agentic-qe/v3-swarm-coordination.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,941 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00040 $0.02941
Opus 5.5 $0.00016 $0.01176
Sonnet 5.5 $0.00008 $0.00588
Haiku 4.5 $0.00004 $0.00294

Measured 1mo ago against content hash 5edfd5e1e675, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

V3 Swarm Coordination 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.

Origin

This is a copy

100% identical to V3 Swarm Coordination — 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.

.agents/skills/ruflo/.agents/skills/v3-swarm-coordination/SKILL.md · 340 lines

How it starts

The opening of the file, as written. The whole thing — 340 lines — stays where its author put it; the contents beside it link to each section on GitHub.

V3 Swarm Coordination

What This Skill Does

Orchestrates the complete 15-agent hierarchical mesh swarm for claude-flow v3 implementation, coordinating parallel execution across domains while maintaining dependencies and timeline adherence.

Quick Start

# Initialize 15-agent v3 swarm
Task("Swarm initialization", "Initialize hierarchical mesh for v3 implementation", "v3-queen-coordinator")

# Security domain (Phase 1 - Critical priority)
Task("Security architecture", "Design v3 threat model and security boundaries", "v3-security-architect")
Task("CVE remediation", "Fix CVE-1, CVE-2, CVE-3 vulnerabilities", "security-auditor")
Task("Security testing", "Implement TDD security framework", "test-architect")

# Core domain (Phase 2 - Parallel execution)
Task("Memory unification", "Implement AgentDB 150x improvement", "v3-memory-specialist")
Task("Integration architecture", "Deep agentic-flow@alpha integration", "v3-integration-architect")
Task("Performance validation", "Validate 2.49x-7.47x targets", "v3-performance-engineer")

15-Agent Swarm Architecture

Hierarchical Mesh Topology

                    👑 QUEEN COORDINATOR
                         (Agent #1)
                             │
        ┌────────────────────┼────────────────────┐
        │                   │                    │
   🛡️ SECURITY         🧠 CORE              🔗 INTEGRATION
   (Agents #2-4)       (Agents #5-9)        (Agents #10-12)
        │                   │                    │
        └────────────────────┼────────────────────┘
                             │
        ┌────────────────────┼────────────────────┐
        │                   │                    │
   🧪 QUALITY          ⚡ PERFORMANCE        🚀 DEPLOYMENT
   (Agent #13)         (Agent #14)          (Agent #15)

Agent Roster

ID Agent Domain Phase Responsibility
1 Queen Coordinator Orchestration All GitHub issues, dependencies, timeline
2 Security Architect Security Foundation Threat modeling, CVE planning
3 Security Implementer Security Foundation CVE fixes, secure patterns
4 Security Tester Security Foundation TDD security testing
5 Core Architect Core Systems DDD architecture, coordination
6 Core Implementer Core Systems Core module implementation
7 Memory Specialist Core Systems AgentDB unification
8 Swarm Specialist Core Systems Unified coordination engine
9 MCP Specialist Core Systems MCP server optimization
10 Integration Architect Integration Integration agentic-flow@alpha deep integration
11 CLI/Hooks Developer Integration Integration CLI modernization
12 Neural/Learning Dev Integration Integration SONA integration
13 TDD Test Engineer Quality All London School TDD
14 Performance Engineer Performance Optimization Benchmarking validation
15 Release Engineer Deployment Release CI/CD and v3.0.0 release

Read the full file on GitHub · 340 lines

Changes

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.

  1. 1mo ago First seen · 340 lines · 40 tokens per session scan A 5edfd5e1e675

Subscribe to this mod's changes

V3 Swarm Coordination is a skill published in the GitHub repository proffesor-for-testing/agentic-qe (515 stars, last pushed yesterday), licensed MIT. It adds 40 tokens to every session and 2,941 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to V3 Swarm Coordination, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…

vercel/next.js · 123 tokens