performance-rules

Coding rules for avoiding slow or resource-heavy operations in a Node.js application. They require asynchronous file and command work, controlled logging, and cleanup of caches and timers.

In plain words
What is it for?
Use them when writing Node.js code that reads files, runs commands, logs diagnostics, stores cached data, or starts repeating timers.
Why use it?
They prevent file reads or shell commands from blocking other work, excessive console output, and resources that remain active after they are needed.

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/sethdford/flowx/performance-rules
Clone the repo
git clone --depth 1 https://github.com/sethdford/flowx

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 2,572 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 $0.00000 $0.02572
Opus 5 $0.00000 $0.01286
Sonnet 5 $0.00000 $0.00514
Haiku 4.5 $0.00000 $0.00257

Measured yesterday against content hash 1f2742cf664e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

performance-rules 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 yesterday.

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.

Runs shell commandslowCapability

Expected in a hook, worth knowing in a rule or an instructions file.

import { execSync, readFileSync } from 'fs';
.cursor/rules/performance-rules.mdc · 394 lines

How it starts

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

Performance Rules: Stay 6x Faster Than Gemini CLI

🚨 PERFORMANCE KILLERS - NEVER DO THESE

Synchronous Operations (Gemini CLI Mistake)

// ❌ FORBIDDEN - Blocks event loop like Gemini CLI
import { execSync, readFileSync } from 'fs';
const result = execSync('command');  // Blocks everything
const content = readFileSync('file.txt');  // Blocks everything

// ✅ REQUIRED - Async operations
import { exec } from 'child_process';
import { readFile } from 'fs/promises';
const result = await exec('command');
const content = await readFile('file.txt');

Console Pollution (Gemini CLI Has 100+)

// ❌ FORBIDDEN - Slows down execution
console.log('debug info');
console.error('error details');
console.warn('warning message');

// ✅ REQUIRED - Use proper logging
import { logger } from '../utils/logger.js';
logger.debug('debug info');
logger.error('error details');
logger.warn('warning message');

Memory Leaks (Gemini CLI Pattern)

// ❌ FORBIDDEN - Memory leaks like Gemini CLI
let globalCache = new Map();  // Never cleaned up
setInterval(() => {}, 1000);  // Never cleared

// ✅ REQUIRED - Proper cleanup
class CacheManager {
  private cache = new Map();
  private cleanupInterval: NodeJS.Timeout;
  
  constructor() {
    this.cleanupInterval = setInterval(() => this.cleanup(), 60000);
  }
  
  cleanup(): void {
    this.cache.clear();
  }
  
  destroy(): void {
    clearInterval(this.cleanupInterval);
    this.cache.clear();
  }
}

⚡ PERFORMANCE PATTERNS - ALWAYS USE THESE

1. Lazy Loading (Beat Gemini CLI Startup)

// ✅ REQUIRED - Lazy load heavy modules
async function getAIClient(): Promise<UnifiedClaudeClient> {
  // Only import when needed
  const { createUnifiedClient } = await import('../ai/unified-client.js');
  return createUnifiedClient();
}

// ❌ WRONG - Heavy imports at startup like Gemini CLI
import { heavyModule } from './heavy-module.js';  // Slows startup

2. Efficient Data Structures

// ✅ REQUIRED - Use appropriate data structures
const userLookup = new Map<string, User>();  // O(1) lookup
const uniqueItems = new Set<string>();       // O(1) contains

// ❌ WRONG - Inefficient structures like Gemini CLI
const userLookup: User[] = [];  // O(n) lookup
const uniqueItems: string[] = [];  // O(n) contains check

Read the full file on GitHub · 394 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. yesterday First seen · 394 lines · 0 tokens per session scan A 1f2742cf664e

Subscribe to this mod's changes

performance-rules is a cursor rule published in the GitHub repository sethdford/flowx (2 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,572 tokens. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.