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 review-commentsgit 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/review-comments)<a href="https://agentmods.dev/skills/webflow/webflow-skills/review-comments"><img src="https://agentmods.dev/badge/skills/webflow/webflow-skills/review-comments/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/review-comments"><img src="https://agentmods.dev/badge/skills/webflow/webflow-skills/review-comments.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.00023 | $0.02258 |
| Opus 5.5 | $0.00009 | $0.00903 |
| Sonnet 5.5 | $0.00005 | $0.00452 |
| Haiku 4.5 | $0.00002 | $0.00226 |
Grade A, and why
webflow-mcp:review-comments 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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review open comment threads on a Webflow site and triage each one.
Input: $ARGUMENTS — a site name (e.g. "Workhaus"), site ID (e.g. 6808fd4eff835ee3af009d6f), or either with the -reply flag (e.g. Workhaus -reply).
Flags:
-reply— in addition to writing the report, post a bot reply to each non-open thread. Without this flag, the skill runs in report-only mode (read-only).
Parse $ARGUMENTS at the start: strip -reply from the input to get the site identifier, and set replyMode = true if -reply was present, false otherwise.
Step 1 — Resolve the site
If the site identifier is empty or blank — cross-site comment survey
- Call
data_sites_tool > list_sitesto get all sites. Page through until all are collected. - For each site, call
data_comments_tool > list_comment_threadswithisResolved: falseandlimit: 100. Page through until all unresolved threads are collected. If the API does not supportisResolvedfiltering, fetch all threads and filter client-side toisResolved === false. Process sites in batches of 20 (batch multiple actions in a single tool call). After each batch completes, log a progress line:Batch {N}/{total} done (sites {start}–{end}): {summary of findings, e.g. "all 0 threads" or "SiteName has X threads, rest 0"}. - For each site, compute:
unresolvedCount= total unresolved threadsnewestDate= the maximumlastUpdatedvalue across all unresolved threads for that site (ISO → human-readable date, e.g. "Apr 3, 2026"). If no threads, show—.oldestDate= the minimumlastUpdatedvalue across all unresolved threads for that site (ISO → human-readable date). If no threads, show—.
- Sort sites by
unresolvedCountdescending. Take the top 10. - Above the table, show a heading line:
### Checked {totalSiteCount} sites — {sitesWithUnresolved} have unresolved comments. - Display a table in this format (link just the site name to
https://webflow.com/design/{siteId}):
| Site | Unresolved Comments | Newest / Oldest |
|------|---------------------|-----------------|
| [Site Name](https://webflow.com/design/{siteId}) ({siteId}) | {N} | {newestDate} / {oldestDate} |
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 · 180 lines · 23 tokens per session scan A 512589b6eb9d
webflow-mcp:review-comments is a skill published in the GitHub repository webflow/webflow-skills (130 stars, last pushed 4d ago), licensed MIT. It adds 23 tokens to every session and 2,258 once invoked, about $0.0001 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
yida-agent-center
An agent-management tool for Yida, a business workflow platform. It manages temporary substitutes who handle or submit approval processes for current employees or departed employees.
yida-voc
A template for organising user feedback (VOC, or voice of the customer) about problems, requests, and performance issues in the Yida platform.
product-planner
Plan a product from idea to sprint tasks in one run: idea-validator, prd-generator, tad-generator, tasks-generator, resuming from existing files. Don't use for one document alone (PRD, TAD, tasks) or only validating an idea.
yida-prd
A planning guide that turns confirmed user needs into a product requirements document, or PRD—a written description of what an application should contain and do.
yida-flow-node-config
A reference guide for configuring nodes in workflow and integration automation. It covers triggers, human tasks, routing, data changes, notifications, and extension steps without creating or publishing the workflow.
yida-requirement-analysis
A requirements-gathering guide that records confirmed user needs and existing Yida resources in a structured brief before design or implementation begins.