event-handling-performance

event-handling-performance is a cursor rule for Cursor from adobecom/da-express-milo. It costs 2,966 tokens per session, scanned A, original, Apache-2.0.

A set of coding rules for handling browser events efficiently in Adobe Experience Manager (AEM), a system for managing website content. It divides event work into eager, lazy, and delayed phases.

In plain words
What is it for?
Use it when adding or reviewing click, scroll, resize, mouse, or third-party event handlers, especially on pages where loading speed matters.
Why use it?
It helps prevent unnecessary event listeners and heavy browser work from slowing the first part of a webpage.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it when adding or reviewing click, scroll, resize, mouse, or third-party event handlers, especially on pages where loading speed matters.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/adobecom/da-express-milo/event-handling-performance
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.

Clone the repo
git clone --depth 1 https://github.com/adobecom/da-express-milo

Made for: Cursor.

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 event-handling-performance

README.md
[![agentmods](https://agentmods.dev/badge/rules/adobecom/da-express-milo/event-handling-performance/github.svg)](https://agentmods.dev/rules/adobecom/da-express-milo/event-handling-performance)
Your own site
<a href="https://agentmods.dev/rules/adobecom/da-express-milo/event-handling-performance"><img src="https://agentmods.dev/badge/rules/adobecom/da-express-milo/event-handling-performance/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for event-handling-performance

Your own site · 80×15
<a href="https://agentmods.dev/rules/adobecom/da-express-milo/event-handling-performance"><img src="https://agentmods.dev/badge/rules/adobecom/da-express-milo/event-handling-performance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 2,966 This file is loaded in full into every session.
When invoked 2,966 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.02966 $0.02966
Opus 5.5 $0.01186 $0.01186
Sonnet 5.5 $0.00593 $0.00593
Haiku 4.5 $0.00297 $0.00297

Measured 2mo ago against content hash c0be240db405, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

event-handling-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 2mo 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.cursor/rules/event-handling-performance.mdc · 423 lines

How it starts

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

Event Handling Performance Rules - Three-Phase Strategy

APPLY: EVERY QUERY - CRITICAL PERFORMANCE RULE

AEM Performance Principles (REQUIRED)

Based on AEM's performance guidelines:

  • Phase E (Eager): Minimal event handlers for LCP elements only
  • Phase L (Lazy): Interactive enhancements and below-fold interactions
  • Phase D (Delayed): Third-party event handlers after 3+ second delay

Phase E - Critical Event Handlers Only (REQUIRED)

Minimal event attachment for LCP elements to stay under 100kb budget

// ✅ REQUIRED - Phase E: Only critical event handlers for LCP elements
const attachCriticalEvents = (element) => {
  const isFirstSection = element.closest('.section') === document.querySelector('.section');
  
  if (isFirstSection) {
    // Phase E: Only essential events for LCP elements
    if (element.matches('button, [role="button"]')) {
      element.addEventListener('click', handleCriticalAction, { passive: false });
    }
    
    // Avoid heavy event handlers in Phase E
    // NO scroll listeners, resize handlers, or mouse tracking
  } else {
    // Phase L: Full event handling for below-fold elements
    attachEnhancedEvents(element);
  }
};

Phase L - Enhanced Event Handling (REQUIRED)

Full interactive functionality after LCP is achieved

// ✅ REQUIRED - Phase L: Rich interactions after LCP
const attachEnhancedEvents = (element) => {
  // Wait for LCP before adding interactive enhancements
  const observer = new PerformanceObserver((list) => {
    const lcpEntry = list.getEntries()[list.getEntries().length - 1];
    if (lcpEntry) {
      // Now safe to add interactive event handlers
      attachFullEventHandlers(element);
    }
  });
  
  observer.observe({ entryTypes: ['largest-contentful-paint'] });
};

const attachFullEventHandlers = (element) => {
  // Throttled/debounced events for performance
  element.addEventListener('scroll', throttle(handleScroll, 100), { passive: true });
  element.addEventListener('resize', debounce(handleResize, 250), { passive: true });
  element.addEventListener('input', debounce(handleInput, 300));
};

Read the full file on GitHub · 423 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. 2mo ago First seen · 423 lines · 2,966 tokens per session scan A c0be240db405

Subscribe to this mod's changes

event-handling-performance is a cursor rule published in the GitHub repository adobecom/da-express-milo (6 stars, last pushed today), licensed Apache-2.0. It adds 2,966 tokens to every session, about $0.0119 per session on Opus 5.5. 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.

Related

event-handling-performance compared with cursor rules from other repositories

event-handling-performance next to 6 cursor rules from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
event-handling-performanceadobecom/da-express-miloCursor rule6todayApache-2.0A2,966Cursor
ponytailDietrichGebert/ponytailCursor rule189k14d agoMITA604Cursor
angular-20angular/angularCursor rule101ktodayMITA0Cursor
dev-standardapache/supersetCursor rule75ktodayApache-2.0A1,147Cursor
prefer-assertions-over-defensive-checksprisma/ormCursor rule48ktodayApache-2.0A0Cursor
prefer-direct-imports-over-module-mocksprisma/ormCursor rule48ktodayApache-2.0A0Cursor
as-contract-cast-smellprisma/ormCursor rule48ktodayApache-2.0A943Cursor