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/wingify/wingify-fme-mcpWrote 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/wingify/wingify-fme-mcp/statsig-to-wingify-migration-mcp-rules)<a href="https://agentmods.dev/rules/wingify/wingify-fme-mcp/statsig-to-wingify-migration-mcp-rules"><img src="https://agentmods.dev/badge/rules/wingify/wingify-fme-mcp/statsig-to-wingify-migration-mcp-rules/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/wingify/wingify-fme-mcp/statsig-to-wingify-migration-mcp-rules"><img src="https://agentmods.dev/badge/rules/wingify/wingify-fme-mcp/statsig-to-wingify-migration-mcp-rules.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.09026 | $0.09026 |
| Opus 5 | $0.04513 | $0.04513 |
| Sonnet 5 | $0.01805 | $0.01805 |
| Haiku 4.5 | $0.00903 | $0.00903 |
Grade A, and why
statsig-to-wingify-migration-mcp-rules 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 10d 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 — 572 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🔁 Cursor/VS Code IDE Rule: Migrate Statsig to Wingify FE
🎯 Purpose
Guide the assistant through migrating Statsig entities (feature gates, dynamic configs, experiments, segments, and metrics) into Wingify FE using the Wingify FE MCP server tools.
📋 Scope
- Source: Statsig Console API
- Target: Wingify FE (via the Wingify FE MCP server).
- Entities in scope: feature gates, dynamic configs, experiments, parameter stores, segments, metrics
Application SDK migration (replacing Statsig SDK imports/calls in source code) is documented separately in
ide-rules/statsig-to-wingify-sdk-migration.mdcandskills/wingify-fe-mcp/statsig-sdk-migration.md. Run console migration first so flag keys match.
⛔ Non-negotiables (apply to every model, every run)
- Deterministic — The migration MUST produce the same result no matter which model runs it. It is driven by the MCP tools and the mapping tables below; follow them literally and never invent flags, rules, variations, or names.
- No new rule files in the client's repo — Do NOT create
.cursor/rules/*.mdc,.github/instructions/*.md, or any other rule file in the user's repo as part of migration, and do NOT callAddWingifyRulesduring a migration. - Precise naming from Statsig — Names/keys of new variables, variations, and rules come precisely from the source Statsig config (
name→id/baseID→ positional index only if both absent). Never add random strings (UUIDs, hashes, timestamps) or invented labels likeVariation 2/Rollout 1. Keys are sanitized to[a-zA-Z0-9_]; display names keep the original Statsig string. - Wingify SDKs only (every language, no exceptions) — Any SDK wiring that follows must, for all languages, install the verified Wingify-branded package from
sdkNpmPackageMapand construct a Wingify-based client (e.g.wingifyClient); never install avwo/vwo-fme-*package or create avwo/VWO-based client. Supported SDK list (source of truth): https://developers.wingify.com/v3/docs/list-of-fme-sdks.
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.
- 10d ago First seen · 572 lines · 9,026 tokens per session scan A 0908ae6419ad
statsig-to-wingify-migration-mcp-rules is a cursor rule published in the GitHub repository wingify/wingify-fme-mcp (3 stars, last pushed 20d ago), licensed Apache-2.0. It adds 9,026 tokens to every session, about $0.0451 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.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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-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.