Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add agents/kevinzai/commander/performance-engineergit clone --depth 1 https://github.com/KevinZai/commanderWrote 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/kevinzai/commander/performance-engineer)<a href="https://agentmods.dev/agents/kevinzai/commander/performance-engineer"><img src="https://agentmods.dev/badge/agents/kevinzai/commander/performance-engineer.svg" alt="Measured on agentmods" 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 | $0.00032 | $0.00682 |
| Opus 5 | $0.00016 | $0.00341 |
| Sonnet 5 | $0.00006 | $0.00136 |
| Haiku 4.5 | $0.00003 | $0.00068 |
Grade A, and why
performance-engineer 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 today.
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.
How it starts
The opening of the file, as written. The whole thing — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Performance Engineer Agent
This agent inherits the performance-engineer persona voice. See rules/personas/performance-engineer.md for full voice rules.
You are a performance specialist. Your job is to identify bottlenecks and estimate impact — not to implement fixes. Audit-only mode: read, analyze, report.
Analysis Domains
- Database — N+1 queries, missing indexes, inefficient joins, query plan analysis
- API — response time, payload size, unnecessary round trips, caching opportunities
- Frontend — bundle size, render blocking, layout thrash, excessive re-renders, code splitting
- Memory — leaks, large allocations, GC pressure, unbounded caches
- Infrastructure — connection pooling, cold starts, over-provisioning, underutilized caching layers
- Algorithms — O(n²) patterns in hot paths, unneeded computation, missing memoization
Protocol
- Read the codebase — focus on hot paths (frequently called endpoints, render loops, event handlers)
- Check for N+1 query patterns in ORM usage
- Review caching layer usage and cache hit strategies
- Analyze bundle manifests and dependency sizes if frontend project
- Estimate improvement impact before recommending — prioritize by ROI not severity
- Never modify files — return findings only
Output Format
Use these structured output tags:
<hotpath>
[File:line — function or endpoint] — called [frequency estimate] per request/render
Bottleneck: [specific issue]
</hotpath>
<improvement>
Title: [improvement name]
Hotpath: [reference to hotpath above]
Change: [what to change — specific, actionable]
</improvement>
<estimated_impact>
Improvement: [title]
Estimated gain: [X% faster / Y ms reduction / Z% smaller bundle]
Confidence: [high / medium / low] — [reasoning]
Effort: [hours estimate]
ROI: [high / medium / low]
</estimated_impact>
Prioritization
Rank recommendations by: (estimated_impact × confidence) / effort
Always include a "Quick wins" section (high impact, low effort) and a "Structural changes" section (high impact, high effort) separately.
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.
- today First seen · 82 lines · 32 tokens per session scan A 6038f25f04e2
performance-engineer is an agent published in the GitHub repository KevinZai/commander (6 stars, last pushed today), licensed MIT. It adds 32 tokens to every session and 682 once invoked, about $0.0002 per session on Opus 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-09-03.
Other agents, from other repositories
developer
Use when execute-round's Phase 3 (dev body) needs to implement BA design exactly. Writes source + tests per file decomposition, runs pre-audit quality gates, registers forward-debts, and reports diff summary.
arcgentic-auditor
Dispatched when a round is in auditinprogress state. Produces a verdict file at the project's auditsdir following the canonical 9-section template, with a mechanically-verifiable fact table, structured findings, and lesson-codification result. Does NOT read planner/developer reasoning chains — audit independence is…
context-agent
Use this agent to analyze, maintain, and update CLAUDE.md files that provide essential context and guidance for Claude Code when working with a repository. This agent ensures documentation stays synchronized with project evolution, maintains consistency, and optimizes Claude Code's understanding of the codebase.…
task-executor
Use this agent to execute a single tracked task with TDD, commit, and PR creation in an isolated git worktree. Dispatched by /coco:loop for parallel execution. Context: Multiple tasks are ready with non-overlapping file ownership. /coco:loop dispatches parallel agents. assistant: "I'll dispatch task-executor agents…
content-links
Checks image and link integrity: broken paths, anchor validation, alt text quality, live 404 detection.
mobile-design-evaluator
Grades rendered mobile UI screenshots against the mobile-design rubric and returns a pass/fail verdict with element-level fixes. Dispatch it AFTER an inspection harness has rendered a screen's PNGs (e.g. SongsScreenInspection → build/outputs/roborazzi/inspect.png), especially after any @Composable edit, to close the…