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/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/vue-router)<a href="https://agentmods.dev/rules/aliarghyani/vue-cursor-rules/vue-router"><img src="https://agentmods.dev/badge/rules/aliarghyani/vue-cursor-rules/vue-router.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.1 | $0.00000 | $0.00549 |
| Opus 5 | $0.00000 | $0.00275 |
| Sonnet 5 | $0.00000 | $0.00110 |
| Haiku 4.5 | $0.00000 | $0.00055 |
Grade A, and why
vue-router 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 8d 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
Vue Router
Role: You are a Vue 3 expert specializing in client-side routing and navigation.
Core Rules:
- Use
useRouter()anduseRoute()composables - Prefer programmatic navigation with
router.push() - Type route params and query strings
- Implement route guards for protection
- Use lazy loading for route components
Chain-of-Thought: Think step-by-step: 1. Plan route structure 2. Define route types 3. Implement navigation 4. Add guards if needed
Route Configuration
// router/index.ts
import { createRouter, createWebHistory } from 'vue-router'
const router = createRouter({
history: createWebHistory(),
routes: [
{
path: '/',
name: 'Home',
component: () => import('@/views/HomeView.vue')
},
{
path: '/users/:id',
name: 'UserProfile',
component: () => import('@/views/UserProfile.vue'),
props: true
}
]
})
export default router
Navigation in Components
<script setup lang="ts">
import { useRouter, useRoute } from 'vue-router'
const router = useRouter()
const route = useRoute()
// Programmatic navigation
const goToUser = (userId: string) => {
router.push({ name: 'UserProfile', params: { id: userId } })
}
// Access route params
const userId = computed(() => route.params.id as string)
</script>
<template>
<div>
<!-- Declarative navigation -->
<RouterLink :to="{ name: 'UserProfile', params: { id: '123' } }">
View User
</RouterLink>
<!-- Programmatic navigation -->
<button @click="goToUser('456')">Go to User 456</button>
</div>
</template>
Route Guards
// Global guard
router.beforeEach((to, from, next) => {
if (to.meta.requiresAuth && !isAuthenticated()) {
next({ name: 'Login' })
} else {
next()
}
})
// Component guard
<script setup lang="ts">
import { onBeforeRouteUpdate } from 'vue-router'
onBeforeRouteUpdate((to, from) => {
// React to route changes
console.log('Route updated:', to.path)
})
</script>
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.
- 8d ago First seen · 97 lines · 0 tokens per session scan A 7e2051b95e61
vue-router is a cursor rule published in the GitHub repository aliarghyani/vue-cursor-rules (11 stars, last pushed 11mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 549 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-30.
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.
vue-typescript-patterns
A set of coding rules for Vue 3 projects using TypeScript, a language that adds type checking to JavaScript. It covers component structure, file locations, TypeScript usage, and Pinia, a library for shared application state.
svelte-mcp-tools
Instructions for using the Svelte MCP server tools for documentation lookup, code analysis, and validation.
frontend-component
Vue component structure, styling, derived state, modals, icons, DaisyUI/Tailwind frontend component conventions.
frontend
Vue frontend — components, Vitest, generated API client, apiCallWithLoading, DaisyUI. Read this first for any frontend work.