dom-structure-preservation

dom-structure-preservation is a cursor rule for Cursor from adobecom/express-milo. It costs 1,919 tokens per session, scanned A, a copy of dom-structure-preservation, Apache-2.0.

A rule that requires performance changes to leave a webpage's existing HTML structure exactly as it is.

In plain words
What is it for?
Use it when refactoring or speeding up blocks while preserving the same elements, order, classes, attributes, text, and nesting.
Why use it?
It prevents optimizations from breaking CSS selectors, visual appearance, automated tests, or production behavior that depend on the current markup.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/adobecom/express-milo/dom-structure-preservation
Clone the repo
git clone --depth 1 https://github.com/adobecom/express-milo

Made for: Cursor.

Wrote 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.

agentmods badge for dom-structure-preservation

README.md
[![agentmods](https://agentmods.dev/badge/rules/adobecom/express-milo/dom-structure-preservation.svg)](https://agentmods.dev/rules/adobecom/express-milo/dom-structure-preservation)
Your own site
<a href="https://agentmods.dev/rules/adobecom/express-milo/dom-structure-preservation"><img src="https://agentmods.dev/badge/rules/adobecom/express-milo/dom-structure-preservation.svg" alt="Measured on agentmods" height="20"></a>
Per session 1,919 This file is loaded in full into every session.
When invoked 1,919 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.01919 $0.01919
Opus 5 $0.00959 $0.00959
Sonnet 5 $0.00384 $0.00384
Haiku 4.5 $0.00192 $0.00192

Measured 3d ago against content hash c3a3d9068113, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

dom-structure-preservation 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.

Origin

This is a copy

100% identical to dom-structure-preservation — 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.

.cursor/rules/dom-structure-preservation.mdc · 233 lines

How it starts

The opening of the file, as written. The whole thing — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.

DOM Structure Preservation Rule - Three-Phase Compatible

APPLY: EVERY QUERY - CRITICAL PERFORMANCE RULE

CRITICAL: Never Break Existing DOM Structure

When refactoring, optimizing, or improving block code, you MUST preserve the exact same DOM output. This is non-negotiable and applies across all phases of the AEM Three-Phase Loading strategy.

⚠️ ABSOLUTE REQUIREMENT: IDENTICAL MARKUP POST-OPTIMIZATION

The markup that is present today MUST be present after any performance optimizations. Class names, DOM order, element types, attributes, text content - EVERYTHING must be identical.

This means:

  • Same CSS works without modification
  • Same visual appearance with zero changes
  • Same DOM inspector view when development is complete
  • Same element hierarchy and nesting structure
  • Same class names and attribute values
  • Same text content and innerHTML structure

Why This Matters

  • Thousands of pages are QA tested and business approved
  • Existing CSS relies on specific selectors and class names
  • Production sites depend on current DOM structure
  • Breaking changes affect live customer experiences

✅ ALLOWED Performance Optimizations (All Phases)

// ✅ GOOD - Phase E: Simple initial structure for LCP
const basicStructure = createTag('div', { class: 'hero' });
el.append(basicStructure); // Same final DOM as before

// ✅ GOOD - Phase L: Progressive enhancement maintaining final structure
setTimeout(() => {
  const enhancement = createTag('div', { class: 'hero-overlay' });
  basicStructure.append(enhancement); // Identical to non-optimized version
}, 0);

// ✅ GOOD - Internal batching without DOM changes
const promises = items.map(processItem);
await Promise.all(promises);

// ✅ GOOD - Event listener optimization keeping same behavior
element.addEventListener('click', handler, { passive: true });

// ✅ GOOD - Lazy loading that produces identical final DOM
const observer = new IntersectionObserver(loadContent);

// ✅ GOOD - requestAnimationFrame for internal state management
requestAnimationFrame(() => updateInternalState());

// ✅ GOOD - Phase D: Delayed third-party content
setTimeout(() => {
  addAnalyticsPixel(); // Same DOM structure as before
}, 3000);

Read the full file on GitHub · 233 lines

Changes

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.

  1. 3d ago First seen · 233 lines · 1,919 tokens per session scan A c3a3d9068113

Subscribe to this mod's changes

dom-structure-preservation is a cursor rule published in the GitHub repository adobecom/express-milo (6 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 1,919 tokens to every session, about $0.0096 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to dom-structure-preservation, differing in 0 lines, and is treated as a copy.