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.
git clone --depth 1 https://github.com/dmenchaca/webflow-to-reactWrote 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/dmenchaca/webflow-to-react/webflow-css-preservation)<a href="https://agentmods.dev/rules/dmenchaca/webflow-to-react/webflow-css-preservation"><img src="https://agentmods.dev/badge/rules/dmenchaca/webflow-to-react/webflow-css-preservation/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/dmenchaca/webflow-to-react/webflow-css-preservation"><img src="https://agentmods.dev/badge/rules/dmenchaca/webflow-to-react/webflow-css-preservation.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.00585 |
| Opus 5.5 | $0.00000 | $0.00234 |
| Sonnet 5.5 | $0.00000 | $0.00117 |
| Haiku 4.5 | $0.00000 | $0.00059 |
Grade A, and why
webflow-css-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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 34 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Preserve Webflow's CSS and class names
This project migrated from a Webflow HTML export. The fastest path to pixel parity is to keep Webflow's compiled CSS and class names verbatim and only refactor later, section by section.
Do
- Put Webflow class names on JSX verbatim (
className="hero-section_wrapper", underscores and all). - Keep the compiled Webflow CSS split under
src/styles/marketing/(normalize.css,layout-components.css,<brand>.css, etc.). marketing.css@importorder:site-fonts.cssfirst, then normalize/layout/compiled<brand>.webflow.css, then anyglobal-embed.css(or similar) copied fromindex.html<style>blocks. Embeds usually define.hideand must load after the site bundle — otherwise hidden Designer nodes become visible. See gotchas.md § Designer-hidden nodes:.hideand stylesheet order.- Rewrite asset URLs in copied CSS to root-relative:
url("/images/..."),url("/fonts/..."). - When in doubt, diff against the root-level
index.html(Webflow reference — read-only).
Don't
- Don't translate Webflow breakpoints (479 / 767 / 991 px) to Tailwind screens while migrating. Leave the media queries inside the copied CSS.
- Don't rename class names "to be cleaner" — it breaks parity and makes diffing against the reference impossible.
- Don't start converting to Tailwind utilities across many sections at once. One section at a time, only after parity is confirmed.
- Don't delete unused-looking rules from the compiled CSS during migration; Webflow CSS often cross-references many class combos.
- Don't assume
html-react-parser/ raw HTML preserves behavior — only structure and styles.webflow.js, IX2, andw-*component JS still need a port or replacement. See gotchas.md § Rawhtml-react-parserand § Webflowwebflow.jsbehaviors.
Progressive refactor path (post-parity)
- Confirm pixel parity on all breakpoints.
- Pick one section. Replace its JSX classes with Tailwind utilities.
- Move any still-needed custom CSS into a section-scoped class.
- Delete the now-dead rules from the compiled CSS.
- Repeat.
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.
- 1mo ago First seen · 34 lines · 0 tokens per session scan A 72a7327e7182
webflow-css-preservation is a cursor rule published in the GitHub repository dmenchaca/webflow-to-react (28 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 585 tokens. 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-30.
Other cursor rules, from other repositories
external-scale
Source: docs/agents/external-scale.md Regenerate: npm run agents:sync -w packages/openbridge-webcomponents -->.
codex-premium-website-skills
Apply Codex Skills standards to frontend, website, motion, accessibility, QA, agent reasoning, and handoff work.
ui-components
USE WHEN: Building UI components, structuring layouts, and applying styles using Tailwind CSS.
ui-components
USE WHEN: Building UI components, structuring layouts, and applying styles using Tailwind CSS.
ui-motion-workflow
Orchestrate motion-aware UI work by sequencing direction, provider choice, implementation, and browser validation.
mobile-first-ui
Mobile-first UI for settings, dialogs, and lists — smaller type, stacked layouts, nested add dialogs.