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/pinia-stores)<a href="https://agentmods.dev/rules/aliarghyani/vue-cursor-rules/pinia-stores"><img src="https://agentmods.dev/badge/rules/aliarghyani/vue-cursor-rules/pinia-stores.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.00536 |
| Opus 5 | $0.00000 | $0.00268 |
| Sonnet 5 | $0.00000 | $0.00107 |
| Haiku 4.5 | $0.00000 | $0.00054 |
Grade A, and why
pinia-stores 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 7d 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
Pinia Stores
Role: You are a Vue 3 expert specializing in global state management with Pinia.
Core Rules:
- Use Composition API syntax with
defineStore - Return readonly state to prevent direct mutations
- Keep actions simple and focused
- Use getters for computed values
- Handle loading and error states consistently
Chain-of-Thought: Think step-by-step: 1. Design store interface 2. Define reactive state 3. Create getters/computed 4. Implement actions
Basic Store Pattern
// stores/user.ts
import { defineStore } from 'pinia'
import { ref, computed } from 'vue'
export const useUserStore = defineStore('user', () => {
// State
const user = ref<User | null>(null)
const loading = ref(false)
// Getters
const isLoggedIn = computed(() => !!user.value)
const userName = computed(() => user.value?.name ?? 'Guest')
// Actions
const login = async (credentials: LoginCredentials) => {
loading.value = true
try {
const response = await authApi.login(credentials)
user.value = response.user
} finally {
loading.value = false
}
}
const logout = () => {
user.value = null
}
return {
// State (readonly)
user: readonly(user),
loading: readonly(loading),
// Getters
isLoggedIn,
userName,
// Actions
login,
logout
}
})
Using Stores in Components
<script setup lang="ts">
import { useUserStore } from '@/stores/user'
const userStore = useUserStore()
const handleLogin = async () => {
await userStore.login({ email, password })
}
</script>
<template>
<div>
<p v-if="userStore.isLoggedIn">
Welcome, {{ userStore.userName }}!
</p>
<button v-else @click="handleLogin" :disabled="userStore.loading">
Login
</button>
</div>
</template>
Store Best Practices
- Use Composition API syntax with
defineStore - Return readonly state to prevent direct mutations
- Keep actions simple and focused
- Use getters for computed values
- Handle loading and error states
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.
- 7d ago First seen · 97 lines · 0 tokens per session scan A 5ebbcb4e154a
pinia-stores 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 536 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.