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/form-handlinggit clone --depth 1 https://github.com/aliarghyani/vue-cursor-rulesWrote 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/aliarghyani/vue-cursor-rules/form-handling)<a href="https://agentmods.dev/rules/aliarghyani/vue-cursor-rules/form-handling"><img src="https://agentmods.dev/badge/rules/aliarghyani/vue-cursor-rules/form-handling.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.1 | $0.00000 | $0.00838 |
| Opus 5 | $0.00000 | $0.00419 |
| Sonnet 5 | $0.00000 | $0.00168 |
| Haiku 4.5 | $0.00000 | $0.00084 |
Grade A, and why
form-handling 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 6d 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Form Handling
Role: You are a Vue 3 expert specializing in form validation and user input management.
Core Rules:
- Use reactive refs for form state
- Implement client-side validation patterns
- Handle loading and error states properly
- Provide clear user feedback
- Separate validation logic into composables
Chain-of-Thought: Think step-by-step: 1. Define form schema 2. Setup reactive state 3. Add validation rules 4. Handle submission
Note: These patterns are UI-framework neutral; adapt templates for kits like Vuetify/Quasar while preserving composable logic.
Basic Form Pattern
<script setup lang="ts">
import { ref } from 'vue'
interface LoginForm {
email: string
password: string
}
const form = ref<LoginForm>({
email: '',
password: ''
})
const errors = ref<Partial<LoginForm>>({})
const loading = ref(false)
const validateForm = (): boolean => {
errors.value = {}
if (!form.value.email) {
errors.value.email = 'Email is required'
} else if (!/\S+@\S+\.\S+/.test(form.value.email)) {
errors.value.email = 'Email is invalid'
}
if (!form.value.password) {
errors.value.password = 'Password is required'
} else if (form.value.password.length < 6) {
errors.value.password = 'Password must be at least 6 characters'
}
return Object.keys(errors.value).length === 0
}
const handleSubmit = async () => {
if (!validateForm()) return
loading.value = true
try {
await api.login(form.value)
// Handle success
} catch (error) {
// Handle error
} finally {
loading.value = false
}
}
</script>
<template>
<form @submit.prevent="handleSubmit">
<div>
<input
v-model="form.email"
type="email"
placeholder="Email"
:class="{ 'error': errors.email }"
/>
<span v-if="errors.email" class="error-message">
{{ errors.email }}
</span>
</div>
<div>
<input
v-model="form.password"
type="password"
placeholder="Password"
:class="{ 'error': errors.password }"
/>
<span v-if="errors.password" class="error-message">
{{ errors.password }}
</span>
</div>
<button type="submit" :disabled="loading">
{{ loading ? 'Submitting...' : 'Submit' }}
</button>
</form>
</template>
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.
- 6d ago First seen · 130 lines · 0 tokens per session scan A b4efee986006
form-handling 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 838 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
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.
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.
frontend
Vue frontend — components, Vitest, generated API client, apiCallWithLoading, DaisyUI. Read this first for any frontend work.