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/commands/usrrname/cursorrules/vue3)<a href="https://agentmods.dev/commands/usrrname/cursorrules/vue3"><img src="https://agentmods.dev/badge/commands/usrrname/cursorrules/vue3/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/commands/usrrname/cursorrules/vue3"><img src="https://agentmods.dev/badge/commands/usrrname/cursorrules/vue3.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.00252 |
| Opus 5.5 | $0.00000 | $0.00101 |
| Sonnet 5.5 | $0.00000 | $0.00050 |
| Haiku 4.5 | $0.00000 | $0.00025 |
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 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.
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>syntaxdefineProps<Props>()for propsdefineEmits<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.
Related
/typescript- TypeScript fundamentals
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 · 63 lines · 0 tokens per session scan A 71cd99112ff3
vue3 is a command 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 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.
Other commands, from other repositories
generate-types
Generate TypeScript types or type definitions from schemas, APIs, or data structures.
svelte:component
Create new Svelte components with best practices, proper structure, and optional TypeScript support.
component
Create a new Vue 3 component with TypeScript and Composition API.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.