performance-engineer

performance-engineer is an agent for Claude Code from calinfaja/K-LEAN. It costs 40 tokens per session (1,438 once invoked), scanned A, original, Apache-2.0.

An engineering guide for finding and fixing application slowdowns. It covers measuring performance, load testing, caching, databases, network delivery, and browser speed.

In plain words
What is it for?
Use it to profile applications, design load tests, optimize database queries and APIs, configure caching or content delivery, and track browser performance.
Why use it?
It helps identify the real bottleneck before changing code and provides a structured way to improve response times and capacity.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: model in frontmatter; names the TodoWrite tool.

Good fit Use it to profile applications, design load tests, optimize database queries and APIs, configure caching or content delivery, and track browser performance.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/calinfaja/k-lean/performance-engineer
Install

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.

Clone the repo
git clone --depth 1 https://github.com/calinfaja/K-LEAN

Made for: Claude Code.

Wrote 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.

agentmods badge for performance-engineer

README.md
[![agentmods](https://agentmods.dev/badge/agents/calinfaja/k-lean/performance-engineer/github.svg)](https://agentmods.dev/agents/calinfaja/k-lean/performance-engineer)
Your own site
<a href="https://agentmods.dev/agents/calinfaja/k-lean/performance-engineer"><img src="https://agentmods.dev/badge/agents/calinfaja/k-lean/performance-engineer/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for performance-engineer

Your own site · 80×15
<a href="https://agentmods.dev/agents/calinfaja/k-lean/performance-engineer"><img src="https://agentmods.dev/badge/agents/calinfaja/k-lean/performance-engineer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 40 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,438 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00040 $0.01438
Opus 5.5 $0.00016 $0.00575
Sonnet 5.5 $0.00008 $0.00288
Haiku 4.5 $0.00004 $0.00144

Measured 1mo ago against content hash 92a6af8b308e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo ago.

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.

src/klean/data/agents/performance-engineer.md · 193 lines

How it starts

The opening of the file, as written. The whole thing — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Citation Requirements

All findings MUST include verified file:line references:

  1. Use grep_with_context to find issues - it returns exact line numbers
  2. ONLY cite line numbers that appear in tool output
  3. Include code snippet context for each finding
  4. Format: filename.py:123 or path/to/file.js:45-50

You are a performance engineer specializing in application optimization and scalability.

When invoked:

  1. Analyze application performance bottlenecks through comprehensive profiling
  2. Design and execute load testing strategies with realistic scenarios
  3. Implement multi-layer caching strategies for optimal performance
  4. Optimize database queries and API response times
  5. Monitor and improve frontend performance including Core Web Vitals
  6. Establish performance budgets and continuous monitoring systems

Process:

  • Always measure before optimizing to establish baseline metrics
  • Focus on biggest bottlenecks first for maximum impact
  • Set realistic performance budgets and SLA targets
  • Implement caching at appropriate layers (browser, CDN, application, database)
  • Load test with realistic user scenarios and traffic patterns
  • Profile applications for CPU, memory, and I/O bottlenecks
  • Focus on user-perceived performance and business impact
  • Monitor continuously with automated alerts and dashboards

Provide:

  • Performance profiling results with detailed flamegraphs and analysis
  • Load test scripts and comprehensive results with traffic scenarios
  • Multi-layer caching implementation with TTL strategies and invalidation
  • Optimization recommendations ranked by impact and implementation effort
  • Before/after performance metrics with specific numbers and benchmarks
  • Monitoring dashboard setup with key performance indicators
  • Database query optimization with execution plan analysis
  • Frontend performance optimization for Core Web Vitals improvements

Immediate Actions

When invoked, ALWAYS:

  1. Gather Context
    # Check for existing benchmarks
    find . -name "*bench*" -o -name "*perf*" | head -10
    # Check package.json for scripts
    grep -A5 "scripts" package.json 2>/dev/null
    # Look for database queries
    grep -rn "SELECT\|INSERT\|UPDATE" --include="*.sql" --include="*.ts" --include="*.js" | head -20
    

Read the full file on GitHub · 193 lines

Changes

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.

  1. 1mo ago First seen · 193 lines · 40 tokens per session scan A 92a6af8b308e

Subscribe to this mod's changes

performance-engineer is an agent published in the GitHub repository calinfaja/K-LEAN (35 stars, last pushed 8d ago), licensed Apache-2.0. It adds 40 tokens to every session and 1,438 once invoked, about $0.0002 per session on Opus 5.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-08-30.

Related

Other agents, from other repositories

bug-plan-creator-default

Architectural Bug Investigation Agent. Deep investigation with line-by-line code analysis, produces fix plans with exact code changes, regression prevention, and verification criteria. Plans work with any executor (loop or swarm).

GantisStorm/essentials-claude-code · 46 tokens

harness-doctor

The omp harness inspection + management device. Runs the deterministic health check (harness-check.py) that audits the WHOLE setup in one pass — every agent parses, tools are valid, autoloadSkills resolve (with source classification: omp-native vs vendor-plugin), no duplicate names or bundled collisions, config.yml…

jhlee0409/omni-harness-kit · 151 tokens

sniper

Use when: after ANY code modification (mandatory post-edit validation). Do NOT use for: new features, quick fixes already identified (use sniper-faster), read-only analysis.

fusengine/agents · 38 tokens

silent-failure-hunter

Error handling review agent for CI: identifies silent failures, empty catch blocks, swallowed errors, overly broad exception handling, and missing user feedback in PR diffs.

rube-de/cc-skills · 38 tokens

patch-generator

Implements the fix for one finding inside a scratch workspace clone, staged for review and delivery as a patch file; dispatched by the fix job, not for direct invocation.

fuxicodex/Fuxi · 37 tokens

fec-ui-checker

Use this subagent to troubleshoot visual defects, layout confusion, CSS issues, responsive exceptions, and inconsistencies between interaction and design in the front-end UI, and save the report as a Markdown file. Supports obtaining design data from Figma, Sketch, MasterGo, Pixso, Moko, and Mock, compares the design…

bovinphang/frontend-craft · 89 tokens