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/project-structuregit 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/project-structure)<a href="https://agentmods.dev/rules/aliarghyani/vue-cursor-rules/project-structure"><img src="https://agentmods.dev/badge/rules/aliarghyani/vue-cursor-rules/project-structure.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.00007 | $0.00565 |
| Opus 5 | $0.00003 | $0.00282 |
| Sonnet 5 | $0.00001 | $0.00113 |
| Haiku 4.5 | $0.00001 | $0.00056 |
Grade A, and why
project-structure 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.
What it actually says
Project Structure
Role: You are a Vue 3 expert specializing in scalable project architecture and organization.
Core Rules:
- Follow feature-based directory structure
- Use barrel exports for clean imports
- Maintain consistent naming conventions
- Separate concerns (components, composables, stores)
- Keep related files together
Chain-of-Thought: Think step-by-step: 1. Identify feature boundaries 2. Organize by domain 3. Setup clean import paths 4. Maintain consistency
Recommended Directory Structure
src/
├── components/ # Reusable UI components
│ ├── ui/ # Base UI components (Button, Input, etc.)
│ └── features/ # Feature-specific components
├── views/ # Page components
├── composables/ # Reusable composition functions
├── stores/ # Pinia stores
├── router/ # Vue Router configuration
├── services/ # API services and external integrations
├── types/ # TypeScript type definitions
├── utils/ # Utility functions
├── assets/ # Static assets (images, styles)
└── main.ts # Application entry point
Component Organization
components/
├── ui/
│ ├── Button.vue
│ ├── Input.vue
│ ├── Modal.vue
│ └── index.ts # Export barrel
├── features/
│ ├── UserProfile/
│ │ ├── UserProfile.vue
│ │ ├── UserAvatar.vue
│ │ └── index.ts
│ └── ProductCard/
│ ├── ProductCard.vue
│ ├── ProductImage.vue
│ └── index.ts
Naming Conventions
- Components: PascalCase (
UserProfile.vue) - Views: PascalCase with View suffix (
HomeView.vue) - Composables: camelCase with use prefix (
useUserData.ts) - Stores: camelCase with Store suffix (
userStore.ts) - Types: PascalCase for interfaces (
User,ApiResponse) - Files: kebab-case for utilities (
api-client.ts)
Import/Export Patterns
// components/ui/index.ts - Barrel exports
export { default as Button } from './Button.vue'
export { default as Input } from './Input.vue'
export { default as Modal } from './Modal.vue'
// In components
import { Button, Input } from '@/components/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 · 76 lines · 7 tokens per session scan A 93f0dba2fe94
project-structure is a cursor rule published in the GitHub repository aliarghyani/vue-cursor-rules (11 stars, last pushed 11mo ago), licensed MIT. It adds 7 tokens to every session and 565 once invoked, about $0.0000 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.