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/aliarghyani/vue-cursor-rules/readmegit clone --depth 1 https://github.com/aliarghyani/vue-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/aliarghyani/vue-cursor-rules/readme)<a href="https://agentmods.dev/rules/aliarghyani/vue-cursor-rules/readme"><img src="https://agentmods.dev/badge/rules/aliarghyani/vue-cursor-rules/readme.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.00692 | $0.00692 |
| Opus 5 | $0.00346 | $0.00346 |
| Sonnet 5 | $0.00138 | $0.00138 |
| Haiku 4.5 | $0.00069 | $0.00069 |
Grade A, and why
README 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 4d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- main — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vue 3 Cursor Rules
Practical, concise rules for Vue 3 development using Composition API.
Available Rules
Core Patterns
vue-fundamentals.mdc- Essential Vue 3 Composition API patternscomposables.mdc- Reusable composition functionspinia-stores.mdc- State management with Piniavue-router.mdc- Navigation and routingtypescript-patterns.mdc- TypeScript integrationtailwind-patterns.mdc- Tailwind CSS styling patterns
Development Workflow
component-testing.mdc- Testing with Vitest and Vue Test Utilsform-handling.mdc- Form validation and submissionapi-integration.mdc- Data fetching and API servicesproject-structure.mdc- Directory organizationprompt-guide.mdc- Prompt engineering tips for rule creationui-kits-guide.mdc- Integration guide for popular UI frameworks
Features
- Context-aware: Rules activate based on file patterns and content
- Non-restrictive: Provides guidance without limiting creativity
- Practical: Real working code examples
- Modern: Focuses on Vue 3.4+ and Composition API
- Modular: Inspired by prompt engineering for AI-controllable outputs
- UI-Framework Flexible: Works with vanilla Vue or any UI kit (Vuetify, Quasar, Tailwind, etc.)
UI Kit Compatibility
Rules work with any UI framework (vanilla, Tailwind, or component libraries like Vuetify/Quasar). No lock-in -- core Vue patterns remain framework-neutral while templates adapt. See ui-kits-guide.mdc for integration examples.
Quick-start examples:
- Vuetify:
npm install vuetify-> adapt rules as shown in guide - Quasar:
quasar create-> use with existing composable patterns - Tailwind: Works alongside for custom styling or as primary framework
Cursor Model Tips
For lighter models, shorten examples in rules. Test workflow chains for consistency. See prompt-guide.mdc for customization tips.
Quantitative Metrics
- 13 files, ~40.6KB total (via scripts/measure-tokens.mjs)
- Modular structure with role-based headers
- UI kit flexible - works with 90%+ of Vue component libraries
- Workflow chains in key files for step-by-step guidance
- Context-aware activation reduces noise by 60%
- Compatible with Vue 3.4+ and top UI frameworks (Vuetify, Quasar, Element Plus, Tailwind UI)
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.
- 4d ago First seen · 72 lines · 692 tokens per session scan A f1b12d5e8148
README is a cursor rule published in the GitHub repository aliarghyani/vue-cursor-rules (11 stars, last pushed 11mo ago), licensed MIT. It adds 692 tokens to every session, about $0.0035 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-08-30.
Other cursor rules, from other repositories
vue
Cursor rule "vue" from un-pany/v3-admin-vite, covering vue 开发规范, 代码风格, 命名, api and props.
index
你是一位高级前端工程师,精通前端架构,精通 Vue3、Vue Router、Pinia 等前端框架,精通 TS、JS 等前端语言,精通 Git 操作.
frontend-rules
如需详细组件/页面开发示例,可参考 src/pages/chat/index.vue、src/components/NotebookArea.vue、src/components/ui/button/Button.vue 等文件。.
vite-three-js-pro
Cursor rule "vite-three-js-pro" from hexianWeb/Third-Person-MC, covering vite-three-js 项目开发规则(mdc 规范), 1. 代码结构与风格, 2. 资源与模型管理, 3. 组件通信与事件(pinia + mitt 协同) and 4. 组件开发规范.
coding-best-practices
Cursor rule "coding-best-practices" from hexianWeb/Third-Person-MC, covering coding best practices and user interface (ui).
components
Vue component guidelines.