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-eds-transformation-patternsgit 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-eds-transformation-patterns)<a href="https://agentmods.dev/rules/adobecom/express-milo/aem-eds-transformation-patterns"><img src="https://agentmods.dev/badge/rules/adobecom/express-milo/aem-eds-transformation-patterns.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.1 | $0.00402 | $0.00402 |
| Opus 5 | $0.00201 | $0.00201 |
| Sonnet 5 | $0.00080 | $0.00080 |
| Haiku 4.5 | $0.00040 | $0.00040 |
Grade A, and why
aem-eds-transformation-patterns 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-eds-transformation-patterns — 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 EDS Transformation Patterns
APPLY: Block decoration and performance optimization
Three-Phase Transformation (NEVER bypass)
Raw HTML → Decorated → Loaded
Simple nested divs → data-status="decorated" → data-block-status="loaded"
Users see NOTHING until loaded. body { display: none; } stays until Phase 3.
Block Structure Transformation
<!-- Raw (Phase 1): Author-friendly structure -->
<div class="grid-marquee ratings">
<div><div><h1>Title</h1><p>Content</p></div></div>
<div><div><picture>...</picture></div></div>
</div>
<!-- Loaded (Phase 3): Interactive structure -->
<div class="grid-marquee ratings" data-block-status="loaded">
<div class="background"><picture>...</picture></div>
<div class="foreground">
<div class="headline"><h1>Title</h1><p>Content</p></div>
<div class="cards-container">...</div>
</div>
</div>
Performance Optimization Strategy
Optimize transformation speed, not bypass transformation:
// ✅ Phase E: LCP structure immediately
export default async function init(el) {
const foreground = createTag('div', { class: 'foreground' });
foreground.append(logo, decorateHeadline(headline)); // LCP elements
el.append(foreground);
// ✅ Phase L: Enhancement async
setTimeout(() => enhanceWithCards(), 0);
}
AEM Performance Requirements
Focus on accelerating transformation speed for LCP elements:
/* ✅ Targets final structure */
.grid-marquee .foreground .headline h1 { }
/* ❌ Won't work - raw structure */
.grid-marquee > div > div h1 { }
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 · 59 lines · 402 tokens per session scan A a1288f09abd7
aem-eds-transformation-patterns is a cursor rule published in the GitHub repository adobecom/express-milo (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 402 tokens to every session, about $0.0020 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to aem-eds-transformation-patterns, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.