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/stack-detection-webflow)<a href="https://agentmods.dev/rules/dmenchaca/webflow-to-react/stack-detection-webflow"><img src="https://agentmods.dev/badge/rules/dmenchaca/webflow-to-react/stack-detection-webflow/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/stack-detection-webflow"><img src="https://agentmods.dev/badge/rules/dmenchaca/webflow-to-react/stack-detection-webflow.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.00598 |
| Opus 5.5 | $0.00000 | $0.00239 |
| Sonnet 5.5 | $0.00000 | $0.00120 |
| Haiku 4.5 | $0.00000 | $0.00060 |
Grade A, and why
stack-detection-webflow 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 — 28 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Webflow stack detection (document shell)
Tools like Wappalyzer infer technology from HTML, URLs, and class names — not from who actually hosts the site. After migration, the React app may still look like Webflow to scanners if you copy the export shell verbatim.
Do (low risk, do during root shell port)
- Set
<meta name="generator">to something accurate (e.g.Vite + React + TanStack Start), notWebflow. - Omit
data-wf-pageanddata-wf-siteon<html>unless something in your code or CSS depends on them. They are Webflow editor / publish metadata; exported CSS almost never selects them. Confirm withrg 'data-wf-' web/src/stylesbefore deleting. - Prefer absolute
og:image/twitter:imageURLs on the production domain (or/images/...on the live origin). URLs onuploads-ssl.webflow.comare a strong third-party fingerprint.
Keep when CSS still needs it
- The export’s inline init that adds
w-mod-js,w-mod-touch(on touch devices), andw-mod-ixondocumentElement— keep this if copiedwebflow.cssor project CSS uses selectors likehtml.w-mod-touchorhtml.w-mod-js:not(.w-mod-ix) …. Removing it without replacing those rules breaks layout or IX fallbacks. w-*classes (w-embed,w-nav, …) on body markup — required for visual parity with compiled Webflow CSS. Many scanners will still mention Webflow; that is expected until a later markup/CSS refactor.
Expectations
- Pixel-parity migrations intentionally ship Webflow-shaped CSS and classes. Some tools will still report “Webflow” even when the app is TanStack + Netlify. That is not the same as the site being published from Webflow Hosting.
- Full removal of Webflow signals requires rehosting assets, renaming classes, and replacing or pruning
webflow.css— out of scope for day-one parity; treat as a follow-up project.
See gotchas.md § Stack detection (Wappalyzer, BuiltWith).
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 · 28 lines · 0 tokens per session scan A 8747b255a411
stack-detection-webflow is a cursor rule published in the GitHub repository dmenchaca/webflow-to-react (27 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 598 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
vue
A set of coding rules for Vue, a JavaScript framework for building web interfaces. It covers component structure, naming, TypeScript usage, reactive data, properties, and routes.
project
A set of project-wide rules for a Vue or TypeScript-style web application, including imports, coding practices, dependency use, linting, and local tool versions. It specifies conventions such as path aliases and supported Node.js and pnpm versions.
index
A set of Chinese-language rules for frontend development, especially Vue 3, Vue Router, Pinia, TypeScript, JavaScript, and Git. It also points to separate project, Vue, TypeScript, and commit-guideline files.
core-principles
USE WHEN: Applying core principles and enforcing global project constraints.
api
USE WHEN: Defining HTTP requests, endpoints, and handling API responses.
tanstack-query
USE WHEN: Managing server state, fetching data, and handling mutations with TanStack Query.