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.
npx agentmods add instructions/wingify/wingify-fme-mcp/agents-mdgit 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/instructions/wingify/wingify-fme-mcp/agents-md)<a href="https://agentmods.dev/instructions/wingify/wingify-fme-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/wingify/wingify-fme-mcp/agents-md.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.01451 | $0.01451 |
| Opus 5 | $0.00726 | $0.00726 |
| Sonnet 5 | $0.00290 | $0.00290 |
| Haiku 4.5 | $0.00145 | $0.00145 |
Grade A, and why
wingify-fme-mcp AGENTS.md 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 5d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Guidance for any AI agent working in this repo, in any IDE (Cursor, VS Code, Claude,
CLI, etc.). This is the cross-IDE source of truth; keep it in sync with the shipped
ide-rules/ and skills/wingify-fe-mcp/ guidance.
Migration policy (model- and IDE-independent)
These three rules are binding for any migration this server drives (Statsig console
entities and application SDK code), no matter which model or IDE is running. Encode them
in tool outputs and shipped ide-rules/; never leave them to model discretion.
1. Deterministic across models
- A migration MUST produce the same result no matter which model or IDE runs it.
- Follow the mapping tables and package names in
ide-rules/andskills/wingify-fe-mcp/literally. Do not improvise flag keys, rule/variation names, variable types, or import styles. - Never invent entities, rules, or names. Missing name → fall back to the documented id/key. If a case is not covered, ask instead of guessing.
2. Never create rule files in the client's repo during migration
- During migration flows, do not write
.cursor/rules/*.mdc,.github/instructions/*.md,AGENTS.md, or any other rule/instructions file into the user's / client's repo, and do not callAddWingifyRulesas part of migration. - Drive consistency from MCP tool outputs and the repo guides instead.
- (The standalone
AddWingifyRulestool, called explicitly by the user outside a migration, is unaffected.)
3. Precise naming from the original Statsig configuration
- Names and keys of new variables, variations, and rules MUST be derived precisely
from the source Statsig config. Never add random strings (no UUIDs, hashes,
timestamps, or invented labels like
Variation 2/Rollout 1). - Ordered priority for every name/key: Statsig
name→ Statsigid/baseID→ (only when both are absent) a stable positional index. Sanitize keys to[a-zA-Z0-9_]; the human-readable name keeps the original Statsig string. - Variables keep their exact Statsig parameter key. Experiment/config variations keep their group/variant name (or id). Rules keep their Statsig rule name (or id).
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.
- 5d ago First seen · 88 lines · 1,451 tokens per session scan A aa036453f6e2
wingify-fme-mcp AGENTS.md is an instructions file published in the GitHub repository wingify/wingify-fme-mcp (3 stars, last pushed 16d ago), licensed Apache-2.0. It adds 1,451 tokens to every session, about $0.0073 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).