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/aem-franklin-loading-phasesgit clone --depth 1 https://github.com/adobecom/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/express-milo/aem-franklin-loading-phases)<a href="https://agentmods.dev/rules/adobecom/express-milo/aem-franklin-loading-phases"><img src="https://agentmods.dev/badge/rules/adobecom/express-milo/aem-franklin-loading-phases.svg" alt="Measured on agentmods" 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 | $0.00435 | $0.00435 |
| Opus 5 | $0.00217 | $0.00217 |
| Sonnet 5 | $0.00087 | $0.00087 |
| Haiku 4.5 | $0.00044 | $0.00044 |
Grade A, and why
aem-franklin-loading-phases 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 5d 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 aem-franklin-loading-phases — 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.
What it actually says
AEM Franklin Loading Phases & Performance
APPLY: EVERY PERFORMANCE QUERY
AEM/Franklin Loading Phases (CRITICAL ARCHITECTURE)
- Raw HTML Phase: Franklin EDS delivers undecorated HTML structure
- Decoration Phase: Blocks receive
data-status="decorated"- components start decorating - Loaded Phase: Final
data-block-status="loaded"- all interactions ready
Performance wins happen in phases 1-2, not phase 3
Three-Phase Loading (E-L-D) Assignment
Phase E (Eager): LCP elements, <100KB, single origin
Phase L (Lazy): Below-fold, same-origin enhancement
Phase D (Delayed): Third-party, 3+ seconds after LCP
Phase E Budget Rules
- 100KB total before LCP
- Single origin only (no CDNs, fonts, APIs)
- First section only
Block Performance Pattern (Hero-Marquee Style)
// ✅ LCP structure first, heavy operations deferred to Promise.all
export default async function init(el) {
// Create LCP DOM immediately - no heavy operations
const foreground = document.createElement('div');
foreground.appendChild(headline); // LCP element here
el.appendChild(foreground);
// Defer heavy operations to Promise.all like hero-marquee
const promiseArr = [];
promiseArr.push(cardProcessing());
promiseArr.push(ratingsAPI());
await Promise.all(promiseArr);
}
Implementation Pattern
// ✅ Phase E: LCP structure immediately
export default async function init(el) {
const isFirstSection = el.closest('.section') === document.querySelector('.section');
if (isFirstSection) {
// Phase E: Create LCP DOM immediately - no async blocking
createLCPStructure(el);
} else {
// Phase L: Lazy load with intersection observer
setupLazyLoading(el);
}
}
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.
- 5d ago First seen · 55 lines · 435 tokens per session scan A cc6ffec4e818
aem-franklin-loading-phases is a cursor rule published in the GitHub repository adobecom/express-milo (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 435 tokens to every session, about $0.0022 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to aem-franklin-loading-phases, 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.
family-instance-domain-actions
Family instance domain action implementation patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.