What is stack-detection-webflow?

A set of migration rules for removing Webflow-only traces from a React website. It also covers metadata and image URLs that technology scanners inspect.

Use it when checking the document shell, generator metadata, social-sharing image URLs, and Webflow attributes during a Webflow-to-React migration.

After moving away from Webflow, scanners can still mistake the site for a Webflow site because copied HTML, class names, and URLs remain.

stack-detection-webflow — Cursor rule by dmenchaca

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/dmenchaca/webflow-to-react/stack-detection-webflow

Clone the repo

git clone --depth 1 https://github.com/dmenchaca/webflow-to-react

Per session 0 Nothing until a file matches its globs; then the whole rule loads.

When invoked 598 The whole file, excluding the scripts and references it only reads on demand.

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.

Model	Per session	Once invoked
Fable 5	$0.00000	$0.00598
Opus 5	$0.00000	$0.00299
Sonnet 5	$0.00000	$0.00120
Haiku 4.5	$0.00000	$0.00060

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

Security

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 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.

rules/stack-detection-webflow.mdc · 28 lines

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), not Webflow.
Omit data-wf-page and data-wf-site on <html> unless something in your code or CSS depends on them. They are Webflow editor / publish metadata; exported CSS almost never selects them. Confirm with rg 'data-wf-' web/src/styles before deleting.
Prefer absolute og:image / twitter:image URLs on the production domain (or /images/... on the live origin). URLs on uploads-ssl.webflow.com are 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), and w-mod-ix on documentElement — keep this if copied webflow.css or project CSS uses selectors like html.w-mod-touch or html.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).

Read the full file on GitHub · 28 lines

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.

yesterday First seen · 28 lines · 0 tokens per session scan A 8747b255a411

Subscribe to this mod's changes

stack-detection-webflow is a cursor rule published in the GitHub repository dmenchaca/webflow-to-react (27 stars, last pushed 2mo 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.

Documents Frontend agent-skills storybook tanstack-start vite webflow

stack-detection-webflow