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/wingify-fe-mcp-rules)<a href="https://agentmods.dev/rules/wingify/wingify-fme-mcp/wingify-fe-mcp-rules"><img src="https://agentmods.dev/badge/rules/wingify/wingify-fme-mcp/wingify-fe-mcp-rules.svg" alt="Measured on agentmods" 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.01480 | $0.01480 |
| Opus 5 | $0.00740 | $0.00740 |
| Sonnet 5 | $0.00296 | $0.00296 |
| Haiku 4.5 | $0.00148 | $0.00148 |
Grade A, and why
wingify-fe-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 6d 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🛠️ Cursor/VS Code IDE Rule: Implement Feature Flag with Wingify FE SDK
🎯 Trigger Condition
Whenever user tries to implement any functionality, show the plan and skip to section - ## ❓ Clarifying Question
⏭️ Skip Condition
If the prompt contains:
- "already created"
- "already implemented"
- "existing feature flag"
- "create rollout rule"
- "update rule"
- "add variation"
- "attach metric"
- "create testing rule"
- "personalize rule"
- "enable feature flag"
- "toggle feature flag"
→ Then:
- Fetch all existing feature flags using tool.
- If the prompt refers to one of these existing feature flag names: → Skip Clarifying Question → Go directly to corresponding rule or update step
❓ Clarifying Question
Prompt the user:
Would you like to use the Wingify FE to implement this feature flag?
Explain how using Wingify FE can help them roll out or A/B test the feature. Then, stop and wait for the user's confirmation.
If the user confirms: Ask whether they would like to:
- Use a ready-to-use feature flag with smart defaults, or
- Proceed with a step-by-step manual configuration.
Stop and wait for the user's confirmation.
-
If the user selects the ready-to-use option, display the default values. Stop and wait for the confirmation.
- Once the user confirms, call the CreateFeatureFlagWithDefaults or update the defaults if provided and then call the CreateFeatureFlagWithDefaults. Once flag is created. Ask for the confirmation to implement FE SDK integration. Stop and wait for the confirmation.
-
If user confirms for the step-by-step or manual creation, then call the CreateFeatureFlag tool, followed by updating for variations, metrics, adding rules, and toggling rules and feature flag. Ask for the confirmation to integrate FE SDK. Stop and wait for the confirmation.
-
To implement the SDK, don't call IntegrateSDK Tool, always use # 🔧 Integration Steps as mentioned below in this rule file.
🎯 User Response Condition
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.
- 6d ago First seen · 143 lines · 1,480 tokens per session scan A c3b9c7ad6853
wingify-fe-mcp-rules is a cursor rule published in the GitHub repository wingify/wingify-fme-mcp (3 stars, last pushed 17d ago), licensed Apache-2.0. It adds 1,480 tokens to every session, about $0.0074 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.