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.
git clone --depth 1 https://github.com/oyjt/uniapp-vue3-templateWrote 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/rules/oyjt/uniapp-vue3-template/vue)<a href="https://agentmods.dev/rules/oyjt/uniapp-vue3-template/vue"><img src="https://agentmods.dev/badge/rules/oyjt/uniapp-vue3-template/vue.svg" alt="Measured on agentmods" height="20"></a>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.00000 | $0.00766 |
| Opus 5 | $0.00000 | $0.00383 |
| Sonnet 5 | $0.00000 | $0.00153 |
| Haiku 4.5 | $0.00000 | $0.00077 |
Grade A, and why
vue 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.
What it actually says
Vue 开发规范
- 你是一位前端开发专家，精通 Uniapp、Vue、Pinia、Uview Plus 等前端框架
代码风格
- 组件: 使用单文件组件 (SFC)
- API: 使用组合式 API (Composition API) 并搭配
<script setup>语法糖 - 语法: 没有特殊说明则使用 TS 进行开发
<script setup lang="ts">
命名
- 组件 (Component) 命名: 始终采用单词大写开头 (PascalCase) 的命名方式, 并且避免与 HTML 元素冲突
- 组件 (Component) 命名示例: 以全局的
lang-select组件@/components/lang-select/index.vue和@/components/agree-privacy/index.vue作为参考，注意index是不需要遵循大驼峰格式的 - 页面 (Page) 命名: 始终采用短横线连接 (kebab-case) 的命名方式
- 页面 (Page) 命名示例: 以
home页面作为参考@/pages/tab/home/index.vue - 组合式函数 (Composable) 命名: 始终采用小驼峰 (camelCase) 的命名方式
- 组合式函数 (Composable) 命名示例: 以剪贴板组合式函数作为参考
@/hooks/use-clipboard/index.ts - Props 命名: 在声明 prop 的时候，其命名应该始终采用小驼峰 (camelCase)，而在模板应该始终采用短横线连接 (kebab-case)
- Props 命名示例: 声明时
const { isActive = false } = defineProps<Props>()和传递时<Demo :is-active="true" /> - TS 或 JS 文件命名: 始终采用短横线连接 (kebab-case) 的命名方式
- TS 或 JS 文件命名示例:
@/utils/index.ts
API
- 定义响应式变量时优先使用
ref而非reactive - 复杂的模板表达式则应该重构为计算属性或方法
- 尽量避免侦听器的循坏触发，防止进入死循环
Props
- Prop 定义应该尽量详细，包括类型、必传、默认值
- 如果是使用了 TS 那么应该使用「基于类型的声明」，示例:
const props = defineProps<Props>()
状态管理
- 对应目录:
@/store - 使用 Pinia
- Store 应该按模块划分
- 优先使用 Setup store 语法，而不是 Option Store 语法
- 避免无脑使用全局状态管理
样式
- 优先使用 Scoped CSS，示例:
<style scoped lang="scss"> - 尽可能避免使用
!important - 优先使用 UnoCSS 内联样式
其他
- 避免直接操作 DOM
- 尽可能编写原子化组件
- 使用
v-for时必须提供唯一的key(不要轻易使用数组下标index当做key) - 不要在同一元素上同时使用
v-if和v-for
参考示例文件
@/pages/tab/home/index.vue
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 First seen · 64 lines · 766 tokens per session scan A a6a623623930
vue is a cursor rule published in the GitHub repository oyjt/uniapp-vue3-template (626 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 766 tokens. 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 cursor rules, from other repositories
vue
A set of coding rules for Vue, a JavaScript framework for building web interfaces. It covers component structure, naming, TypeScript usage, reactive data, properties, and routes.
project
A set of project-wide rules for a Vue or TypeScript-style web application, including imports, coding practices, dependency use, linting, and local tool versions. It specifies conventions such as path aliases and supported Node.js and pnpm versions.
index
A set of Chinese-language rules for frontend development, especially Vue 3, Vue Router, Pinia, TypeScript, JavaScript, and Git. It also points to separate project, Vue, TypeScript, and commit-guideline files.
front-form-validation-conventions
YiSmartCloud front-end form validation conventions.
front-vue-page-conventions
YiSmartCloud front-end Vue page conventions.
sveltekit-typescript-guide-cursorrules-prompt-file
Cursor rules for SvelteKit development with TypeScript integration.