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 skills add smicolon/ai-kit --skill veevalidate-form-validatorgit clone --depth 1 https://github.com/smicolon/ai-kitWrote 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/skills/smicolon/ai-kit/veevalidate-form-validator)<a href="https://agentmods.dev/skills/smicolon/ai-kit/veevalidate-form-validator"><img src="https://agentmods.dev/badge/skills/smicolon/ai-kit/veevalidate-form-validator/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/skills/smicolon/ai-kit/veevalidate-form-validator"><img src="https://agentmods.dev/badge/skills/smicolon/ai-kit/veevalidate-form-validator.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.00065 | $0.01170 |
| Opus 5.5 | $0.00026 | $0.00468 |
| Sonnet 5.5 | $0.00013 | $0.00234 |
| Haiku 4.5 | $0.00006 | $0.00117 |
Grade A, and why
veevalidate-form-validator 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 — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VeeValidate + Zod Form Validator
Activation Triggers
This skill activates when:
- Creating form components
- Mentioning "form", "validation", "input"
- Writing
<form>or v-model - Handling user input
Required Pattern
<script setup lang="ts">
import { useForm } from 'vee-validate'
import { toTypedSchema } from '@vee-validate/zod'
import { z } from 'zod'
// Define schema with Zod
const schema = toTypedSchema(
z.object({
email: z.string().email('Invalid email'),
password: z.string().min(8, 'Password too short'),
})
)
// Create form with VeeValidate
const { handleSubmit, errors, defineField } = useForm({
validationSchema: schema,
})
// Define reactive fields
const [email, emailAttrs] = defineField('email')
const [password, passwordAttrs] = defineField('password')
// Type-safe submit handler
const onSubmit = handleSubmit((values) => {
// values is typed: { email: string, password: string }
console.log(values.email, values.password)
})
</script>
<template>
<form @submit="onSubmit">
<div>
<label for="email">Email</label>
<input
id="email"
v-model="email"
v-bind="emailAttrs"
type="email"
aria-describedby="email-error"
/>
<span v-if="errors.email" id="email-error" class="error" role="alert">
{{ errors.email }}
</span>
</div>
<div>
<label for="password">Password</label>
<input
id="password"
v-model="password"
v-bind="passwordAttrs"
type="password"
aria-describedby="password-error"
/>
<span v-if="errors.password" id="password-error" class="error" role="alert">
{{ errors.password }}
</span>
</div>
<button type="submit">Submit</button>
</form>
</template>
Forbidden Patterns
<!-- WRONG: No validation -->
<input v-model="email" />
<button @click="submit">Submit</button>
<!-- WRONG: Manual validation -->
<input v-model="email" @blur="validateEmail" />
<!-- WRONG: Template-only validation -->
<input v-model="email" :class="{ error: !isValidEmail }" />
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 · 191 lines · 65 tokens per session scan A d138f6237720
veevalidate-form-validator is a skill published in the GitHub repository smicolon/ai-kit (6 stars, last pushed 1mo ago), licensed MIT. It adds 65 tokens to every session and 1,170 once invoked, about $0.0003 per session on Opus 5.5. 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-09-03.
Other skills, from other repositories
vue-component
Create Vue 3 components with Composition API — composables, Pinia store integration, TypeScript, and unit tests.
develop-web-game
Use when Codex is building or iterating on a web game (HTML/JS) and needs a reliable development + testing loop: implement small changes, run a Playwright-based test script with short input bursts and intentional pauses, inspect screenshots/text, and review console errors with rendergametotext.
ui-craft-checks
Use this comprehensive gate for formal review, QA, launch handoff, exact-fidelity inspection, high-risk complex UI, or when the fast gate exposes a deeper craft problem. Ordinary single-screen work uses ui-design-executor and its bundled validator without loading this full matrix. Pair standalone artifacts with…
red-team-review
Unified adversarial review, two modes. Strategic Matrix v4.3 (MTA-004) for arguments/plans/decisions: Priors → Rubric → Adversarial Lenses → SWOT/TOWS → MCDA → Blind Spot/Kill Switch → Summary. Deliverable Audit for built artefacts (assignments, reports, code outputs): isolated fresh-context hunt against the brief…
ha-test-strategy
Hope-native test strategy for features, fixes, and refactors: select test-first, regression-first, characterization, integration, E2E, or manual evidence according to risk and repository rules.
visual-regression
Setup visual regression testing with Storybook stories, configuration, and CI/CD workflows. Supports Chromatic, Percy, BackstopJS. Auto-invoke when user says "set up visual regression", "add Chromatic tests", "add screenshot testing", or "set up Percy".