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 cloud-appsgit 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/cloud-apps)<a href="https://agentmods.dev/skills/webflow/webflow-skills/cloud-apps"><img src="https://agentmods.dev/badge/skills/webflow/webflow-skills/cloud-apps/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/cloud-apps"><img src="https://agentmods.dev/badge/skills/webflow/webflow-skills/cloud-apps.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 37 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00116 | $0.04824 |
| Opus 5.5 | $0.00046 | $0.01930 |
| Sonnet 5.5 | $0.00023 | $0.00965 |
| Haiku 4.5 | $0.00012 | $0.00482 |
Grade A, and why
webflow-mcp:cloud-apps 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 3d 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 — 401 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Webflow Cloud Apps
Use data_apps_tool to create GitHub-source apps, answer operational questions,
and manage environments for Webflow Cloud apps. Start from the user's outcome,
gather only the evidence needed, and distinguish observations from conclusions.
Use the webflow-cli:cloud skill when the task requires CLI/local-source app
creation or deployment, or creating or updating environment variables.
Client-side build output is not sent to Webflow and cannot be recovered through
MCP.
Instructions
1. Establish scope
Use the Webflow MCP connection established by the user's request or existing task context. If only one connection is active, use it without asking the user to choose or reconfirm a region. If multiple connections are active and the intended target remains ambiguous, ask the user to disambiguate before proceeding with target-dependent operations. Do not switch regions to recover from missing resources or access errors.
Before handing an existing MCP app or environment to the CLI for configuration writes or deployment, compare their configured regions. If they differ, do not assume either is correct or silently retarget either tool. Resolve the intended target from explicit task context; if that does not resolve the conflict, ask the user. Pause dependent mutations until the conflict is resolved.
Once the intended region is established, verify that the CLI can read the exact MCP app and environment IDs, and carry that region and those IDs explicitly into subsequent mutations. Login status or a region label alone is insufficient. If verification fails, report the failure without inferring its cause and pause dependent mutations. Continue independent work whose target is established.
- Call
webflow_guide_toolbefore any other Webflow MCP tool. The live guide and action schemas are authoritative for current arguments and responses. - Use Webflow MCP tools for Webflow operations except the explicit CLI handoff for environment-variable values. Never call Webflow APIs directly.
- Include the required
contextparameter in every tool call. Write 15-25 words in third-person perspective. - Route by the capability the task requires:
- Use
data_apps_toolto create GitHub-source apps; inspect apps, environments, domains, deployment records, logs, and variable metadata; manage GitHub sources and environments; and enqueue GitHub deployments. - Use
data_variable_toolfor Designer color, size, font, and CSS variables. - Use
webflow-cli:cloudfor CLI/local-source apps, local builds and deployments, or creating and updating environment-variable values.
- Use
- If
data_apps_toolis unavailable, report that the Cloud Apps MCP capability is not enabled. Do not bypass it with a direct API request.
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.
- 3d ago Changed · +6 lines 2aec66a89f84
- 1mo ago First seen · 395 lines · 116 tokens per session scan A 64f2a29cbef1
webflow-mcp:cloud-apps is a skill published in the GitHub repository webflow/webflow-skills (132 stars, last pushed today), licensed MIT. It adds 116 tokens to every session and 4,824 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
terraform-skill
Use when working with Terraform or OpenTofu - creating modules, writing tests (native test framework, Terratest), setting up CI/CD pipelines, reviewing configurations, choosing between testing approaches, debugging state issues, implementing security scanning (trivy, checkov), or making infrastructure-as-code…
terraform-cli-setup
A setup guide for installing and initializing Terraform, a tool for managing infrastructure from configuration files. It also covers basic provider downloads and mirror settings, but not cloud-provider credentials.
alicloud_cli
A Chinese-language reference for the Alibaba Cloud command-line tool, which lets developers manage Alibaba Cloud services from a terminal. It uses an offline copy of the documentation as its main source.
deploy
A deployment workflow for putting Rails applications online using Railway, a hosting service.
oss-upload
Upload local files to Tencent COS (oss.1024code.com CDN) using coscli. Use when user wants to upload a file to CDN/OSS, or deploy static assets.
aws-advisor
Expert AWS Cloud Advisor for architecture design, security review, and implementation guidance. Leverages AWS MCP tools for accurate, documentation-backed answers. Use when user asks about AWS architecture, security, service selection, migrations, troubleshooting, or learning AWS. Triggers on AWS, Lambda, S3, EC2…