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/express-milo-performance-diagnosisgit 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/express-milo-performance-diagnosis)<a href="https://agentmods.dev/rules/adobecom/express-milo/express-milo-performance-diagnosis"><img src="https://agentmods.dev/badge/rules/adobecom/express-milo/express-milo-performance-diagnosis.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.00466 | $0.00466 |
| Opus 5 | $0.00233 | $0.00233 |
| Sonnet 5 | $0.00093 | $0.00093 |
| Haiku 4.5 | $0.00047 | $0.00047 |
Grade A, and why
express-milo-performance-diagnosis 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 express-milo-performance-diagnosis — 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
Express-Milo Performance Diagnosis
APPLY: PageSpeed < 90 queries
Performance Issue Decision Tree
User: "PageSpeed score 75, H1 LCP 5+ seconds"
├─ LCP > 3s + white screen pattern?
│ └─ YES → CSS render-blocking (27KB styles.css via JavaScript)
├─ Font loading issue?
│ └─ NO → Removing typekit has no impact
└─ SOLUTION → Optimize AEM loading phases for LCP elements
User: "Need to bypass body { display: none; }"
└─ NO → Optimize AEM EDS transformation speed, not bypass
Root Cause: CSS Render-Blocking in scripts.js
// ❌ PROBLEM: 27KB CSS blocks body visibility for 5+ seconds
(function loadStyles() {
const link = document.createElement('link');
link.setAttribute('rel', 'stylesheet');
link.setAttribute('href', path); // BLOCKS until download complete
document.head.appendChild(link);
}());
AEM EDS Transformation Requirements
Raw HTML → Decorated → Loaded (3 phases, users see NONE until loaded)
- H1 exists in raw HTML but needs final DOM structure CSS
body { display: none; }required untildata-block-status="loaded"- Focus on accelerating transformation speed for LCP elements
Solution Pattern
// ✅ SOLUTION: Follow hero-marquee pattern for LCP optimization
export default async function init(el) {
// Phase 1: Create LCP structure immediately (synchronous DOM)
const basicStructure = createLCPStructure(el);
el.append(basicStructure);
// Phase 2: Defer heavy operations to Promise.all
const dataPromises = Promise.all([
fetchCards(),
fetchRatings() // Don't block LCP with API calls
]);
// Phase 3: Enhance with data after LCP
const data = await dataPromises;
enhanceWithData(basicStructure, data);
}
Expected: LCP 5s → 1.5s, PageSpeed 75 → 98
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 · 61 lines · 466 tokens per session scan A 29f2a87d7cf4
express-milo-performance-diagnosis is a cursor rule published in the GitHub repository adobecom/express-milo (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 466 tokens to every session, about $0.0023 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to express-milo-performance-diagnosis, 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-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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.