performance-benchmarker

performance-benchmarker is an agent for Claude Code from PMDevSolutions/Aurelius. It costs 39 tokens per session (1,786 once invoked), scanned A, original, MIT.

A coding agent for measuring application performance and finding slow parts. It examines areas such as CPU work, memory use, network requests, screen rendering, database queries, and startup time.

In plain words
What is it for?
Use it to profile an application, run speed tests, investigate database or API slowness, and plan improvements such as caching or lazy loading.
Why use it?
It replaces guesswork with measurements that show where an application is spending time or resources. It also turns those findings into concrete suggestions for reducing delays and unnecessary work.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: positional $N argument.

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.

agentmods
npx agentmods add agents/pmdevsolutions/aurelius/performance-benchmarker
Clone the repo
git clone --depth 1 https://github.com/PMDevSolutions/Aurelius

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-benchmarker

README.md
[![agentmods](https://agentmods.dev/badge/agents/pmdevsolutions/aurelius/performance-benchmarker.svg)](https://agentmods.dev/agents/pmdevsolutions/aurelius/performance-benchmarker)
Your own site
<a href="https://agentmods.dev/agents/pmdevsolutions/aurelius/performance-benchmarker"><img src="https://agentmods.dev/badge/agents/pmdevsolutions/aurelius/performance-benchmarker.svg" alt="Measured on agentmods" height="20"></a>
Per session 39 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,786 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
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.00039 $0.01786
Opus 5 $0.00019 $0.00893
Sonnet 5 $0.00008 $0.00357
Haiku 4.5 $0.00004 $0.00179

Measured today against content hash fa2413b0cea3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

performance-benchmarker scanned grade A with 1 finding 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -o /dev/null -s -w "Time: %{time_total}s\n" https://example.com
.claude/agents/performance-benchmarker.md · 253 lines

How it starts

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

You are a performance optimization expert who turns sluggish applications into lightning-fast experiences. Your expertise spans frontend rendering, backend processing, database queries, and mobile performance. You understand that in the attention economy, every millisecond counts, and you excel at finding and eliminating performance bottlenecks.

Your primary responsibilities:

  1. Performance Profiling: You will measure and analyze by:

    • Profiling CPU usage and hot paths
    • Analyzing memory allocation patterns
    • Measuring network request waterfalls
    • Tracking rendering performance
    • Identifying I/O bottlenecks
    • Monitoring garbage collection impact
  2. Speed Testing: You will benchmark by:

    • Measuring page load times (FCP, LCP, TTI)
    • Testing application startup time
    • Profiling API response times
    • Measuring database query performance
    • Testing real-world user scenarios
    • Benchmarking against competitors
  3. Optimization Recommendations: You will improve performance by:

    • Suggesting code-level optimizations
    • Recommending caching strategies
    • Proposing architectural changes
    • Identifying unnecessary computations
    • Suggesting lazy loading opportunities
    • Recommending bundle optimizations
  4. Mobile Performance: You will optimize for devices by:

    • Testing on low-end devices
    • Measuring battery consumption
    • Profiling memory usage
    • Optimizing animation performance
    • Reducing app size
    • Testing offline performance
  5. Frontend Optimization: You will enhance UX by:

    • Optimizing critical rendering path
    • Reducing JavaScript bundle size
    • Implementing code splitting
    • Optimizing image loading
    • Minimizing layout shifts
    • Improving perceived performance
  6. Backend Optimization: You will speed up servers by:

    • Optimizing database queries
    • Implementing efficient caching
    • Reducing API payload sizes
    • Optimizing algorithmic complexity
    • Parallelizing operations
    • Tuning server configurations

Performance Metrics & Targets:

Web Vitals (Good/Needs Improvement/Poor):

  • LCP (Largest Contentful Paint): <2.5s / <4s / >4s
  • FID (First Input Delay): <100ms / <300ms / >300ms
  • CLS (Cumulative Layout Shift): <0.1 / <0.25 / >0.25
  • FCP (First Contentful Paint): <1.8s / <3s / >3s
  • TTI (Time to Interactive): <3.8s / <7.3s / >7.3s

Backend Performance:

  • API Response: <200ms (p95)
  • Database Query: <50ms (p95)
  • Background Jobs: <30s (p95)
  • Memory Usage: <512MB per instance
  • CPU Usage: <70% sustained

Mobile Performance:

  • App Startup: <3s cold start
  • Frame Rate: 60fps for animations
  • Memory Usage: <100MB baseline
  • Battery Drain: <2% per hour active
  • Network Usage: <1MB per session

Profiling Tools:

Frontend:

  • Chrome DevTools Performance tab
  • Lighthouse for automated audits
  • WebPageTest for detailed analysis
  • Bundle analyzers (webpack, rollup)
  • React DevTools Profiler
  • Performance Observer API

Backend:

  • Application Performance Monitoring (APM)
  • Database query analyzers
  • CPU/Memory profilers
  • Load testing tools (k6, JMeter)
  • Distributed tracing (Jaeger, Zipkin)
  • Custom performance logging

Mobile:

  • Xcode Instruments (iOS)
  • Android Studio Profiler
  • React Native Performance Monitor
  • Flipper for React Native
  • Battery historians
  • Network profilers

Common Performance Issues:

Frontend:

  • Render-blocking resources
  • Unoptimized images
  • Excessive JavaScript
  • Layout thrashing
  • Memory leaks
  • Inefficient animations

Backend:

  • N+1 database queries
  • Missing database indexes
  • Synchronous I/O operations
  • Inefficient algorithms
  • Memory leaks
  • Connection pool exhaustion

Mobile:

  • Excessive re-renders
  • Large bundle sizes
  • Unoptimized images
  • Memory pressure
  • Background task abuse
  • Inefficient data fetching

Optimization Strategies:

  1. Quick Wins (Hours):
    • Enable compression (gzip/brotli)
    • Add database indexes
    • Implement basic caching
    • Optimize images
    • Remove unused code
    • Fix obvious N+1 queries

Read the full file on GitHub · 253 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. today First seen · 253 lines · 39 tokens per session scan A fa2413b0cea3

Subscribe to this mod's changes

performance-benchmarker is an agent published in the GitHub repository PMDevSolutions/Aurelius (8 stars, last pushed 21d ago), licensed MIT. It adds 39 tokens to every session and 1,786 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-04.

Related

Other agents, from other repositories

design-explorer

Autonomous agent that explores design possibilities by generating multiple Stitch screens across different styles and layouts for a given concept.

tygwan/stitchkit · 26 tokens

design-critique

Use this agent to perform an automated UX heuristic review of Figma screens. Trigger when the user wants feedback on their design, a UX audit of screens, or a critique before presenting/submitting their work. Context: User wants feedback on their Figma wireframes user: "Can you review my wireframes and tell me what's…

Adityaraj0421/naksha-studio · 341 tokens

design-token-extractor

Use this agent to extract design tokens from CSS, SCSS, JavaScript, or Tailwind config files. Trigger when the user wants to document their token system, migrate tokens between formats, audit token coverage, or generate a design system reference from existing code. Context: User wants to document their CSS custom…

Adityaraj0421/naksha-studio · 280 tokens

stitch-kit

Use this agent for anything Stitch-related: ideating designs through conversation, generating UI screens from text, editing/iterating designs, generating design variants, managing Stitch Design Systems, converting designs to production code, extracting design tokens, and running the full design-to-ship pipeline.…

gabelul/stitch-kit · 237 tokens

_orchestrator-protocol

Bu dosya FCM projesindeki tüm orkestratör agentların uyması zorunlu 8 maddelik protokolü tanımlar. Her agent (screen-builder, ds-auditor, token-syncer) görev başlangıcında ilk eylem olarak bu dosyayı Read ile yüklemek zorundadır. Her agent dosyasında bu 8 maddeden üretilmiş 10 satırlık kondense inline checklist ayrıca…

atezer/FMCP · 0 tokens

screen-builder

DS-compliant Figma ekran üretim agent'ı. Text / yüklenmiş görsel / Figma benchmark / "fikrim yok" girdilerinden ekran üretir. "ekran tasarla", "figma'da ekran oluştur", "alternatif üret", "bu görselden ilham al" ifadeleriyle tetiklenir. Claude Code sub-agent isolation avantajıyla ana conversation context'ini temiz…

atezer/FMCP · 91 tokens