swarmcode CLAUDE.md

Repository instructions for SwarmCode, which lets Claude Code sessions communicate across machines and workspaces through Redis, a message-storage and messaging system.

In plain words
What is it for?
Use them when modifying cross-workspace messaging, inbox notifications, listeners, initialization, or the command-line entry point.
Why use it?
They explain the project’s components, message channels, workspace identifiers, and required Redis settings so changes fit the existing design.

Instructions file

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.

agentmods
npx agentmods add instructions/spranab/swarmcode/claude-md
Clone the repo
git clone --depth 1 https://github.com/spranab/swarmcode
Per session 254 This file is loaded in full into every session.
When invoked 254 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.00254 $0.00254
Opus 5 $0.00127 $0.00127
Sonnet 5 $0.00051 $0.00051
Haiku 4.5 $0.00025 $0.00025

Measured 2d ago against content hash 74f53a772920, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

swarmcode CLAUDE.md 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 2d 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.

CLAUDE.md · 27 lines

What it actually says

SwarmCode

Real-time communication between Claude Code instances across machines and workspaces.

Architecture

  • src/channel.js - MCP server with swarm_send/receive/status/register tools + Redis pub/sub
  • src/listener.js - One-shot Redis listener for background task notifications
  • src/check-inbox-http.js - Hook script for inbox check on each prompt
  • src/init.js - CLI to initialize any workspace in one command
  • src/server.js - CLI entry point (routes to init/channel/listen)

Key Design

  • Redis pub/sub for real-time cross-machine messaging
  • Per-workspace channels: swarmcode:ws:<workspace-id>
  • Broadcast channel: swarmcode:ws:broadcast
  • Background task pattern: listener exits on message → task-notification → auto-process
  • Messages stored in per-workspace inbox lists with 24h TTL

Running

npx swarmcode init <workspace-id> --redis redis://host:port

Environment

  • SWARMCODE_REDIS_URL - Redis URL (default: redis://localhost:6379)
  • SWARMCODE_WORKSPACE_ID - Workspace identifier
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. 2d ago First seen · 27 lines · 254 tokens per session scan A 74f53a772920

Subscribe to this mod's changes

swarmcode CLAUDE.md is an instructions file published in the GitHub repository spranab/swarmcode (8 stars, last pushed 14d ago), licensed MIT. It adds 254 tokens to every session, about $0.0013 per session on Opus 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-08-31.