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.
git clone --depth 1 https://github.com/TheSethRose/DevRulesWrote 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/thesethrose/devrules/vue3)<a href="https://agentmods.dev/rules/thesethrose/devrules/vue3"><img src="https://agentmods.dev/badge/rules/thesethrose/devrules/vue3/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/thesethrose/devrules/vue3"><img src="https://agentmods.dev/badge/rules/thesethrose/devrules/vue3.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.01068 |
| Opus 5.5 | $0.00000 | $0.00427 |
| Sonnet 5.5 | $0.00000 | $0.00214 |
| Haiku 4.5 | $0.00000 | $0.00107 |
Grade A, and why
Vue3 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 1mo 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vue.js 3 Best Practices
Core Principles
- Declarative Rendering: Use Vue's template syntax to declaratively bind the DOM to the underlying component state.
- Reactivity: Leverage Vue's reactivity system. Understand how changes to reactive state automatically update the DOM.
- Component-Based: Build interfaces by composing small, reusable components.
API Styles (Options vs. Composition)
- Understand Both: Be familiar with both Options API and Composition API. Choose based on project needs, team preference, or complexity.
- Options API: Organizes code by options (
data,methods,computed,watch, lifecycle hooks). Good for simpler components or class-based mental models. - Composition API: Organizes code by logical concern using imported functions (
ref,reactive,computed,watch, lifecycle hooks). Excellent for logic reuse (Composables) and managing complex components. Often used with<script setup>.
- Options API: Organizes code by options (
- Consistency: Maintain consistency in the chosen API style within a project or team if possible.
Single-File Components (SFCs - .vue files)
- Structure: Use SFCs to encapsulate template (
<template>), logic (<script>or<script setup>), and styles (<style>) in one file. <script setup>: Prefer<script setup>when using Composition API for reduced boilerplate and better TypeScript inference.- Scoped Styles: Use
<style scoped>to limit CSS rules to the current component, preventing global scope pollution.
Component Design
- Keep Components Focused: Design components with a single, clear responsibility.
- Props for Input: Pass data down from parent to child components using
props. Define props clearly with types and validation. - Events for Output: Emit events (
$emit) from child components to communicate changes or actions back to the parent. - Slots for Content Distribution: Use
slotsto allow parent components to pass template fragments into child components, enhancing flexibility and composition. - Provide/Inject: Use
provideandinjectfor dependency injection, especially for deeply nested components, but use with caution as it makes components less explicitly coupled.
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.
- 1mo ago First seen · 61 lines · 1,068 tokens per session scan A 9ea531425d1a
Vue3 is a cursor rule published in the GitHub repository TheSethRose/DevRules (26 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,068 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-09-03.
Other cursor rules, from other repositories
svelte-5-vs-svelte-4-cursorrules-prompt-file
Cursor rules for comparing Svelte 5 and Svelte 4 development.
sveltekit-typescript-guide-cursorrules-prompt-file
Cursor rules for SvelteKit development with TypeScript integration.
javascript-astro-tailwind-css-cursorrules-prompt-f
Cursor rules for JavaScript development with Astro and Tailwind CSS integration.
sveltekit-tailwindcss-typescript-cursorrules-promp
Cursor rules for SvelteKit development with Tailwind CSS and TypeScript integration.
sveltekit-restful-api-tailwind-css-cursorrules-pro
Cursor rules for SvelteKit development with RESTful API and Tailwind CSS integration.
svelte
Svelte best practices and patterns for modern web applications.