performance-bottlenecks

performance-bottlenecks is a command for Claude Code from spencermarx/open-code-review. It costs 0 tokens per session (310 once invoked), scanned A, a copy of performance-bottlenecks, Apache-2.0.

An automated check for slow or inefficient coding-agent work. It looks at task timing, agent use, resource limits, and repeated operations.

In plain words
What is it for?
Use it to find tasks that run for a long time, use too many operations, or assign complex work to too few agents, then review suggested improvements.
Why use it?
It helps reveal why work is taking too long, such as unnecessary sequential steps, repeated file access, or poorly divided tasks.

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/spencermarx/open-code-review/performance-bottlenecks
Clone the repo
git clone --depth 1 https://github.com/spencermarx/open-code-review

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for performance-bottlenecks

README.md
[![agentmods](https://agentmods.dev/badge/commands/spencermarx/open-code-review/performance-bottlenecks.svg)](https://agentmods.dev/commands/spencermarx/open-code-review/performance-bottlenecks)
Your own site
<a href="https://agentmods.dev/commands/spencermarx/open-code-review/performance-bottlenecks"><img src="https://agentmods.dev/badge/commands/spencermarx/open-code-review/performance-bottlenecks.svg" alt="Measured on agentmods" height="20"></a>
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 310 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod 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.00310
Opus 5 $0.00000 $0.00155
Sonnet 5 $0.00000 $0.00062
Haiku 4.5 $0.00000 $0.00031

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

Security

Grade A, and why

performance-bottlenecks 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 4d 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

This is a copy

100% identical to performance-bottlenecks — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/commands/analysis/performance-bottlenecks.md · 59 lines

What it actually says

Performance Bottleneck Analysis

Purpose

Identify and resolve performance bottlenecks in your development workflow.

Automated Analysis

1. Real-time Detection

The post-task hook automatically analyzes:

  • Execution time vs. complexity
  • Agent utilization rates
  • Resource constraints
  • Operation patterns

2. Common Bottlenecks

Time Bottlenecks:

  • Tasks taking > 5 minutes
  • Sequential operations that could parallelize
  • Redundant file operations

Coordination Bottlenecks:

  • Single agent for complex tasks
  • Unbalanced agent workloads
  • Poor topology selection

Resource Bottlenecks:

  • High operation count (> 100)
  • Memory constraints
  • I/O limitations

3. Improvement Suggestions

Tool: mcp__claude-flow__task_results
Parameters: {"taskId": "task-123", "format": "detailed"}

Result includes:
{
  "bottlenecks": [
    {
      "type": "coordination",
      "severity": "high",
      "description": "Single agent used for complex task",
      "recommendation": "Spawn specialized agents for parallel work"
    }
  ],
  "improvements": [
    {
      "area": "execution_time",
      "suggestion": "Use parallel task execution",
      "expectedImprovement": "30-50% time reduction"
    }
  ]
}

Continuous Optimization

The system learns from each task to prevent future bottlenecks!

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. 4d ago First seen · 59 lines · 0 tokens per session scan A 61e9e3a163b2

Subscribe to this mod's changes

performance-bottlenecks is a command published in the GitHub repository spencermarx/open-code-review (352 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 310 tokens. A static security scan graded it A with 0 findings. It is 100% identical to performance-bottlenecks, differing in 0 lines, and is treated as a copy.