Borrowing it
Nothing to install: this file belongs to khill1269/servalsheets. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/khill1269/servalsheets/main/.claude/agents/performance-optimizer.mdgit clone --depth 1 https://github.com/khill1269/servalsheetsWrote 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.
[](https://agentmods.dev/agents/khill1269/servalsheets/performance-optimizer)<a href="https://agentmods.dev/agents/khill1269/servalsheets/performance-optimizer"><img src="https://agentmods.dev/badge/agents/khill1269/servalsheets/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.
<a href="https://agentmods.dev/agents/khill1269/servalsheets/performance-optimizer"><img src="https://agentmods.dev/badge/agents/khill1269/servalsheets/performance-optimizer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.1 | $0.00056 | $0.03126 |
| Opus 5.5 | $0.00022 | $0.01250 |
| Sonnet 5.5 | $0.00011 | $0.00625 |
| Haiku 4.5 | $0.00006 | $0.00313 |
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 2mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- performance-optimizer — 100% identical, 0 lines differ
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 });
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.
- 2mo ago First seen · 483 lines · 56 tokens per session scan A 1db0668deab0
performance-optimizer is an agent published in the GitHub repository khill1269/servalsheets (0 stars, last pushed 1mo ago), licensed MIT. It adds 56 tokens to every session and 3,126 once invoked, about $0.0002 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-08-31.
Other agents, from other repositories
chainaware-token-launch-auditor
Audits a new token launch for launchpads by combining rug pull detection on the contract with fraud and behavioral analysis on the deployer wallet. Returns a composite Launch Safety Score, a APPROVED / CONDITIONAL / REJECTED listing verdict, a public-facing safety badge, and specific conditions the launchpad should…
dangerous-agent
An agent with security issues for testing.
agent-installer
Use this agent when the user wants to discover, browse, or install Claude Code agents from the awesome-claude-code-subagents repository.
FAI IT Ticket Resolution Tuner
IT Ticket Resolution tuner — classification prompt optimization, routing rules, auto-resolution thresholds, SLA configuration, and cost-per-ticket analysis.
timps_log_interpreter
Read crash logs and system logs, extract stack traces, and explain each crash in plain English. Classifies as app bug / OS bug / hardware / user error. Pass a log file path to analyse a specific log. Use the timpsloginterpreter MCP tool to perform this task. Do not answer directly — delegate to this sub-agent.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.