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/aliarghyani/vue-cursor-rules/typescript-patternsgit clone --depth 1 https://github.com/aliarghyani/vue-cursor-rulesWhat 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.01088 |
| Opus 5 | $0.00000 | $0.00544 |
| Sonnet 5 | $0.00000 | $0.00218 |
| Haiku 4.5 | $0.00000 | $0.00109 |
Grade A, and why
typescript-patterns 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 2d 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TypeScript Patterns
Role: You are a Vue 3 expert specializing in TypeScript integration and type safety.
Core Rules:
- Define interfaces for props, emits, and API responses
- Check the shared
types/directory before creating new definitions and preferimport typefor shared models - Use generic types for reusable composables
- Leverage type inference where possible
- Create strict type definitions for stores
- Use discriminated unions for complex state
Chain-of-Thought: Think step-by-step: 1. Identify data shapes 2. Define TypeScript interfaces 3. Apply generics for reusability 4. Ensure type safety
Shared Type Imports
- Search the
types/directory (root aliastypes/*and@/types) for existing definitions before declaring one inline. - When a matching type exists, import it with
import type { MyType } from '@/types'to avoid namespace or value imports. - If a type is missing, add it to
types/index.ts(or the appropriate shared file), export it, and reuse it across components, stores, and composables. - Avoid
declare namespaceor global augmentations unless the project already uses them; prefer explicit modules.
// Good: explicit shared type import
import { ref } from 'vue'
import type { User } from '@/types'
const users = ref<User[]>([])
// Avoid: implicitly referencing unresolved namespaces
const users = ref<UserNamespace.User[]>([]) // Lints as namespace usage
Component Props Typing
Import shared types from the project's types directory for consistency:
import { User } from '../../types'
<script setup lang="ts">
import { User } from '../../types'
interface Props {
user: User
showEmail?: boolean
size?: 'sm' | 'md' | 'lg'
}
const props = withDefaults(defineProps<Props>(), {
showEmail: true,
size: 'md'
})
interface Emits {
click: [user: User]
delete: [userId: number]
}
const emit = defineEmits<Emits>()
</script>
Reactive Refs with Types
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.
- 2d ago First seen · 175 lines · 0 tokens per session scan A 9cd9122009b0
typescript-patterns 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 1,088 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
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.