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/da-express-milo/lazy-loading-implementationgit clone --depth 1 https://github.com/adobecom/da-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.02427 | $0.02427 |
| Opus 5 | $0.01213 | $0.01213 |
| Sonnet 5 | $0.00485 | $0.00485 |
| Haiku 4.5 | $0.00243 | $0.00243 |
Grade A, and why
lazy-loading-implementation 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- lazy-loading-implementation — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 359 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lazy Loading Performance Rules - Three-Phase Strategy
APPLY: EVERY QUERY - CRITICAL PERFORMANCE RULE
AEM Three-Phase Loading Implementation (REQUIRED)
Based on AEM's performance guidelines:
Phase Assignment Strategy
Phase E (Eager): First section only, LCP candidates, under 100kb total
Phase L (Lazy): Below-fold blocks, same-origin enhancements
Phase D (Delayed): Third-party content, 3+ seconds after LCP
Phase E - Critical Section Only (REQUIRED)
NEVER lazy load the first section - it contains LCP candidates
// ✅ REQUIRED - First section loads immediately (Phase E)
export default async function init(element) {
const isFirstSection = element.closest('.section') === document.querySelector('.section');
if (isFirstSection) {
// Critical path - load immediately for LCP
loadBlock(element);
} else {
// Below-fold - use Phase L lazy loading
createIntersectionObserver({
el: element,
options: { rootMargin: '200px' },
callback: loadBlock,
});
}
}
Phase L - IntersectionObserver Pattern (REQUIRED)
ALL non-critical blocks MUST use lazy loading following utils.js:
// ✅ REQUIRED - Standard Phase L lazy loading
export default async function init(element) {
// Check for override (testing purposes)
if (element.textContent.includes('no-lazy')) {
loadBlock(element);
return;
}
// Phase L: Lazy load with appropriate rootMargin
const blockType = element.classList[0];
const rootMargin = getOptimalRootMargin(blockType);
createIntersectionObserver({
el: element,
options: { rootMargin },
callback: () => loadBlock(element),
});
}
// Optimize loading distance based on block importance
function getOptimalRootMargin(blockType) {
const criticalBlocks = ['marquee', 'hero', 'cards'];
const heavyBlocks = ['video', 'carousel', 'interactive'];
if (criticalBlocks.includes(blockType)) return '300px'; // Load earlier
if (heavyBlocks.includes(blockType)) return '100px'; // Load closer
return '200px'; // Default
}
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 · 359 lines · 2,427 tokens per session scan A ed480040d54a
lazy-loading-implementation is a cursor rule published in the GitHub repository adobecom/da-express-milo (6 stars, last pushed 2d ago), licensed Apache-2.0. It adds 2,427 tokens to every session, about $0.0121 per session on Opus 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.
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.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.