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 liuyanghejerry/Clausura --skill vue-best-practicesgit clone --depth 1 https://github.com/liuyanghejerry/ClausuraWrote 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/liuyanghejerry/clausura/vue-best-practices)<a href="https://agentmods.dev/skills/liuyanghejerry/clausura/vue-best-practices"><img src="https://agentmods.dev/badge/skills/liuyanghejerry/clausura/vue-best-practices/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/liuyanghejerry/clausura/vue-best-practices"><img src="https://agentmods.dev/badge/skills/liuyanghejerry/clausura/vue-best-practices.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.00031 | $0.00383 |
| Opus 5.5 | $0.00012 | $0.00153 |
| Sonnet 5.5 | $0.00006 | $0.00077 |
| Haiku 4.5 | $0.00003 | $0.00038 |
Grade A, and why
vue-best-practices 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.
What it actually says
Vue 代码规范审查
审查 Vue 组件（.vue 文件）中违反最佳实践的模式。
检查清单
组件命名
- 组件名未使用 PascalCase 或多词命名（Vue 官方风格指南要求）
- rule_id:
vue-component-name - severity:
warning
Props 校验
- Props 未声明 type 或 validator
- rule_id:
vue-missing-prop-validation - severity:
warning
避免 as any
- TypeScript 中使用
as any绕过类型检查 - rule_id:
no-as-any - severity:
warning
Options API vs Composition API
- 同一组件中混用 Options API 和 Composition API（
<script setup>中不应出现data()、methods:） - rule_id:
vue-mixed-api-style - severity:
info
模板中的复杂表达式
<template>中包含超过一行的 JavaScript 表达式（应提取为 computed）- rule_id:
vue-complex-template - severity:
info
输出格式
{
"rule_id": "no-as-any",
"severity": "warning",
"message": "在 PaymentForm.vue 中发现 as any 类型断言",
"evidence": "const data = response as any",
"location": { "file": "src/components/PaymentForm.vue", "line_start": 42, "line_end": 42, "column_start": 13, "column_end": 35 }
}
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 · 48 lines · 31 tokens per session scan A 6cc15c441e87
vue-best-practices is a skill published in the GitHub repository liuyanghejerry/Clausura (204 stars, last pushed 28d ago), licensed MIT. It adds 31 tokens to every session and 383 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
setup-pre-commit
Use when bootstrapping or extending the pre-commit hook chain (Husky + lint-staged + Prettier + typecheck + integration tests) for an EVOKORE-style TypeScript repo, including detecting an existing setup, surfacing the diff, and never silently overwriting a configured chain.
quality-gate
Use when you need to check if current work meets quality thresholds before proceeding to the next phase or merging.
pull-request-feedback-loop
Handles PR review feedback by fetching comments, grouping issues, fixing one group at a time, and verifying before replies.
claude-c-suite-cto
Use for architecture, tech debt, refactoring, dependency, scaling, migration, and codebase health reviews.
claude-c-suite-dx-lead
Use for developer experience, API ergonomics, SDK usability, docs quality, onboarding, and error-message reviews.
claude-c-suite-audit
Use when auditing or release-checking the Claude C-Suite plugin's own command conformance.