What is bottleneck-detect?

A bottleneck detector for swarm operations that examines delays, agent response times, task completion, parallel work, memory access, and resource contention.

Use it to inspect the current or a specific swarm over a chosen time range, set the percentage threshold for reporting issues, export findings, or run automatic fixes.

It helps locate parts of a multi-agent workflow that slow the whole swarm down and can optionally apply automatic optimizations.

bottleneck-detect — Command by ruvnet

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/ruvnet/ruview/bottleneck-detect

Clone the repo

git clone --depth 1 https://github.com/ruvnet/RuView

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 874 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.

Model	Per session	Once invoked
Fable 5	$0.00000	$0.00874
Opus 5	$0.00000	$0.00437
Sonnet 5	$0.00000	$0.00175
Haiku 4.5	$0.00000	$0.00087

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

Security

Grade A, and why

bottleneck-detect 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 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.

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.

Origin

Copies of this mod

8 near-identical copies found in the catalogue:

bottleneck-detect — 100% identical, 0 lines differ
bottleneck-detect — 100% identical, 17 lines differ
bottleneck-detect — 100% identical, 0 lines differ
bottleneck-detect — 100% identical, 0 lines differ
bottleneck-detect — 100% identical, 0 lines differ
bottleneck-detect — 100% identical, 0 lines differ
bottleneck-detect — 100% identical, 0 lines differ
bottleneck-detect — 100% identical, 0 lines differ

.claude/commands/analysis/bottleneck-detect.md · 163 lines

How it starts

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