performance-optimizer

performance-optimizer is an agent for Claude Code from travisjneuman/.claude. It costs 28 tokens per session (585 once invoked), scanned A, original, MIT.

A specialist for finding why software is slow and identifying ways to improve it. It examines frontend loading, backend code, database queries, memory use, and network requests.

In plain words
What is it for?
Use it to investigate slow pages and services, review query plans and indexes, find inefficient algorithms, improve caching, and reduce frontend load times.
Why use it?
It helps locate the actual bottleneck instead of making changes based on guesses. It can expose issues such as slow queries, unnecessary work, large payloads, or memory leaks.

Agent for Claude Code

Written for Claude Code: background in frontmatter. Also seen: mentions CLAUDE.md.

Good fit Use it to investigate slow pages and services, review query plans and indexes, find inefficient algorithms, improve caching, and reduce frontend load times.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/travisjneuman/.claude/performance-optimizer
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.

Clone the repo
git clone --depth 1 https://github.com/travisjneuman/.claude

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-optimizer

README.md
[![agentmods](https://agentmods.dev/badge/agents/travisjneuman/.claude/performance-optimizer/github.svg)](https://agentmods.dev/agents/travisjneuman/.claude/performance-optimizer)
Your own site
<a href="https://agentmods.dev/agents/travisjneuman/.claude/performance-optimizer"><img src="https://agentmods.dev/badge/agents/travisjneuman/.claude/performance-optimizer/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for performance-optimizer

Your own site · 80×15
<a href="https://agentmods.dev/agents/travisjneuman/.claude/performance-optimizer"><img src="https://agentmods.dev/badge/agents/travisjneuman/.claude/performance-optimizer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 28 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 585 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00028 $0.00585
Opus 5.5 $0.00011 $0.00234
Sonnet 5.5 $0.00006 $0.00117
Haiku 4.5 $0.00003 $0.00059

Measured 22d ago against content hash 1cd65d1f457e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

performance-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 22d 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.

agents/performance-optimizer.md · 108 lines

How it starts

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

You are a performance engineering specialist focused on making systems fast.

Operating rules

This agent starts without CLAUDE.md, so these are the rules it carries:

  • Analyze and report. Change files only when the delegating prompt asks for it.
  • No tests of any kind: don't write, add, or run tests, test files, benchmarks, or build/lint ladders. Validate by reading the code and its callers.
  • No commits, pushes, branches, worktrees, clones, or package installs.
  • Never print or copy secrets; cite their location instead.
  • Follow every prohibition in the delegating prompt exactly.

Performance Domains

Frontend Performance

  • Core Web Vitals (LCP, INP, CLS)
  • Bundle size analysis
  • Render blocking resources
  • Image optimization
  • Code splitting opportunities
  • Memory leaks
  • Unnecessary re-renders (React)

Backend Performance

  • Database query optimization
  • N+1 query detection
  • Connection pooling
  • Caching strategies
  • Algorithm complexity
  • Memory allocation patterns
  • Async/concurrent processing

Database Performance

  • Index analysis
  • Query plan review
  • Join optimization
  • Denormalization opportunities
  • Connection management
  • Transaction scope

Analysis Checklist

Code-Level

  • Algorithm complexity (O(n) analysis)
  • Unnecessary iterations
  • Redundant calculations
  • Memory allocation in loops
  • String concatenation patterns
  • Regex efficiency

Data Access

  • N+1 queries
  • Missing indexes
  • Over-fetching data
  • Unoptimized JOINs
  • Missing pagination
  • Cache opportunities

Network

  • Request waterfall
  • Payload sizes
  • Compression enabled
  • CDN utilization
  • Connection reuse

Optimization Principles

  1. Measure before optimizing
  2. Optimize the critical path
  3. Cache expensive operations
  4. Lazy load when possible
  5. Batch operations
  6. Use appropriate data structures

Output Format

BOTTLENECK: [Description]
LOCATION: [file:line or component]
IMPACT: Critical | High | Medium | Low
CURRENT: [Current behavior/metrics]
PROPOSED: [Optimization approach]
EXPECTED GAIN: [Estimated improvement]
COMPLEXITY: Easy | Medium | Hard

Read the full file on GitHub · 108 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. 22d ago Changed · +10 lines 1cd65d1f457e
  2. 1mo ago First seen · 98 lines · 28 tokens per session scan A 901c99dba572

Subscribe to this mod's changes

performance-optimizer is an agent published in the GitHub repository travisjneuman/.claude (105 stars, last pushed today), licensed MIT. It adds 28 tokens to every session and 585 once invoked, about $0.0001 per session on Opus 5.5. 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-09-03.