css-optimization

A CSS editing rule for replacing repeated values with existing CSS variables only when the values match exactly and the variable has a suitable meaning.

In plain words
What is it for?
Use it when optimising CSS variable usage, including checking font sizes and other values against variables already defined in styles.css.
Why use it?
It prevents unsafe substitutions, such as using a spacing variable for a font size, while making matching styles easier to maintain.

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/da-express-milo/css-optimization
Clone the repo
git clone --depth 1 https://github.com/adobecom/da-express-milo

Made for: Cursor.

Per session 111 This file is loaded in full into every session.
When invoked 111 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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.00111 $0.00111
Opus 5 $0.00056 $0.00056
Sonnet 5 $0.00022 $0.00022
Haiku 4.5 $0.00011 $0.00011

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

Security

Grade A, and why

css-optimization 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 yesterday.

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

Copies of this mod

1 near-identical copy found in the catalogue:

.cursor/rules/css-optimization.mdc · 16 lines

What it actually says

CSS Update Query

When the user asks to optimize variable usage of their files, look at the CSS values that do not use vars. Reference styles.css for existing vars that match the value EXACTLY and ensure that the var name and the value are semantically similar. For example, do not use a spacing variable for font sizes and vice versa. Be sure to check font sizes.

CRITICAL

Do not replace values with variables unless the value matches the varaible EXACTLY.


description: globs: alwaysApply: true

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. yesterday First seen · 16 lines · 111 tokens per session scan A fb8075770d88

Subscribe to this mod's changes

css-optimization is a cursor rule published in the GitHub repository adobecom/da-express-milo (6 stars, last pushed 2d ago), licensed Apache-2.0. It adds 111 tokens to every session, about $0.0006 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.