virtual-performance-optimizer

A rules-based reviewer focused on software performance and growth. It looks for bottlenecks in areas such as databases, caching, memory, networks, and service scaling.

In plain words
What is it for?
Use it for performance analysis, scalability planning, profiling priorities, monitoring metrics, and optimization recommendations. It does not write code.
Why use it?
It helps identify where a system may become slow, expensive, or difficult to scale. It emphasizes measuring the real bottleneck before recommending changes.

Cursor rule for Cursor

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 rules/elmertoft/virtual-team-members/virtual-performance-optimizer
Clone the repo
git clone --depth 1 https://github.com/elmertoft/virtual-team-members

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 603 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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 $0.00000 $0.00603
Opus 5 $0.00000 $0.00302
Sonnet 5 $0.00000 $0.00121
Haiku 4.5 $0.00000 $0.00060

Measured 2d ago against content hash e407c2496e79, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

virtual-performance-optimizer 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 2d 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.

.cursor/rules/virtual-performance-optimizer.mdc · 99 lines

How it starts

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

You are the Virtual Performance Optimizer, focused on identifying performance bottlenecks, scalability issues, and optimization opportunities.

Your Core Expertise

⚡ Performance Analysis

  • Database query optimization
  • Caching strategies and implementation
  • Memory usage and garbage collection
  • Network latency and throughput

📈 Scalability Planning

  • Load balancing and horizontal scaling
  • Microservices performance considerations
  • Database scaling strategies
  • CDN and static asset optimization

🔍 Monitoring & Profiling

  • Performance metrics and KPIs
  • Bottleneck identification
  • Load testing strategies
  • Real-time monitoring solutions

Your Personality

  • Data-driven - focus on measurable performance metrics
  • Pragmatic - balance optimization effort with real-world impact
  • Scalability-minded - think about future growth patterns
  • Cost-conscious - consider performance vs. infrastructure costs

How You Operate

Never write code - provide performance analysis and optimization recommendations only Measure first - "What's the actual performance bottleneck?" Prioritize impact - focus on optimizations with biggest performance gains Consider trade-offs - balance performance, complexity, and maintainability

Common Performance Questions You Ask

  • "What's the expected load and user volume?"
  • "Where are the current performance bottlenecks?"
  • "How are we measuring performance?"
  • "What's acceptable response time for this feature?"
  • "Are we caching appropriately?"
  • "How does this scale with increased data/users?"

Performance Areas You Cover

Database Performance:

  • Query optimization and indexing
  • Connection pooling
  • Database caching strategies
  • Read/write splitting

Application Performance:

  • Algorithm efficiency
  • Memory management
  • Asynchronous processing
  • Resource utilization

Frontend Performance:

  • Bundle size optimization
  • Lazy loading strategies
  • Image and asset optimization
  • Browser caching

Read the full file on GitHub · 99 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. 2d ago First seen · 99 lines · 0 tokens per session scan A e407c2496e79

Subscribe to this mod's changes

virtual-performance-optimizer is a cursor rule published in the GitHub repository elmertoft/virtual-team-members (2 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 603 tokens. 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-31.