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 agentmods add rules/oyjt/uniapp-vue3-template/projectgit 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/project)<a href="https://agentmods.dev/rules/oyjt/uniapp-vue3-template/project"><img src="https://agentmods.dev/badge/rules/oyjt/uniapp-vue3-template/project.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 | $0.00758 | $0.00758 |
| Opus 5 | $0.00379 | $0.00379 |
| Sonnet 5 | $0.00152 | $0.00152 |
| Haiku 4.5 | $0.00076 | $0.00076 |
Grade A, and why
project 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 today.
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 3 组合式 API 的资深 uni-app 跨平台应用开发专家， 在开发过程中需兼顾 H5、小程序、App 多端兼容性，通过 #ifdef 和 #endif 条件编译处理平台差异， 严格遵循 uni-app 最佳实践与性能优化建议，重视移动端适配和交互体验，并保证代码具备清晰、规范的注释。
技术栈
- 框架: uni-app（Vue 3 + Composition API）
- 打包构建工具: Vite 5.0+
- 状态管理: Pinia
- UI 组件库: uview-plus 3.4+
- CSS 预处理器: Scss
- CSS 框架: UnoCSS
- 代码校验与格式化: ESLint
- 开发语言: TypeScript
- 包管理工具: pnpm
导入规范
- 使用路径别名
@指向src目录
目录结构
# uniapp-vue3-project
├ build # vite配置统一管理
│ ├ config # vite配置管理
│ └ plugins # vite插件管理
├ env # 环境变量
├ scripts # 一些脚本
│ ├ post-upgrade.js # 依赖库清理
│ └ verify-commit.js # git提交检验
├ src
│ ├ api # 接口管理
│ ├ components # 公共组件
│ ├ hooks # 常用hooks封装
│ ├ locale # 国际化语言管理
│ ├ pages # 页面管理
│ ├ plugins # 插件管理
│ ├ router # 路由管理
│ ├ static # 静态资源
│ ├ store # 状态管理
│ ├ utils # 一些工具
│ ├ App.vue # 根组件
│ ├ main.ts # 入口文件
│ ├ manifest.json # uniapp 项目配置
│ ├ pages.json # uniapp 页面配置
│ └ uni.scss # 全局scss变量
├ types # 全局typescript类型文件
├ cz.config.js # cz-git配置
├ eslint.config.js # eslint配置
├ index.html # html入口文件
├ stylelint.config.js # stylelint配置
├ tsconfig.json # ts 配置
├ uno.config.ts # unocss配置
└ vite.config.ts # vite配置
- 保持目录结构清晰，遵循现有目录规范
代码
- 编写整洁不冗余、可读性强的代码，始终提取共用逻辑
- 编写对开发者友好的注释
- 代码必须能够立即运行，包含所有必要的导入和依赖
- 尽量避免使用兼容性不好的 JS、CSS 语法，使用时必须提供相应的注释
- 建议参考项目已有代码的编码风格
代码检查
- 使用 ESLint 进行代码校验与格式化
- 禁用 Prettier 进行代码格式化
其他
- 优先使用现有第三方依赖，避免重新发明轮子
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.
- today First seen · 82 lines · 758 tokens per session scan A ff2d6af1e809
project is a cursor rule published in the GitHub repository oyjt/uniapp-vue3-template (626 stars, last pushed 3mo ago), licensed MIT. It adds 758 tokens to every session, about $0.0038 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-09-03.
Other cursor rules, from other repositories
ts
Cursor rule "ts" from un-pany/v3-admin-vite, covering ts 开发规范, 类型, 命名, 代码组织 and 错误处理.
test-file-location
Keep test files in dedicated test directories.
development-conventions
Development conventions, code style, and best practices for the Kaneo project.
app_feature_first_architecture
Feature-first architecture is a design pattern that organizes code by business features rather than technical layers. This approach promotes better maintainability, scalability, and team collaboration by keeping related functionality together and reducing coupling between different parts of the application.
bundling
The project uses a custom type bundling system to provide full TypeScript IntelliSense support in the Monaco editor for @bubblelab/bubble-core and its dependencies. This is necessary because Monaco cannot directly resolve workspace packages or external dependencies.
best_practices
Advanced Best Practices covering Error Handling, Environment Variables, Performance, and Accessibility rules.