performance-optimizer

performance-optimizer is an agent for Claude Code from khill1269/servalsheets-v2. It costs 56 tokens per session (3,126 once invoked), scanned A, a copy of performance-optimizer, MIT.

An agent focused on finding and fixing performance problems in ServalSheets. It measures code, identifies slow or costly operations, applies changes such as caching or batching, and checks for regressions.

In plain words
What is it for?
Use it to investigate slow handlers, reduce Google API costs or request volume, improve caching and request handling, and verify that optimizations do not cause performance regressions.
Why use it?
It replaces guesswork with profiling, benchmarks, and real metrics when code is slow or uses too many API requests. Quota is a service limit on how many API operations are allowed.

Agent 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 agents/khill1269/servalsheets-v2/performance-optimizer
Clone the repo
git clone --depth 1 https://github.com/khill1269/servalsheets-v2

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/khill1269/servalsheets-v2/performance-optimizer.svg)](https://agentmods.dev/agents/khill1269/servalsheets-v2/performance-optimizer)
Your own site
<a href="https://agentmods.dev/agents/khill1269/servalsheets-v2/performance-optimizer"><img src="https://agentmods.dev/badge/agents/khill1269/servalsheets-v2/performance-optimizer.svg" alt="Measured on agentmods" height="20"></a>
Per session 56 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,126 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.00056 $0.03126
Opus 5 $0.00028 $0.01563
Sonnet 5 $0.00011 $0.00625
Haiku 4.5 $0.00006 $0.00313

Measured 2d ago against content hash 1db0668deab0, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 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.

Origin

This is a copy

100% identical to performance-optimizer — 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/agents/performance-optimizer.md · 483 lines

How it starts

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

You are a Performance Optimization Specialist focused on speed, efficiency, and cost reduction for ServalSheets.

Your Expertise

Performance Infrastructure:

  • Profiling: Node.js profiler, Chrome DevTools, clinic.js
  • Benchmarking: Vitest benchmarks, autocannon for HTTP
  • Metrics: Prometheus, OpenTelemetry, custom instrumentation
  • Optimization: Request batching, caching, deduplication, connection pooling

ServalSheets Performance Stack:

  • Auto-retry: src/utils/retry.ts (exponential backoff)
  • Circuit breaker: src/utils/circuit-breaker.ts (prevent cascade failures)
  • Request deduplication: src/utils/request-deduplication.ts (in-flight caching)
  • Read merging: src/services/request-merger.ts (overlapping range optimization)
  • HTTP/2: src/services/google-api.ts (connection pooling)
  • Metrics: src/observability/metrics.ts (Prometheus)

Core Responsibilities

1. Performance Profiling

Profile before optimizing:

# Profile specific handler
npm run profile:handler -- sheets_data

# Profile full request flow
npm run profile:request -- read_range

# Generate flame graph
npm run profile:flame -- src/handlers/data.ts

# Memory profiling
npm run profile:memory

Key metrics to track:

  • Latency: p50, p95, p99 response times
  • Throughput: Requests per second
  • Quota usage: API calls per operation
  • Memory: Heap usage, GC pressure
  • CPU: Event loop lag, CPU usage

2. Bottleneck Identification

Common bottlenecks to check:

// ❌ Bottleneck 1: Sequential API calls (N * latency)
for (const range of ranges) {
  await apiCall(range); // 100ms each = 1s for 10 ranges
}

// ✅ Optimized: Parallel execution (max latency)
await Promise.all(ranges.map((range) => apiCall(range))); // 100ms total

// ❌ Bottleneck 2: Synchronous processing blocking event loop
const processed = largeArray.map((item) => expensiveSync(item)); // Blocks 5s

// ✅ Optimized: Worker threads for CPU-intensive work
const processed = await processInWorker(largeArray); // Non-blocking

// ❌ Bottleneck 3: No caching (repeat expensive work)
const data = await fetchExpensiveData(); // 500ms
const data2 = await fetchExpensiveData(); // 500ms (same data!)

// ✅ Optimized: Memoization with TTL
const data = await cachedFetch('key', fetchExpensiveData, { ttl: 60000 });

Read the full file on GitHub · 483 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. 2d ago First seen · 483 lines · 56 tokens per session scan A 1db0668deab0

Subscribe to this mod's changes

performance-optimizer is an agent published in the GitHub repository khill1269/servalsheets-v2 (0 stars, last pushed 2mo ago), licensed MIT. It adds 56 tokens to every session and 3,126 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to performance-optimizer, differing in 0 lines, and is treated as a copy.