workflows:swarm

workflows:swarm is a command for Claude Code from Workflowsio/company-os-starter-kit. It costs 35 tokens per session (1,231 once invoked), scanned A, original, MIT.

An autonomous workflow that creates a plan, divides the work among parallel agents, executes it, and reviews the result. Parallel agents are separate automated workers handling different tasks at the same time.

In plain words
What is it for?
Use it to carry a project from planning through implementation and final review, when the required supporting commands are available.
Why use it?
It reduces the need to coordinate each work step manually, while keeping planning and review in the same workflow.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: reads .claude/ paths.

Good fit Use it to carry a project from planning through implementation and final review, when the required supporting commands are available.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/workflowsio/company-os-starter-kit/swarm
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.

Clone the repo
git clone --depth 1 https://github.com/Workflowsio/company-os-starter-kit

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 workflows:swarm

README.md
[![agentmods](https://agentmods.dev/badge/commands/workflowsio/company-os-starter-kit/swarm/github.svg)](https://agentmods.dev/commands/workflowsio/company-os-starter-kit/swarm)
Your own site
<a href="https://agentmods.dev/commands/workflowsio/company-os-starter-kit/swarm"><img src="https://agentmods.dev/badge/commands/workflowsio/company-os-starter-kit/swarm/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 workflows:swarm

Your own site · 80×15
<a href="https://agentmods.dev/commands/workflowsio/company-os-starter-kit/swarm"><img src="https://agentmods.dev/badge/commands/workflowsio/company-os-starter-kit/swarm.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 35 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,231 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 original No closer match found 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.00035 $0.01231
Opus 5.5 $0.00014 $0.00492
Sonnet 5.5 $0.00007 $0.00246
Haiku 4.5 $0.00003 $0.00123

Measured yesterday against content hash b67073928837, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

workflows: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 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.

.claude/commands/workflows/swarm.md · 154 lines

How it starts

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

Swarm-enabled autonomous workflow. Run these steps in order, parallelizing where indicated. Do not stop between steps - complete every step through to the end.

Steps 2, 5, 6 and 7 call /deepen-plan, /test-browser, /resolve_todo_parallel and /feature-video, which this kit does not ship. If a command is not installed, skip that step and say so in the run summary rather than stopping.

Dynamic Context

Current branch: !git branch --show-current Recent commits: !git log --oneline -5

Phase 1: Plan (Sequential)

  1. /workflows:plan $ARGUMENTS
  2. /deepen-plan

Phase 2: Execute (Swarm)

After the plan is written and deepened, execute it using parallel agent swarm orchestration.

Step 1: Create the Task Board

Read the plan file. Break it into discrete, parallelizable tasks. Create ALL tasks upfront using TaskCreate, then wire dependencies with TaskUpdate.

TaskCreate({
  subject: "Task 1: [specific deliverable]",
  description: "[what needs to be done, files to create/modify, references to follow]",
  activeForm: "Building [deliverable]..."
})
TaskCreate({
  subject: "Task 2: [specific deliverable]",
  description: "[what needs to be done]",
  activeForm: "Drafting [deliverable]..."
})
... (create every task from the plan)

Then set up dependencies:

TaskUpdate({ taskId: "3", addBlockedBy: ["1"] })  // Task 3 needs Task 1 done first
TaskUpdate({ taskId: "5", addBlockedBy: ["2", "4"] })  // Task 5 needs 2 and 4

Rules:

  • Aim for 8-15 tasks. Each = a concrete deliverable (file, component, report, draft, config)
  • Group tiny items together. Split large items apart.
  • Independent tasks have NO blockedBy (can run in parallel immediately)
  • Sequential tasks use addBlockedBy to enforce ordering
  • The user sees real-time progress as dots change: pending -> in_progress -> completed

Step 2: Launch the Swarm

Launch 5-6 parallel Agent workers. Each agent gets a color for visual differentiation. Use isolation: "worktree" when agents touch different files to avoid conflicts.

Read the full file on GitHub · 154 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. yesterday First seen · 154 lines · 35 tokens per session scan A b67073928837

Subscribe to this mod's changes

workflows:swarm is a command published in the GitHub repository Workflowsio/company-os-starter-kit (104 stars, last pushed yesterday), licensed MIT. It adds 35 tokens to every session and 1,231 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-11-09.

Related

workflows:swarm compared with commands from other repositories

workflows:swarm next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
workflows:swarmWorkflowsio/company-os-starter-kitCommand104yesterdayMITA35Claude Code
_registry-protocolChappygo-OS/Atomic-SpecCommand104d agoMITA0Claude Code
mach12:gh-pr-readLeanAndMean/scramjetCommand88d agoApache-2.0A25Claude Code
scramjet:troubleshootLeanAndMean/scramjetCommand88d agoApache-2.0A9Claude Code
gaai-auditdigipulse-engineering/GAAI-frameworkCommand1638d agononeA10Claude Code
cold-startkunalsuri/ai-fication-kitCommand326d agoApache-2.0A28GitHub Copilot
healthalexgreensh/token-optimizerCommand2.9kyesterdaynoneC28Claude Code