performance-auditor · gupsammy — Claude Code subagent: purpose and setup
The performance-auditor subagent inspects code for algorithmic, data-access, and resource bottlenecks. Use it after changes on hot paths or when you need to reason about how code scales.
no license ★ 276 updated 2026-10-29
/plugin marketplace add gupsammy/Claudest
/plugin install claude-coding@ClaudestWhat performance-auditor does
performance-auditor examines code without running it. It reasons about how costs change as inputs grow, looking for repeated data access, unnecessary passes over collections, and resource growth. Ask a focused question for advice, or request an audit of changed files or a defined scope.
It can use Read, Grep, Glob, and Bash, and keeps project notes about hot paths and performance-sensitive areas. It does not run builds, tests, or benchmarks, so its findings are based on code rather than measured timings. When static inspection cannot settle the impact, profiling is needed.
Its remit is performance. Code quality, security, and architectural structure belong to other named agents, which it may point out without investigating those areas. That boundary matters: this agent’s review is not a substitute for a security audit.
What it helps with
- spot nested iteration whose cost grows with input size
- find external queries or file reads repeated for each collection item
- check for full dataset reads without bounds
- identify accumulating collections and repeated allocations on hot paths
Example prompts for the agent
- Review this changed loop and explain how its cost grows with larger inputs.
- Audit these files for performance bottlenecks, especially queries inside loops.
- Check hot-path code for repeated reads and memory that keeps growing.
How to install performance-auditor
1Plugin marketplace
/plugin marketplace add gupsammy/Claudest/plugin install claude-coding@Claudest2Manually: put the files in place
.claude/agents/performance-auditor.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/performance-auditor.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/performance-auditor.mdCursor also reads .claude/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-auditor
How do I install performance-auditor in Claude Code?
Run /plugin marketplace add gupsammy/Claudest, then run /plugin install claude-coding@Claudest.
What does performance-auditor do?
It inspects code for algorithmic complexity, inefficient data access, and resource-use issues. It can answer a targeted performance question or audit a specified scope without executing the code.
Does performance-auditor run benchmarks?
No. It reasons from the code and does not run builds, tests, or benchmarks. If static inspection cannot establish the impact, it recommends profiling.
Similar subagents
Subagents catalog →performance-auditor by other authors comes first.