vue3

A command for applying Vue 3 development patterns with TypeScript and the Composition API, Vue's approach for organising reusable component logic.

In plain words
What is it for?
Creating Vue 3 components, composables, state management code, and TypeScript integrations.
Why use it?
It gives Vue code a consistent structure and adds type checking for components, state, events, and reusable logic.

Command for Claude Code

Install

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.

agentmods
npx agentmods add commands/usrrname/cursorrules/vue3
Clone the repo
git clone --depth 1 https://github.com/usrrname/cursorrules

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 252 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00252
Opus 5 $0.00000 $0.00126
Sonnet 5 $0.00000 $0.00050
Haiku 4.5 $0.00000 $0.00025

Measured 2d ago against content hash 71cd99112ff3, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

vue3 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.

.claude/commands/vue3.md · 63 lines

What it actually says

/vue3

Apply Vue 3 with TypeScript and Composition API patterns.

Usage

/vue3 [component-or-composable]

When to Invoke

Use this command when:

  • Creating Vue 3 components
  • Using Composition API
  • Building custom composables
  • Managing Vue state

Standards Applied

Component Structure

  • <script setup> syntax
  • defineProps<Props>() for props
  • defineEmits<Emits>() for events
  • Proper TypeScript types

Composition API

  • Composables for reusable logic
  • Prefix with 'use'
  • Eager loading for relationships
  • Query scopes for reuse

TypeScript Integration

  • Enable strict mode
  • Type reactive objects
  • Use generic components
  • Type provide/inject

Examples

<script setup lang="ts">
interface Props {
  title: string;
  count?: number;
}

const props = withDefaults(defineProps<Props>(), {
  count: 0
});

const doubled = computed(() => props.count * 2);
</script>

Agent

Uses BasicBitch for implementation.

  • /typescript - TypeScript fundamentals
Changes

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.

  1. 2d ago First seen · 63 lines · 0 tokens per session scan A 71cd99112ff3

Subscribe to this mod's changes

vue3 is a command published in the GitHub repository usrrname/cursorrules (10 stars, last pushed 4mo ago), licensed ISC. It costs nothing until one of its globs matches a file; then it loads 252 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.