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 rules/adonai-labs/agent-runway/performancegit clone --depth 1 https://github.com/adonai-labs/agent-runwayWhat 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.00000 | $0.01673 |
| Opus 5 | $0.00000 | $0.00837 |
| Sonnet 5 | $0.00000 | $0.00335 |
| Haiku 4.5 | $0.00000 | $0.00167 |
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.
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.lazyandSuspense - 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-analyzerorvite-bundle-analyzerregularly - Do add
npm run analyzeto build scripts - Don't ship large dependencies without checking their impact
Memory Management
Leak prevention
- Do return a cleanup function from every
useEffectthat registers listeners, timers, or subscriptions - Do remove event listeners in
useEffectcleanup
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.
- 3d ago First seen · 243 lines · 0 tokens per session scan A 3f2890e2682e
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.
Other cursor rules, from other repositories
archgate-governance
Archgate ADR governance — enforces architecture decision records.
cursorrules
When the user asks you to generate diagrams, analyze code structure, or visualize architecture, follow this analysis pipeline. Use terminal commands (rg, find, cat) for all file operations.
arch4
Keep Arch4 architecture maps current.
cursorrules
You are working with a React Native (Expo) architecture reference project. Read the skill files before generating any code.
archcore-files
Enforce MCP-only operations when working with .archcore/ files.
execution
Repository execution and verification commands.