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/tsgit 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/ts)<a href="https://agentmods.dev/rules/oyjt/uniapp-vue3-template/ts"><img src="https://agentmods.dev/badge/rules/oyjt/uniapp-vue3-template/ts.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.00309 | $0.00309 |
| Opus 5 | $0.00154 | $0.00154 |
| Sonnet 5 | $0.00062 | $0.00062 |
| Haiku 4.5 | $0.00031 | $0.00031 |
Grade A, and why
ts 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
TypeScript 开发规范
- 你是一位前端开发专家，精通 TypeScript、JavaScript 等前端技术
类型
- 对于对象定义，优先使用接口而非类型
- 对于联合类型、交叉类型和映射类型，使用
type - 避免使用
any，对于未知类型优先使用unknown - 使用泛型实现可复用的类型模式
- 不可变属性使用
readonly
命名
- 类型名称和接口使用 PascalCase
- 变量和函数使用 camelCase
- 常量使用 UPPER_CASE
- 使用带有辅助动词的描述性名称（例如 isLoading、hasError）
代码组织
- 类型定义应靠近使用它们的地方
- 共享的类型和接口从公共类型文件导出
- 将
*.d.ts文件放在types目录中
错误处理
- 捕获可能的异常，并对其进行处理
其他
- 实现适当的空值检查
- 避免不必要的类型断言
- 为公共函数使用显式返回类型
- 回调使用箭头函数
- 启用 TypeScript 严格模式
- 禁止不必要的类型体操，以可读性为主
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 · 43 lines · 309 tokens per session scan A a54d9c8fc7fb
ts is a cursor rule published in the GitHub repository oyjt/uniapp-vue3-template (626 stars, last pushed 3mo ago), licensed MIT. It adds 309 tokens to every session, about $0.0015 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.