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-markup-sections-blocksgit 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-markup-sections-blocks)<a href="https://agentmods.dev/rules/adobecom/express-milo/aem-markup-sections-blocks"><img src="https://agentmods.dev/badge/rules/adobecom/express-milo/aem-markup-sections-blocks.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.02448 | $0.02448 |
| Opus 5 | $0.01224 | $0.01224 |
| Sonnet 5 | $0.00490 | $0.00490 |
| Haiku 4.5 | $0.00245 | $0.00245 |
Grade C, and why
aem-markup-sections-blocks scanned grade C with 1 finding 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- Links get classes, some processing begins --> This is a copy
100% identical to aem-markup-sections-blocks — 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.
How it starts
The opening of the file, as written. The whole thing — 309 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AEM Markup, Sections, and Blocks Architecture
APPLY: EVERY QUERY - CRITICAL STRUCTURE RULE
Overview
Based on AEM's markup documentation, our architecture follows a structured approach for content organization and block development that balances author simplicity with developer flexibility.
Document Structure Hierarchy
1. Default Content (Preferred)
Keep as much content as default content as possible - this is the natural authoring experience.
Default content includes:
- Headings (
<h1>-<h6>) - Body text and paragraphs
- Lists (
<ul>,<ol>) - Images with responsive
<picture>tags - Links and emphasis (
<em>,<strong>) - Natural semantic markup
Author Experience: Content creators work with familiar Word/Google Docs semantics without needing to understand blocks.
2. Sections (Layout Grouping)
Purpose: Group content visually (background colors, layout changes)
Section Rules:
- Separated by horizontal rules (
---) in authoring - Contain multiple blocks and/or default content
- Minimal JavaScript interaction beyond CSS styling
- Can include
Section Metadatafor data attributes and styling
Example Section Metadata:
Section Metadata
- Style: dark, wide
- Background: blue
DOM Output:
<div class="section dark wide" data-background="blue">
<!-- section content -->
</div>
3. Blocks (Component Logic)
Purpose: Componentized functionality and styling
Block Architecture:
- Block name = folder name = CSS class = filename
- CSS file:
blockname.css(scoped to.blocknameclass) - JavaScript file:
blockname.js(ESM module with default export) - DOM structure: Nested
<div>tags for rows/columns
Block Development Standards
Block File Structure
blocks/
blockname/
blockname.css
blockname.js
Block JavaScript Pattern (REQUIRED)
// ✅ REQUIRED: Standard block export pattern
export default async function init(el) {
// 1. DOM enhancement first (for LCP)
const basicStructure = createBasicUI(el);
el.append(basicStructure);
// 2. Data fetching second (progressive enhancement)
const data = await fetchData();
enhanceWithData(basicStructure, data);
}
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 · 309 lines · 2,448 tokens per session scan C 5fc5c4aac784
aem-markup-sections-blocks is a cursor rule published in the GitHub repository adobecom/express-milo (6 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 2,448 tokens to every session, about $0.0122 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). It is 100% identical to aem-markup-sections-blocks, 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.
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.