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/bravew/trove/trove-vuegit clone --depth 1 https://github.com/bravew/troveWrote 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/bravew/trove/trove-vue)<a href="https://agentmods.dev/rules/bravew/trove/trove-vue"><img src="https://agentmods.dev/badge/rules/bravew/trove/trove-vue.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.00000 | $0.00624 |
| Opus 5 | $0.00000 | $0.00312 |
| Sonnet 5 | $0.00000 | $0.00125 |
| Haiku 4.5 | $0.00000 | $0.00062 |
Grade A, and why
trove-vue 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 5d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Trove · v2026.7.4
Session Init
This skill ships Trove conventions. Prefer existing project patterns over generic best practices when they conflict.
Vue 3 Composition API Conventions
Script Setup
Always use <script setup lang="ts"> for single-file components:
<script setup lang="ts">
import { ref, computed, onMounted } from 'vue'
const count = ref(0)
const doubled = computed(() => count.value * 2)
onMounted(() => {
console.log('Component mounted')
})
</script>
Reactivity (CRITICAL)
- Use
ref()for primitives,reactive()for objects - Always access
.valueon refs in script (auto-unwrapped in template) - Use
computed()for derived state — never compute in template - Use
watchEffect()for side effects that depend on reactive state
// BAD — reactive object loses reactivity on destructure
const { name, age } = reactive(user)
// GOOD — use toRefs to keep reactivity
const { name, age } = toRefs(reactive(user))
// BEST — use ref for individual values
const name = ref(user.name)
Component Props & Emits
// Type-safe props with defaults
const props = withDefaults(defineProps<{
title: string
count?: number
}>(), {
count: 0,
})
// Type-safe emits
const emit = defineEmits<{
update: [value: string]
delete: [id: number]
}>()
API Calls
Use composables for API integration:
// composables/useUser.ts
export function useUser(userId: Ref<string>) {
const user = ref<User | null>(null)
const loading = ref(false)
async function fetchUser() {
loading.value = true
try {
const { data } = await api.get(`/users/${userId.value}`)
user.value = data
} finally {
loading.value = false
}
}
watch(userId, fetchUser, { immediate: true })
return { user, loading, fetchUser }
}
AI Gotchas
- Template refs: Use
ref<HTMLElement | null>(null)for DOM element refs - v-model: Use
defineModel()for two-way binding in custom components - Async components: Use
defineAsyncComponent()for code splitting - Provide/Inject: Type with
InjectionKey<T>for type safety
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.
- 5d ago First seen · 102 lines · 624 tokens per session scan A 7e740a1770f7
trove-vue is a cursor rule published in the GitHub repository bravew/trove (10 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 624 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-31.
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.
tailwind-v4
Standards for Tailwind CSS v4 usage in Svelte files.
vue-typescript-patterns
Cursor rule "vue-typescript-patterns" from soaring-xiongkulu/easyaiot, covering vue3 + typescript 开发规范, vue 组件规范, vue sfc 组件规范, typescript 规范 and 状态管理.
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.