performance-analysis

A tool for measuring and diagnosing the performance of Claude Flow swarms, which are groups of coordinated software agents. It looks for slowdowns in communication, processing, memory use, and networking.

In plain words
What is it for?
Use it to detect bottlenecks, profile current or past operations, generate performance reports, and receive optimization suggestions.
Why use it?
It helps show where a swarm is spending time or resources, so optimization work can target a specific bottleneck.

Skill for Claude CodeCodex

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 skills/aegntic/cldcde/performance-analysis
Any agent
npx skills add aegntic/cldcde --skill performance-analysis
Clone the repo
git clone --depth 1 https://github.com/aegntic/cldcde

Made for: Claude Code, Codex.

Per session 20 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,517 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.00020 $0.03517
Opus 5 $0.00010 $0.01758
Sonnet 5 $0.00004 $0.00703
Haiku 4.5 $0.00002 $0.00352

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

Security

Grade A, and why

performance-analysis scanned grade A with 1 finding 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 3d 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.

Runs shell commandslowCapability

Expected in a hook, worth knowing in a rule or an instructions file.

const { exec } = require('child_process');
.claude/skills/performance-analysis/SKILL.md · 564 lines

How it starts

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

Performance Analysis Skill

Comprehensive performance analysis suite for identifying bottlenecks, profiling swarm operations, generating detailed reports, and providing actionable optimization recommendations.

Overview

This skill consolidates all performance analysis capabilities:

  • Bottleneck Detection: Identify performance bottlenecks across communication, processing, memory, and network
  • Performance Profiling: Real-time monitoring and historical analysis of swarm operations
  • Report Generation: Create comprehensive performance reports in multiple formats
  • Optimization Recommendations: AI-powered suggestions for improving performance

Quick Start

Basic Bottleneck Detection

npx claude-flow bottleneck detect

Generate Performance Report

npx claude-flow analysis performance-report --format html --include-metrics

Analyze and Auto-Fix

npx claude-flow bottleneck detect --fix --threshold 15

Core Capabilities

1. Bottleneck Detection

Command Syntax
npx claude-flow bottleneck detect [options]
Options
  • --swarm-id, -s <id> - Analyze specific swarm (default: current)
  • --time-range, -t <range> - Analysis period: 1h, 24h, 7d, all (default: 1h)
  • --threshold <percent> - Bottleneck threshold percentage (default: 20)
  • --export, -e <file> - Export analysis to file
  • --fix - Apply automatic optimizations
Usage Examples
# Basic detection for current swarm
npx claude-flow bottleneck detect

# Analyze specific swarm over 24 hours
npx claude-flow bottleneck detect --swarm-id swarm-123 -t 24h

# Export detailed analysis
npx claude-flow bottleneck detect -t 24h -e bottlenecks.json

# Auto-fix detected issues
npx claude-flow bottleneck detect --fix --threshold 15

# Low threshold for sensitive detection
npx claude-flow bottleneck detect --threshold 10 --export critical-issues.json
Metrics Analyzed

Communication Bottlenecks:

  • Message queue delays
  • Agent response times
  • Coordination overhead
  • Memory access patterns
  • Inter-agent communication latency

Read the full file on GitHub · 564 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. 3d ago First seen · 564 lines · 20 tokens per session scan A 438bdb02203c

Subscribe to this mod's changes

performance-analysis is a skill published in the GitHub repository aegntic/cldcde (11 stars, last pushed 6d ago), licensed MIT. It adds 20 tokens to every session and 3,517 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.