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/aem-three-phase-performancegit 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/aem-three-phase-performance)<a href="https://agentmods.dev/rules/adobecom/da-express-milo/aem-three-phase-performance"><img src="https://agentmods.dev/badge/rules/adobecom/da-express-milo/aem-three-phase-performance.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.00220 | $0.00220 |
| Opus 5 | $0.00110 | $0.00110 |
| Sonnet 5 | $0.00044 | $0.00044 |
| Haiku 4.5 | $0.00022 | $0.00022 |
Grade A, and why
aem-three-phase-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 3d 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:
- aem-three-phase-performance — 100% identical, 0 lines differ
What it actually says
AEM Three-Phase Loading (E-L-D)
APPLY: EVERY PERFORMANCE QUERY
Phase 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)
- Essential AEM CSS (required for transformations)
- First section only
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
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.
- 3d ago First seen · 32 lines · 220 tokens per session scan A 8ba855f75079
aem-three-phase-performance is a cursor rule published in the GitHub repository adobecom/da-express-milo (6 stars, last pushed 4d ago), licensed Apache-2.0. It adds 220 tokens to every session, about $0.0011 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.
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.