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/e-gov/cursor-prompts/nuxt-conventionsgit clone --depth 1 https://github.com/e-gov/cursor-promptsWrote 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/e-gov/cursor-prompts/nuxt-conventions)<a href="https://agentmods.dev/rules/e-gov/cursor-prompts/nuxt-conventions"><img src="https://agentmods.dev/badge/rules/e-gov/cursor-prompts/nuxt-conventions.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.08507 | $0.08507 |
| Opus 5 | $0.04254 | $0.04254 |
| Sonnet 5 | $0.01701 | $0.01701 |
| Haiku 4.5 | $0.00851 | $0.00851 |
Grade A, and why
nuxt-conventions 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.
How it starts
The opening of the file, as written. The whole thing — 1,032 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Nuxt Development Conventions
Context
- Apply this rule when developing Nuxt applications
- This rule complements
typescript-common/application-logging.mdcandtypescript-common/audit-logging.mdcfor logging - For TypeScript code standards, see
typescript-common/typescript-code-standards.mdc - For comprehensive security best practices, see
rules/common/security.mdc - Follow Vue style guide and Nuxt best practices
- Convention over Configuration: Adhere to Nuxt 4 conventions to simplify development and collaboration
Requirements
1. Project Structure
- Feature-based organization: Group related components, composables, and stores by feature
- Shared components: Create shared components for common functionality
- Lazy loading: Implement lazy loading for route components
- Directory Structure: Co-locate related files:
. ├── app/ # Nuxt 4 uses app/ directory │ ├── assets/ # Assets processed by build tools (CSS, images, fonts) │ ├── components/ │ │ ├── [feature-name]/ │ │ │ └── FeatureComponent.vue │ │ └── MyComponent.vue │ ├── composables/ │ │ └── useUser.ts │ ├── layouts/ │ │ └── default.vue │ ├── middleware/ # Route middleware │ │ └── auth.ts │ ├── pages/ # File-based routing │ │ ├── [feature-name]/ │ │ │ └── feature-page.vue │ │ └── index.vue │ ├── plugins/ │ │ └── analytics.ts │ ├── store/ │ │ └── user-store.ts │ ├── utils/ # Utility functions │ │ └── formatDate.ts │ ├── app.config.ts # Reactive configuration (optional, no secrets!) │ ├── app.vue # Root application component (optional) │ └── error.vue # Error page (optional) ├── modules/ # Custom Nuxt modules ├── public/ # Static assets (images, fonts) ├── server/ # API routes and server-side logic │ ├── api/ │ ├── routes/ │ └── middleware/ └── test/ # Mirror app/ structure for test files ├── unit/ ├── integration/ └── e2e/
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 · 1,032 lines · 8,507 tokens per session scan A da6ccf2b3668
nuxt-conventions is a cursor rule published in the GitHub repository e-gov/cursor-prompts (34 stars, last pushed 4mo ago), licensed MIT. It adds 8,507 tokens to every session, about $0.0425 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.