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 skills add webflow/webflow-skills --skill flowkit-naminggit clone --depth 1 https://github.com/webflow/webflow-skillsWrote 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/skills/webflow/webflow-skills/flowkit-naming)<a href="https://agentmods.dev/skills/webflow/webflow-skills/flowkit-naming"><img src="https://agentmods.dev/badge/skills/webflow/webflow-skills/flowkit-naming/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/skills/webflow/webflow-skills/flowkit-naming"><img src="https://agentmods.dev/badge/skills/webflow/webflow-skills/flowkit-naming.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00081 | $0.07173 |
| Opus 5.5 | $0.00032 | $0.02869 |
| Sonnet 5.5 | $0.00016 | $0.01435 |
| Haiku 4.5 | $0.00008 | $0.00717 |
Grade A, and why
webflow-mcp:flowkit-naming 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 — 946 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flowkit Naming System
Apply FlowKit CSS naming conventions in Webflow projects using Webflow Designer tools.
Important Note
ALWAYS use Webflow MCP tools for all operations:
- Use Webflow MCP's
webflow_guide_toolto get best practices before starting - Use Webflow MCP's
data_sites_toolwith actionlist_sitesto identify the target site - Use Webflow MCP's
data_pages_toolwith actionlist_pagesto find the target page by name or slug — headless, no Designer needed - Use Webflow MCP's
data_element_toolto inspect current classes and apply new ones — headless, pass the page's ID directly - Use Webflow MCP's
data_style_toolto create and update FlowKit-compliant styles — headless - Use Webflow MCP's
webflow_guide_toolto understand supported style properties - Use Webflow MCP's
designer_toolonly if the user wants to work with whatever page is currently open in Designer, or wants to interactively select an element on the canvas - DO NOT use any other tools or methods for Webflow operations
- All tool calls must include the required
contextparameter (15-25 words, third-person perspective) - No Designer connection is required for the core workflow. Getting the page, inspecting classes, creating styles, and applying classes all run headlessly against an explicit page ID. Designer is only needed for the optional
designer_toolconveniences above.
Instructions
Phase 1: Discovery & Setup
- Identify the task: Determine if user is:
- Creating new component classes
- Auditing existing class names
- Building complete page sections
- Refactoring non-FlowKit classes to FlowKit
- Get target page: Use Webflow MCP's
data_pages_toolwith actionlist_pagesto find the page by name or slug — no Designer connection needed. If the user wants to work with whatever page they currently have open in Designer, usedesigner_toolwith actionget_current_pageinstead. - Ask for scope: Clarify which elements or sections to work with
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 · 946 lines · 81 tokens per session scan A 154997c3ab23
webflow-mcp:flowkit-naming is a skill published in the GitHub repository webflow/webflow-skills (130 stars, last pushed 4d ago), licensed MIT. It adds 81 tokens to every session and 7,173 once invoked, about $0.0003 per session on Opus 5.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-30.
Other skills, from other repositories
web-design-engineer
Build or redesign polished browser-rendered visual artifacts with HTML/CSS/JavaScript/React: pages, dashboards, prototypes, slide decks, animations, UI mockups, and data visualizations. Use for visual front-end creation, design-system exploration, design critique, or explicit browser acceptance / QA of a web artifact.…
yida-data-manage-ui
A method for improving the appearance and usability of Yida data-management pages, while keeping their data, permissions, queries, and business actions unchanged. Yida is a platform for building business applications.
frontend-blueprint
AI frontend specialist and design consultant that guides users through a structured discovery process before generating any code. Collects visual references, design tokens, typography, icons, layout preferences, and brand guidelines to ensure the final output matches the user's vision with high fidelity. Use when the…
ardot-style-guide
A design-system workflow for choosing and applying colors, fonts, spacing, and page layouts in Ardot projects.
design-optimizer
Optimize a website or app design in one run: capture the page once, audit usability, UX/AX, virality and agent readiness, merge overlaps into one prioritized report, apply fixes on opt-in. Don't use for one lens (dont-make-me-think, ux-ax-review).
cf-design
UI design workflow — scan patterns, design new UI, or modify UI consistently. Use to redesign a component/page, change colors/typography/style, or extract the design system. Triggers: "make it look like", "update the styling", "redesign this", "match the existing style", "add a dark mode", "make it more minimal".