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.
git clone --depth 1 https://github.com/adobecom/da-express-miloWrote 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.
[](https://agentmods.dev/rules/adobecom/da-express-milo/event-handling-performance)<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.
<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>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.
| Model | Per session | Once 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 |
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- event-handling-performance — 100% identical, 0 lines differ
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.
- 2mo 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/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.
event-handling-performance compared with cursor rules from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| event-handling-performanceadobecom/da-express-milo | Cursor rule | 6 | today | Apache-2.0 | A | 2,966 | Cursor |
| ponytailDietrichGebert/ponytail | Cursor rule | 189k | 14d ago | MIT | A | 604 | Cursor |
| angular-20angular/angular | Cursor rule | 101k | today | MIT | A | 0 | Cursor |
| dev-standardapache/superset | Cursor rule | 75k | today | Apache-2.0 | A | 1,147 | Cursor |
| prefer-assertions-over-defensive-checksprisma/orm | Cursor rule | 48k | today | Apache-2.0 | A | 0 | Cursor |
| prefer-direct-imports-over-module-mocksprisma/orm | Cursor rule | 48k | today | Apache-2.0 | A | 0 | Cursor |
| as-contract-cast-smellprisma/orm | Cursor rule | 48k | today | Apache-2.0 | A | 943 | Cursor |