Skip to main content
subagent CX Codex

performance-monitor · voltagent/awesome-codex-subagents — Codex subagent: what it does, how to install

performance-monitor triages build, runtime, and operational metrics, weeds out noise, and pinpoints responsible subsystems before heavy profiling starts.

MIT ★ 6,505 updated 2026-10-05

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

What performance-monitor does

This subagent handles early-warning metric triage across environments. It correlates metric swings with recent deployments, configuration adjustments, and workload patterns rather than guessing root causes. The triage classifies dominant signals into CPU, memory, IO, queueing, or latency.

The final summary ranks suspected owner areas with explicit confidence levels, notes missing telemetry, and details confounders like instrumentation drift or synthetic test traffic. It intentionally treats metric links as correlation rather than confirmed causation unless parent agents demand otherwise.

What it helps with

  • separate metric regression signals from normal baseline variance
  • classify resource bottlenecks across CPU, memory, IO, and latency
  • map runtime latency spikes to recent releases or config changes
  • identify the most probable subsystem owner before deep profiling

Example prompts for the agent

  • Inspect runtime latency spikes after the latest release and triage the dominant resource signal.
  • Check memory metrics on the worker nodes and separate baseline variance from a true regression.
  • Triage build duration changes over the last two sprints and recommend the next diagnostic step.

How to install performance-monitor

Manually: put the files in place

.codex/agents/performance-monitor.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-monitor

How to install performance-monitor in Codex?

Save the subagent configuration file directly into .codex/agents/performance-monitor.toml.

What does performance-monitor do?

It evaluates performance metrics across build and runtime environments, isolates actionable signals from noise, and maps out the next diagnostic step.

Does performance-monitor prove root cause?

It identifies probable triggers and ranks likely owner subsystems, but avoids treating correlation as confirmed causality unless instructed by the caller.

Source text

performance-monitor.toml · MIT
# performance-monitor

Use when a task needs ongoing performance-signal interpretation across build, runtime, or operational metrics before deeper optimization starts.

Own performance signal triage as early-warning interpretation before deep optimization work begins.

Distinguish meaningful regressions from noise and route investigation to the right owner quickly.

Working mode:
1. Map metric movement by timeframe, subsystem, and recent change context.
2. Separate signal from noise using baseline variance and impact magnitude.
3. Identify most probable ownership boundary for deeper investigation.
4. Recommend next diagnostic step with highest information gain.

Focus on:
- metric definition integrity and comparability across periods/environments
- severity weighting by user impact and business-critical path relevance
- correlation with releases, config changes, and workload shifts
- dominant resource signal (CPU, memory, IO, latency, queueing) classification
- confidence scoring for likely owner subsystem
- alert fatigue reduction through prioritized triage output
- handoff readiness for specialist performance engineering follow-up

Quality checks:
- verify observed movement exceeds expected baseline noise
- confirm candidate root-area ranking includes confidence and caveats
- check for confounders (traffic mix, synthetic tests, instrumentation drift)
- ensure next-step recommendation is specific and executable
- call out missing telemetry needed to avoid misrouting effort

Return:
- concise performance summary and impact assessment
- likely owner area(s) with confidence ranking
- probable trigger candidates and evidence basis
- next investigative action and why it is highest leverage
- data gaps and monitoring improvements needed

Do not label correlation as confirmed causality unless explicitly requested by the parent agent.

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

Similar subagents

All subagents for DevOps and infrastructure →

performance-monitor by other authors comes first.

performance-monitor VoltAgent Community performance-monitor analyzes existing logs and metric files, spots bottlenecks, and writes an evidence-cited observability plan in Markdown. Useful for auditing performance from stored run data. CX Codex 298installs 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 Performance Monitor ruvnet Performance Monitor collects system and agent metrics, hunts bottlenecks and watches SLA thresholds. Useful when several agents run at once and it is unclear which one is slow. CX Codex ★ 850repo stars 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 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 Seth Hobson performance-optimization coordinates end-to-end performance audits, database optimizations, frontend tuning, and load testing. CX Codex +1 ★ 126repo stars wp-performance WordPress wp-performance is a Claude Code skill that profiles WordPress backends with WP-CLI, REST headers, and diagnostic scripts, without browser access. CX Codex +1 7,200installs

From the same set176

The whole set →
cohort-analysis cohort-analysis — a subagent for diagnosing product health via retention curves and user cohort behavior. Separates product-market-fit problems from growth issues and identifies activation moments that predict long-term engagement. CX Codex ★ 6,505repo stars ab-test-analysis ab-test-analysis evaluates A/B test data, inspects statistical and practical significance, and delivers principled ship or no-ship decisions. CX Codex ★ 6,505repo stars workflow-orchestrator The workflow-orchestrator subagent turns a complex request into staged Codex work, with delegation rules, validation gates, integration steps, and failure handling. CX Codex ★ 6,505repo stars task-distributor task-distributor is a Codex subagent that breaks broad tasks into work units with boundaries, dependencies, and ownership. It divides work across agents without duplication or overlap. CX Codex ★ 6,505repo stars multi-agent-coordinator The multi-agent-coordinator subagent divides work between the parent agent and parallel delegates, sets ownership boundaries, and plans how results come together. Use it for tasks with separable workstreams. CX Codex ★ 6,505repo stars knowledge-synthesizer knowledge-synthesizer merges reports from several agents into one picture: what is confirmed, where findings disagree, and what to do next. CX Codex ★ 6,505repo stars it-ops-orchestrator it-ops-orchestrator coordinates complex operational planning across infrastructure, identity, endpoints, and incident response teams. CX Codex ★ 6,505repo stars error-coordinator error-coordinator groups multiple errors by likely cause, sets investigation priorities, and routes each cluster to a suitable specialist. Use it when symptoms pile up and the first fault is unclear. CX Codex ★ 6,505repo stars

Project sponsors

Companies that keep this analytics open