What is SwarmOps

SwarmOps is a hardened, optimized fork of ruflo / claude-flow for global ~/.claude/ installs. It ships agents, skills, slash-commands, and MCP servers — the standard Claude Code plugin surface — and discovers + routes to your existing ~/.claude/{agents,skills,commands,plugins}/ registry on startup.

Why Backend & Architecture

Sits next to maestro-orchestrate (line 130) — both are multi-agent orchestration systems for Claude Code. SwarmOps' angle is global-install correctness plus measurable performance and security wins.

Three strongest concrete claims

1. 46× faster memory_search (74.2 ms → 1.6 ms warm). In-process SQLite connection pool eliminates per-call DB open. Reproducible via npm run bench:memory in the repo.
2. Real semantic memory via local Ollama + mxbai-embed-large (1024-dim) replacing the bundled all-MiniLM-L6-v2 (384-dim). +33% recall on paraphrased queries. swarm_init({task, strategy: "specialized"}) auto-picks user-installed agents based on task semantics.
3. AIDefence wired into hooks (UserPromptSubmit + PreToolUse:WebFetch) which upstream ships but never invokes. Plus 14 npm-audit CVEs patched (0 highs remaining), tightened permission allowlist, file perms hardened to 0600.

Submission compliance

• Entry placed in Backend & Architecture next to maestro-orchestrate (the closest existing entry by use case).
• One entry, one section.
• No edits to other sections, contribution guidelines, or unrelated content.
• Repo is MIT licensed, same as upstream and consistent with this list's plugins.
• Externally-hosted entry (same pattern as maestro-orchestrate, aws-cost-saver, security-sweep, CCHub, backlog, etc.).

Thank you for maintaining this list.