optimizer

A command for measuring and improving an application's performance. It examines areas such as execution speed, memory use, network activity, database queries, and bundle size.

In plain words
What is it for?
Use it to profile an application, identify bottlenecks, improve algorithms or database queries, reduce resource use, and check whether optimizations helped.
Why use it?
It replaces guesswork with a sequence of measuring current performance, finding slow points, making changes, and checking their effect.

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/natea/fitfinder/optimizer
Clone the repo
git clone --depth 1 https://github.com/natea/fitfinder

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 271 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.00271
Opus 5 $0.00000 $0.00135
Sonnet 5 $0.00000 $0.00054
Haiku 4.5 $0.00000 $0.00027

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

Security

Grade A, and why

optimizer 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/commands/sparc/optimizer.md · 55 lines

What it actually says

SPARC Optimizer Mode

Purpose

Performance optimization with systematic analysis and improvements.

Activation

Option 1: Using MCP Tools (Preferred in Claude Code)

mcp__claude-flow__sparc_mode {
  mode: "optimizer",
  task_description: "optimize application performance",
  options: {
    profile: true,
    benchmark: true
  }
}

Option 2: Using NPX CLI (Fallback when MCP not available)

# Use when running from terminal or MCP tools unavailable
npx claude-flow sparc run optimizer "optimize application performance"

# For alpha features
npx claude-flow@alpha sparc run optimizer "optimize application performance"

Option 3: Local Installation

# If claude-flow is installed locally
./claude-flow sparc run optimizer "optimize application performance"

Core Capabilities

  • Performance profiling
  • Code optimization
  • Resource optimization
  • Algorithm improvement
  • Scalability enhancement

Optimization Areas

  • Execution speed
  • Memory usage
  • Network efficiency
  • Database queries
  • Bundle size

Systematic Approach

  1. Baseline measurement
  2. Bottleneck identification
  3. Optimization implementation
  4. Impact verification
  5. Continuous monitoring
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 · 55 lines · 0 tokens per session scan A 5f5c2ab6e0f7

Subscribe to this mod's changes

optimizer is a command published in the GitHub repository natea/fitfinder (4 stars, last pushed 10mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 271 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.