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 wot-ui/wot-starter --skill wot-ui-v2git clone --depth 1 https://github.com/wot-ui/wot-starterWrote 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/wot-ui/wot-starter/wot-ui-v2)<a href="https://agentmods.dev/skills/wot-ui/wot-starter/wot-ui-v2"><img src="https://agentmods.dev/badge/skills/wot-ui/wot-starter/wot-ui-v2/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/wot-ui/wot-starter/wot-ui-v2"><img src="https://agentmods.dev/badge/skills/wot-ui/wot-starter/wot-ui-v2.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.00084 | $0.00802 |
| Opus 5 | $0.00042 | $0.00401 |
| Sonnet 5 | $0.00017 | $0.00160 |
| Haiku 4.5 | $0.00008 | $0.00080 |
Grade A, and why
wot-ui-v2 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 12d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- wot-ui-v2 — 100% identical, 0 lines differ
What it actually says
Wot UI V2 Skill
这个 skill 用于让 Agent 在处理 wot-ui v2 相关任务时，优先采用组件库既有能力、遵守 uni-app 场景限制，并结合本仓库提供的 wot CLI 查询离线知识。
适用场景
- 用户询问某个
wd-*组件的基础用法、属性、事件、插槽或样式变量。 - 需要生成或重构
uni-app + Vue 3 + TypeScript的 wot-ui 页面或组件代码。 - 需要在
ConfigProvider、主题变量、暗黑模式、国际化、反馈类 hooks、表单等场景下给出正确做法。 - 需要排查文档中常见的
Toast、Dialog、Popup、Tabs、Slider、样式覆盖问题。 - 用户只是泛化地提到主题定制，但还没有明确要求按“单文件主题 SCSS + App.vue 只
@use”的结构生成时。
推荐流程
- 先用本仓库 CLI 或 MCP 工具查组件知识。
- 再根据项目实际安装方式决定导入路径与集成方式。
- 优先复用现成的
wd-*组件、hooks、主题变量与组合模式，不要退化成原生标签堆砌。 - 如果问题涉及约束或坑位，再查阅 参考知识。
- 如果用户明确要求生成
src/themes/styles/{主题名}.scss单文件主题，并把挂载逻辑收进主题文件，优先切换到create-wot-ui-themeskill。
查询顺序
wot list找组件名。wot info <Component>看 props、events、slots、CSS 变量。wot demo <Component>看 demo 名称或具体 demo 代码。wot doc <Component>看完整 markdown 文档。wot token <Component>看主题变量。
工作规则
- 默认把 wot-ui 视为
uni-app + Vue 3 + TypeScript组件库。 - 写页面时优先输出
script setup风格。 - 反馈类能力如
useToast、useDialog、useNotify、useImagePreview、useVideoPreview，除了 hook 调用外，通常还需要页面内显式声明对应组件实例。 - 文档里经常出现
@/uni_modules/wot-ui导入路径；如果用户项目采用 npm 安装，应切换成@wot-ui/ui。 - 主题定制优先走
ConfigProvider和 CSS 变量，不优先建议深度覆盖内部类名。 - 生成代码时尽量沿用组件库文档里的命名和交互模式，例如
v-model:visible、before-confirm、confirm、change、custom-class、custom-style。
参考资料
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 47 lines · 84 tokens per session scan A 27deb83f399c
wot-ui-v2 is a skill published in the GitHub repository wot-ui/wot-starter (386 stars, last pushed 14d ago), licensed MIT. It adds 84 tokens to every session and 802 once invoked, about $0.0004 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 skills, from other repositories
nuxt-data-audit
An audit guide for checking how Nuxt projects load data and whether their data-fetching patterns follow the project's performance rules.
nuxt-content
Build typed, content-driven Nuxt applications with @nuxt/content. Use when working with content.config.ts, collections, queryCollection, Markdown or MDC rendering, content databases, hooks, custom sources, search, or Content v2 migrations.
nuxt-modules
Use when creating Nuxt modules: (1) Published npm modules (@nuxtjs/, nuxt-), (2) Local project modules (modules/ directory), (3) Runtime extensions (components, composables, plugins), (4) Server extensions (API routes, middleware), (5) Releasing/publishing modules to npm, (6) Setting up CI/CD workflows for modules.…
vue-expert
Expert knowledge in Vue.js 3, Composition API, Pinia state management, and Nuxt.js for building modern reactive web applications. Use when the user mentions Vue 3, the Composition API, Pinia, Nuxt, reactive, or frontend, or when the task involves Vue 3 Fundamentals, Composition API, Pinia State Management, or Nuxt.js.
review-frontend
Performs a strict code review of the Svelte 5 frontend code (files, diffs, or snippets). Trigger whenever the user shares frontend code (Svelte, TypeScript, CSS) and asks for a review, feedback, or says "review this" — including partial snippets.
use-quail-ui-in-frontend-project
Use this skill when integrating Quail UI into a Vue 3 frontend, migrating an existing screen to Quail UI components, or needing the library's themes, tokens, icons, demo-backed usage patterns, and agent-facing onboarding docs.