performance

A set of guidelines for finding and reducing slowdowns in Electron, React, and web applications. Electron is a framework for desktop apps built with web technologies.

In plain words
What is it for?
Use it when splitting bundles, reducing memory leaks, improving rendering or network behavior, and monitoring application performance.
Why use it?
It gives performance-sensitive work concrete areas and reference targets to check, including loading speed, memory use, bundle size, rendering, and network activity.

Cursor rule

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/adonai-labs/agent-runway/performance
Clone the repo
git clone --depth 1 https://github.com/adonai-labs/agent-runway
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 1,673 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.01673
Opus 5 $0.00000 $0.00837
Sonnet 5 $0.00000 $0.00335
Haiku 4.5 $0.00000 $0.00167

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

Security

Grade A, and why

performance 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 3d 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/core/rules/performance.mdc · 243 lines

How it starts

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

Performance Optimisation Guidelines

Directives for performance-sensitive code. Apply when building or optimising Electron, React, or web applications.


Performance Fundamentals

Key metrics to track

  • Loading: FCP, LCP, FID, CLS
  • Runtime: heap used, heap total, RSS
  • Bundle: main chunk size, renderer chunk size, total size
  • Electron: main process memory, renderer process memory

Performance budgets (reference)

Metric Target Typical threshold
FCP < 1.5s 1500 ms
LCP < 2.5s 2500 ms
FID < 100 ms 100 ms
Main bundle < 1 MB 1024 KB
Renderer bundle < 2 MB 2048 KB
Heap used < 512 MB 512 MB
Memory leak < 10 MB/min 10 MB

Bundle Optimisation

Code splitting

  • Do lazy-load routes with React.lazy and Suspense
  • Do lazy-load heavy components (charts, tables, editors)
const Dashboard = lazy(() => import('./pages/Dashboard'));
const Chart = lazy(() => import('./components/Chart'));
  • Do wrap lazy-loaded routes in <Suspense> with a fallback
  • Don't import everything at the top level; use dynamic imports for feature modules

Tree shaking

  • Do use named exports instead of default exports for utilities
  • Do import only what you need from libraries (e.g. import Button from '@mui/material/Button')
import { Button } from '@/components/ui'; // not import * from '@mui/material'
  • Don't use barrel files that re-export everything; prefer selective exports

Dynamic imports

  • Do use import() for feature modules that are conditionally loaded
  • Do load heavy libraries (charts, analytics) only when needed

Bundle analysis

  • Do run webpack-bundle-analyzer or vite-bundle-analyzer regularly
  • Do add npm run analyze to build scripts
  • Don't ship large dependencies without checking their impact

Memory Management

Leak prevention

  • Do return a cleanup function from every useEffect that registers listeners, timers, or subscriptions
  • Do remove event listeners in useEffect cleanup

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

Subscribe to this mod's changes

performance is a cursor rule published in the GitHub repository adonai-labs/agent-runway (2 stars, last pushed 13d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,673 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.