# Performance Monitor

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.

- subagent · `type=agent` · Claude Code, Codex, Cursor · ★ 850 repo stars
- Author: ruvnet
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/ruvnet/agentic-flow/tree/HEAD/.claude/agents/optimization/performance-monitor.md
- Updated: 2026-10-26
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/agents/ruvnet-performance-monitor

## What it does

Metrics come from several places at once: CPU load, memory pressure, disk and network I/O, process and thread counts. The agent also calls `agent_list` and `agent_metrics` over MCP and scores each agent on efficiency, responsiveness and reliability. Those calls need a running MCP server with both tools, otherwise that half of the report stays empty.

Bottleneck hunting is split across six detectors: CPU, memory, I/O, network, coordination, task queue. They run in parallel and the findings get ranked by severity. A ring buffer holding 1000 entries keeps signatures of past incidents, so a problem that keeps returning is recognised instead of rediscovered.

SLA work goes through `defineSLA`. Defaults are 99.9% availability, 1000 ms response time, 100 requests per second, 0.1% error rate and 300 s recovery, checked every 60 s over a 300 s window. Alert thresholds sit at 0.8, 0.9 and 1.0 of the target.

## Install

### Claude Code (native platform)

**Manually: put the files in place**
- File: `.claude/agents/performance-monitor.md` — For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

### Codex

**Manually: put the files in place**
- File: `.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/

### Cursor

**Manually: put the files in place**
- File: `.cursor/agents/performance-monitor.md` — Cursor also reads .claude/agents/

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/ruvnet/agentic-flow/tree/HEAD/.claude/agents/optimization/performance-monitor.md

## When to use it
- spot which agent is eating the most CPU
- separate a one-off spike from a recurring bottleneck
- set SLA limits and catch breaches as they happen
- read system and agent numbers in a single report
- see whether tasks stall on memory, disk or coordination

## Example prompts
- Collect the current system and agent metrics and show which agent uses the most CPU.
- Analyze the bottlenecks and rank them by severity.
- Define an SLA for the `api` service with 99.9% availability and 1000 ms response time, then check for violations.

## Similar
- [performance-monitor](https://affpapa.org/en/nevibecode/agents/voltagent-performance-monitor.md) — subagent · ★ 6505 repo stars
- [performance-tuner](https://affpapa.org/en/nevibecode/agents/performance-tuner.md) — subagent · ★ 788 repo stars
- [observability-monitoring-monitor-setup](https://affpapa.org/en/nevibecode/skills/observability-monitoring-monitor-setup.md) — skill · ★ 50109 repo stars
- [performance-analysis](https://affpapa.org/en/nevibecode/skills/performance-analysis.md) — skill · 1200 installs
- [V3 Performance Optimization](https://affpapa.org/en/nevibecode/skills/v3-performance-optimization.md) — skill · 1100 installs
- [performance-engineer](https://affpapa.org/en/nevibecode/agents/rohitg00-performance-engineer.md) — subagent · ★ 2858 repo stars

From the same set: [ruvnet/agentic-flow](https://affpapa.org/en/nevibecode/by/ruvnet/agentic-flow.md) — 76 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
