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/adobecom/express-milo/event-handling-performancegit clone --depth 1 https://github.com/adobecom/express-miloWhat 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.02966 | $0.02966 |
| Opus 5 | $0.01483 | $0.01483 |
| Sonnet 5 | $0.00593 | $0.00593 |
| Haiku 4.5 | $0.00297 | $0.00297 |
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 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.
This is a copy
100% identical to event-handling-performance — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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));
};
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.
- 2d ago First seen · 423 lines · 2,966 tokens per session scan A c0be240db405
event-handling-performance is a cursor rule published in the GitHub repository adobecom/express-milo (6 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 2,966 tokens to every session, about $0.0148 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to event-handling-performance, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.