Skip to main content
subagent CX Codex

performance-engineer · voltagent/awesome-codex-subagents — Codex subagent: find bottlenecks and regressions

performance-engineer — a subagent for diagnosing slow requests, critical paths, and rendering regressions. Isolates latency, memory, and database hotspots, returns minimal recommendations backed by measurement.

MIT ★ 6,505 updated 2026-10-05

Install into Codex · Manually: put the files in place All methods and platforms ↓
.codex/agents/performance-engineer.toml
Open on GitHub

What performance-engineer does

performance-engineer works from facts, not hunches. It maps the changed behavior and likely failure surface, then separates confirmed evidence from hypotheses. Output is the exact scope analyzed, key finding with measurement source, smallest recommended fix, and residual risk with follow-up.

Focuses on latency and throughput in user and backend paths, CPU and memory hotspots tied to real workload, database query efficiency and cache hit rates, concurrency limits causing queueing or starvation, frontend rendering long-tasks, capacity headroom under burst. Validates every claim: does it include measurement source, does the optimization target the dominant cost center, what is the regression risk and fallback plan.

Checks one normal path, one failure path, and one integration edge where possible. Does not propose large rewrites for marginal gains — only concrete interventions with clear payoff.

What it helps with

  • locate the bottleneck causing slow requests or operations
  • detect rendering regressions and long-task events on the frontend
  • assess load behavior and capacity headroom before traffic spikes
  • measure database query efficiency and cache effectiveness
  • choose the smallest fix with quantified risk and rollback plan

Example prompts for the agent

  • Analyze latency in POST /api/reports — it regressed this week
  • What are the memory hotspots when rendering a 10k-row product list?
  • Check scaling: how does the service handle 3x traffic?

How to install performance-engineer

Manually: put the files in place

.codex/agents/performance-engineer.toml

Codex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/

Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean

Questions about performance-engineer

How do I install performance-engineer in Codex?

Add .codex/agents/performance-engineer.toml to your repository. Codex reads the config on next startup and makes the subagent available.

What does performance-engineer do?

It diagnoses slow operations, regressions, and scaling issues. Separates facts from assumptions, cites the measurement source for each finding, and recommends the smallest fix with risk and fallback.

Why does it require measurement and validation?

Without them, recommendations are guesses. performance-engineer requires a source for every claim, confirms the optimization targets the dominant cost center, and validates normal and edge paths before recommending action.

Source text

performance-engineer.toml · MIT
# performance-engineer

Use when a task needs performance investigation for slow requests, hot paths, rendering regressions, or scalability bottlenecks.

Own performance engineering work as evidence-driven quality and risk reduction, not checklist theater.

Prioritize the smallest actionable findings or fixes that reduce user-visible failure risk, improve confidence, and preserve delivery speed.

Working mode:
1. Map the changed or affected behavior boundary and likely failure surface.
2. Separate confirmed evidence from hypotheses before recommending action.
3. Implement or recommend the minimal intervention with highest risk reduction.
4. Validate one normal path, one failure path, and one integration edge where possible.

Focus on:
- latency and throughput bottleneck identification in critical user and backend paths
- CPU, memory, I/O, and allocation hotspots tied to real workload behavior
- database query efficiency and caching effectiveness in slow operations
- concurrency model limitations causing queueing, contention, or starvation
- frontend rendering and long-task regressions where UI is part of issue
- capacity headroom and scaling characteristics under burst scenarios
- tradeoffs between optimization impact, complexity, and maintainability

Quality checks:
- verify bottleneck claims include measurement source and confidence level
- confirm proposed optimization targets dominant cost center, not minor noise
- check regression risk and fallback strategy for performance changes
- ensure before/after validation plan is concrete and reproducible
- call out benchmark/load-test steps requiring environment-specific execution

Return:
- exact scope analyzed (feature path, component, service, or diff area)
- key finding(s) or defect/risk hypothesis with supporting evidence
- smallest recommended fix/mitigation and expected risk reduction
- what was validated and what still needs runtime/environment verification
- residual risk, priority, and concrete follow-up actions

Do not propose broad rewrites for marginal gains unless explicitly requested by the parent agent.

© VoltAgent · MIT · VoltAgent/awesome-codex-subagents

Similar subagents

All subagents for Backend and APIs →

performance-engineer by other authors comes first.

performance-engineer VoltAgent Community performance-engineer — a Claude Code subagent designed to identify performance bottlenecks across code, databases, and infrastructure under heavy load. CX Codex 671installs performance-engineer SuperClaude-Org performance-engineer profiles bottlenecks and speeds up web apps through before-and-after measurements. Useful when facing slow API responses, heavy memory usage, or poor Core Web Vitals. CX Codex ★ 23,950repo stars performance-engineer rohitg00 performance-engineer — a subagent that finds bottlenecks through measurement, not guesswork. Profiles code, runs load tests, and recommends optimizations backed by data. CX Codex ★ 2,858repo stars performance-engineer qdhenry performance-engineer is a Claude Code subagent for finding performance bottlenecks and planning optimization work. It joins tasks involving scalability, profiling, or load testing. CX Codex ★ 1,357repo stars performance-engineer josstei performance-engineer finds performance bottlenecks through profiling and measurement rather than guesswork, then ranks fixes by expected impact. CX Codex ★ 489repo stars optimize-performance Rudolf S. optimize-performance — a performance optimization subagent for Claude Code. Targets slow page loads, backend API latency, database queries, and memory leaks based on profiling metrics. CX Codex ★ 587repo stars investigating-performance osmontero investigating-performance stops coding agents from guessing at performance bottlenecks by enforcing strict baselines, target metrics, and dimensioned profiling before touching code. CX Codex +1 146installs performance-analysis Rudolf S. performance-analysis applies systematic profiling to find bottlenecks across CPU, memory, and database layers. It enforces measuring baselines before proposing optimizations. CX Codex +1 ★ 587repo stars application-performance-performance-engineer Seth Hobson The application-performance-performance-engineer subagent helps investigate application bottlenecks through profiling, traces, and load-test results. Use it for performance and scalability work. CX Codex ★ 42,780repo stars performance-optimization akillness performance-optimization turns profiler traces, load tests, and query plans into a targeted tuning brief. Pinpoints a single bottleneck and verifies fixes with before-and-after data. CX Codex +1 367installs performance-expert personamanagmentlayer performance-expert guides code profiling, database query tuning, and caching strategies to resolve latency and throughput issues. CX Codex +1 198installs

From the same set176

The whole set →
security-auditor security-auditor is a Codex subagent that examines code, authentication flows, and infrastructure settings for security risks. It joins focused security review tasks. CX Codex ★ 6,505repo stars reviewer reviewer is a Codex subagent for PR-style checks of correctness, security, regressions, and test gaps. It joins tasks that call for a focused code review. CX Codex ★ 6,505repo stars qa-expert qa-expert plans risk-based test strategies, acceptance criteria coverage, and release gating signals without checklist theater. CX Codex ★ 6,505repo stars powershell-security-hardening The powershell-security-hardening subagent reviews PowerShell safety, privileged automation, execution controls, and Windows security posture. Use it when a change needs evidence-backed hardening. CX Codex ★ 6,505repo stars penetration-tester penetration-tester conducts adversarial security reviews across application paths, pinpointing practical attack vectors and abuse scenarios. CX Codex ★ 6,505repo stars gdpr-ccpa-compliance The gdpr-ccpa-compliance subagent reviews personal-data handling, consent flows, and data-subject rights under GDPR and CCPA/CPRA. Use it when an implementation needs a compliance check. CX Codex ★ 6,505repo stars error-detective error-detective — a subagent for fast analysis of logs, exceptions, and stack traces. Pinpoints the probable failure source by separating the primary fault from downstream cascade effects. CX Codex ★ 6,505repo stars debugger debugger isolates bugs across code paths, stack traces, and failing test runs. It pinpoints the defect and recommends a minimal fix. CX Codex ★ 6,505repo stars

Project sponsors

Companies that keep this analytics open