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/cmnemoi/cursor-rules/3-vuejs-3git clone --depth 1 https://github.com/cmnemoi/cursor-rulesWrote 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/cmnemoi/cursor-rules/3-vuejs-3)<a href="https://agentmods.dev/rules/cmnemoi/cursor-rules/3-vuejs-3"><img src="https://agentmods.dev/badge/rules/cmnemoi/cursor-rules/3-vuejs-3.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.00000 | $0.00538 |
| Opus 5 | $0.00000 | $0.00269 |
| Sonnet 5 | $0.00000 | $0.00108 |
| Haiku 4.5 | $0.00000 | $0.00054 |
Grade A, and why
3-vuejs@3 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
Component Structure:
- Use Composition API for new components.
- Keep components focused on a single responsibility.
- Extract reusable logic into composables.
- Strongly type component props with
defineProps<{...}>(). - Provide default values with
withDefaults(). - Use
<script setup>for simpler component definitions. - Use Options API exclusively.
Reactivity:
- Use
ref()for primitive values. - Use
reactive()for object values. - Prefer
computed()over methods for derived state. - Use
watch()andwatchEffect()sparingly. - Extract complex reactive logic into composables.
- Avoid direct mutation of props.
- Use
toRefs()when destructuring reactive objects.
State Management:
- Use a global state management library.
- Create stores based on domains, not components.
- Implement dependency injection for service access.
- Define store interfaces for better testability.
- Keep component state local when possible.
- Use
provide/injectfor deep component trees. - Avoid direct store imports in components.
Templates:
- Use
v-bindshorthand (:prop) for dynamic props. - Use
v-onshorthand (@event) for event handlers. - Avoid complex expressions in templates.
- Extract complex logic to computed properties.
- Use template refs instead of querying DOM.
- Implement slots for component composition.
- Use teleport for modals and popups.
Performance:
- Apply
v-memofor expensive renders. - Use
v-oncefor static content. - Implement
defineAsyncComponent()for code splitting. - Add
v-prefor non-reactive content. - Use
shallowRef()for large objects with no deep reactivity. - Apply
markRaw()for non-reactive objects. - Implement virtual scrolling for large lists.
Ports & Adapters:
- Define service interfaces in
typesdirectory. - Implement concrete services in
servicesdirectory. - Use dependency injection for service access.
- Mock services in tests with interfaces.
- Extract API calls from components and stores.
- Create repository pattern for data access.
- Separate domain models from API responses.
Testing:
- Unit test composables and stores independently.
- Mock external dependencies in unit tests.
- Use test utils for component testing.
- Test slots and render functions.
- Use snapshot tests for visual components.
- Test error boundaries and fallbacks.
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 · 68 lines · 538 tokens per session scan A 256ffdcd23b1
3-vuejs@3 is a cursor rule published in the GitHub repository cmnemoi/cursor-rules (2 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 538 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-08-31.
Other cursor rules, from other repositories
tailwind-v4
Standards for Tailwind CSS v4 usage in Svelte files.
vue-typescript-patterns
Cursor rule "vue-typescript-patterns" from soaring-xiongkulu/easyaiot, covering vue3 + typescript 开发规范, vue 组件规范, vue sfc 组件规范, typescript 规范 and 状态管理.
vue
Cursor rule "vue" from un-pany/v3-admin-vite, covering vue 开发规范, 代码风格, 命名, api and props.
index
你是一位高级前端工程师,精通前端架构,精通 Vue3、Vue Router、Pinia 等前端框架,精通 TS、JS 等前端语言,精通 Git 操作.
svelte-mcp-tools
Instructions for using the Svelte MCP server tools for documentation lookup, code analysis, and validation.
svelte
You are an expert in Svelte 5, SvelteKit, TypeScript, and modern web development.