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/usrrname/cursorrulesWrote 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/usrrname/cursorrules/vue3-typescript-auto)<a href="https://agentmods.dev/rules/usrrname/cursorrules/vue3-typescript-auto"><img src="https://agentmods.dev/badge/rules/usrrname/cursorrules/vue3-typescript-auto/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/usrrname/cursorrules/vue3-typescript-auto"><img src="https://agentmods.dev/badge/rules/usrrname/cursorrules/vue3-typescript-auto.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.02292 |
| Opus 5.5 | $0.00000 | $0.00917 |
| Sonnet 5.5 | $0.00000 | $0.00458 |
| Haiku 4.5 | $0.00000 | $0.00229 |
Grade A, and why
vue3-typescript-auto 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 — 359 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vue 3 with TypeScript Standards
Modern Vue 3 development with TypeScript, emphasizing type safety, Composition API, and performance.
Critical Rules
- Use Composition API with
<script setup lang="ts">syntax - Type all props, emits, reactive data, and composables explicitly
- Use
defineModel()for 2 way binding v-model anddefineSlots()for slot typing - Follow PascalCase naming for components
- Use proper provide/inject typing with injection keys
- Type watchers explicitly and ensure proper cleanup
- Optimize performance with computed properties and shallow reactivity
✅ Use Composition API with proper typing:
<script setup lang="ts">
interface Props {
title: string
count?: number
}
interface Emits {
(e: 'update', value: number): void
}
interface Slots {
default(props: { item: string }): any
header(): any
}
const props = defineProps<Props>()
const emit = defineEmits<Emits>()
const slots = defineSlots<Slots>()
const model = defineModel<string>()
const count = ref<number>(0)
const doubleCount = computed<number>(() => count.value * 2)
</script>
❌ Avoid Options API and untyped refs:
const props = defineProps(['title'])
const count = ref(0)
examples:
- input: | const props = defineProps(['title']) const model = defineModel() const count = ref(0) output: | interface Props { title: string } const props = defineProps() const model = defineModel() const count = ref(0) metadata: priority: high version: 1.0
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 · 359 lines · 2,292 tokens per session scan A 51323823a20e
vue3-typescript-auto is a cursor rule published in the GitHub repository usrrname/cursorrules (11 stars, last pushed 6mo ago), licensed ISC. It costs nothing until one of its globs matches a file; then it loads 2,292 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
sveltekit-tailwindcss-typescript-cursorrules-promp
Cursor rules for SvelteKit development with Tailwind CSS and TypeScript integration.
angular
Angular: signals, standalone components, RxJS patterns.
typescript
Strict TypeScript: generics, discriminated unions, no any.
bun
Bun runtime: Bun.serve, Bun.file, bundler, test runner.
deno
Deno: permissions, deno.json, std library, Deploy.
typescript
TypeScript best practices.