distributed-analysis

A multi-agent review method for distributed systems, which are applications whose parts run across multiple computers or services.

In plain words
What is it for?
Use it to review system architecture, data flows, dependencies, performance, recovery behaviour, and likely failure modes.
Why use it?
It helps examine complex systems from several angles, including bottlenecks, scaling limits, data consistency, security, and failures.

Command for Claude Code

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 commands/thelobbi/claude/distributed-analysis
Clone the repo
git clone --depth 1 https://github.com/TheLobbi/claude

Made for: Claude Code.

Per session 0 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,791 The whole file, excluding the scripts and references it only reads on demand.
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.00000 $0.01791
Opus 5 $0.00000 $0.00896
Sonnet 5 $0.00000 $0.00358
Haiku 4.5 $0.00000 $0.00179

Measured yesterday against content hash 9adc55330b15, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

distributed-analysis 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/distributed-analysis.md · 223 lines

How it starts

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

Distributed Systems Analysis

Comprehensive analysis of distributed systems using 10+ specialized agents with shared blackboard pattern for collaborative problem-solving and emergent insights.

Purpose

Analyze complex distributed systems to identify architectural issues, performance bottlenecks, scalability limitations, data consistency problems, and failure modes using collaborative multi-agent intelligence.

Multi-Agent Coordination Strategy

Uses blackboard pattern where specialized agents contribute domain-specific knowledge to a shared workspace, enabling emergent solutions through collaborative analysis.

Blackboard Architecture

``` ┌─────────────────────────────────────────────┐ │ Shared Knowledge Blackboard │ │ ┌─────────────────────────────────────┐ │ │ │ System Topology & Dependencies │ │ │ │ Performance Metrics & Bottlenecks │ │ │ │ Failure Modes & Recovery Patterns │ │ │ │ Data Flow & Consistency Issues │ │ │ │ Security Vulnerabilities │ │ │ │ Scalability Constraints │ │ │ └─────────────────────────────────────┘ │ └─────────────────────────────────────────────┘ ↑ ↑ ↑ Agent A Agent B Agent C ```

Execution Flow

Phase 1: Discovery & Mapping (0-15 mins)

  1. system-mapper - Map distributed architecture topology
  2. dependency-analyzer - Identify service dependencies and coupling
  3. data-flow-tracer - Trace data flows across services
  4. api-cartographer - Catalog all API endpoints and contracts

Phase 2: Performance Analysis (15-30 mins)

  1. performance-profiler - Analyze latency, throughput, resource usage
  2. bottleneck-detective - Identify performance bottlenecks
  3. scaling-analyst - Assess scalability limits and patterns
  4. resource-optimizer - Optimize resource allocation

Phase 3: Reliability & Resilience (30-45 mins)

  1. failure-mode-analyst - Identify failure scenarios
  2. circuit-breaker-auditor - Validate fault tolerance patterns
  3. recovery-strategist - Assess recovery and retry mechanisms
  4. chaos-simulator - Simulate failure scenarios

Read the full file on GitHub · 223 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 · 223 lines · 0 tokens per session scan A 9adc55330b15

Subscribe to this mod's changes

distributed-analysis is a command published in the GitHub repository TheLobbi/claude (21 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,791 tokens. 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.