cldcde: Skill for Claude Code

.claude/skills/swarm-orchestration/SKILL.md

Swarm Orchestration is a skill for Claude Code from aegntic/cldcde. It costs 46 tokens per session (1,053 once invoked), scanned A, a copy of Swarm Orchestration, MIT.

A system for coordinating multiple AI agents working on one task or workflow. It can assign work across mesh, hierarchical, or adaptive arrangements, with examples including coding, testing, and reviewing agents.

In plain words
What is it for?
Use it to initialize a group of agents, distribute tasks, run work in parallel, balance workloads, coordinate specialized roles, and build distributed AI workflows.
Why use it?
A single agent may be slow or poorly suited to every part of a complex task. Dividing work among specialized agents allows tasks to run in parallel and supports coordination when the workload changes.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is aegntic/cldcde's own configuration. It tells Claude Code how to work on cldcde itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything cldcde configures →

Reuse

Borrowing it

Nothing to install: this file belongs to aegntic/cldcde. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/aegntic/cldcde/main/.claude/skills/swarm-orchestration/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/aegntic/cldcde

Made for: Claude Code.

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 Swarm Orchestration

README.md
[![agentmods](https://agentmods.dev/badge/skills/aegntic/cldcde/swarm-orchestration/github.svg)](https://agentmods.dev/skills/aegntic/cldcde/swarm-orchestration)
Your own site
<a href="https://agentmods.dev/skills/aegntic/cldcde/swarm-orchestration"><img src="https://agentmods.dev/badge/skills/aegntic/cldcde/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.

agentmods 80×15 button for Swarm Orchestration

Your own site · 80×15
<a href="https://agentmods.dev/skills/aegntic/cldcde/swarm-orchestration"><img src="https://agentmods.dev/badge/skills/aegntic/cldcde/swarm-orchestration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 46 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,053 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 95% 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.00046 $0.01053
Opus 5 $0.00023 $0.00526
Sonnet 5 $0.00009 $0.00211
Haiku 4.5 $0.00005 $0.00105

Measured 9d ago against content hash 9f0bc14c44ec, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

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 9d 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

95% identical to Swarm Orchestration — 2 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.

.claude/skills/swarm-orchestration/SKILL.md · 180 lines

How it starts

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

Swarm Orchestration

What This Skill Does

Orchestrates multi-agent swarms using agentic-flow's advanced coordination system. Supports mesh, hierarchical, and adaptive topologies with automatic task distribution, load balancing, and fault tolerance.

Prerequisites

  • agentic-flow v1.5.11+
  • Node.js 18+
  • Understanding of distributed systems (helpful)

Quick Start

# Initialize swarm
npx agentic-flow hooks swarm-init --topology mesh --max-agents 5

# Spawn agents
npx agentic-flow hooks agent-spawn --type coder
npx agentic-flow hooks agent-spawn --type tester
npx agentic-flow hooks agent-spawn --type reviewer

# Orchestrate task
npx agentic-flow hooks task-orchestrate \
  --task "Build REST API with tests" \
  --mode parallel

Topology Patterns

1. Mesh (Peer-to-Peer)

// Equal peers, distributed decision-making
await swarm.init({
  topology: 'mesh',
  agents: ['coder', 'tester', 'reviewer'],
  communication: 'broadcast'
});

2. Hierarchical (Queen-Worker)

// Centralized coordination, specialized workers
await swarm.init({
  topology: 'hierarchical',
  queen: 'architect',
  workers: ['backend-dev', 'frontend-dev', 'db-designer']
});

3. Adaptive (Dynamic)

// Automatically switches topology based on task
await swarm.init({
  topology: 'adaptive',
  optimization: 'task-complexity'
});

Task Orchestration

Parallel Execution

// Execute tasks concurrently
const results = await swarm.execute({
  tasks: [
    { agent: 'coder', task: 'Implement API endpoints' },
    { agent: 'frontend', task: 'Build UI components' },
    { agent: 'tester', task: 'Write test suite' }
  ],
  mode: 'parallel',
  timeout: 300000 // 5 minutes
});

Pipeline Execution

// Sequential pipeline with dependencies
await swarm.pipeline([
  { stage: 'design', agent: 'architect' },
  { stage: 'implement', agent: 'coder', after: 'design' },
  { stage: 'test', agent: 'tester', after: 'implement' },
  { stage: 'review', agent: 'reviewer', after: 'test' }
]);

Read the full file on GitHub · 180 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. 9d ago First seen · 180 lines · 46 tokens per session scan A 9f0bc14c44ec

Subscribe to this mod's changes

Swarm Orchestration is a skill published in the GitHub repository aegntic/cldcde (11 stars, last pushed 13d ago), licensed MIT. It adds 46 tokens to every session and 1,053 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to Swarm Orchestration, differing in 2 lines, and is treated as a copy.

Related

Other skills, from other repositories

hono-core

Hono ultrafast web framework fundamentals - routing, context, handlers, and response patterns for multi-runtime deployment.

bobmatnyc/claude-mpm-skills · 26 tokens

tauri-django-react

Agents should invoke this skill for Tauri + Django + React desktop apps, especially backend lifecycle, CORS/auth, frontend integration, mandatory light/dark theming, German/English i18n, build packaging, dual desktop/web deployment, Rust commands, and platform-specific gotchas.

Firstp1ck/pi-coding-agent-forge · 63 tokens

project-readme

Use when creating, updating, reviewing, restructuring, or harmonizing a repository's project README from verified local evidence for user-oriented or developer/library-oriented readers.

Firstp1ck/pi-coding-agent-forge · 35 tokens

subagent-governance

Delegation admissibility governance for a parent orchestrator. Use when deciding whether to launch, sequence, replace, or accept one or more delegated child runs while preserving role fit, plan-backed worker contracts, one-writer isolation, bounded retry safety, and reviewer finding disposition. Covers admissibility…

Firstp1ck/pi-coding-agent-forge · 74 tokens

html-report

Creates polished self-contained HTML explanation reports for complex, multi-step topics using overview tables, evidence cards, adaptive graphs or diagrams, meaningful SVG/media, and accessible tabs for long pages. Use when the user requests a browser-readable diagnostic report, technical guide, decision analysis…

Firstp1ck/pi-coding-agent-forge · 67 tokens

repo-explorer

Agents should invoke this skill before modifying unfamiliar codebases, answering where/how something is implemented, tracing dependencies, mapping repo structure, or planning changes. Explores a repository and returns a strict JSON handoff with key files, symbols, risks, and evidence.

Firstp1ck/pi-coding-agent-forge · 55 tokens