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 williamzujkowski/standards --skill vuegit clone --depth 1 https://github.com/williamzujkowski/standardsWrote 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/williamzujkowski/standards/vue)<a href="https://agentmods.dev/skills/williamzujkowski/standards/vue"><img src="https://agentmods.dev/badge/skills/williamzujkowski/standards/vue/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/williamzujkowski/standards/vue"><img src="https://agentmods.dev/badge/skills/williamzujkowski/standards/vue.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.00009 | $0.02685 |
| Opus 5.5 | $0.00004 | $0.01074 |
| Sonnet 5.5 | $0.00002 | $0.00537 |
| Haiku 4.5 | $0.00001 | $0.00268 |
Grade A, and why
vue-frontend 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 yesterday.
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 — 481 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vue.js Frontend Development Skill
Level 1: Quick Reference (~700-900 tokens)
Core Concepts
Composition API vs Options API
// Composition API (recommended for new projects)
import { ref, computed } from 'vue';
const count = ref(0);
const doubled = computed(() => count.value * 2);
// Options API (traditional)
export default {
data() { return { count: 0 }; },
computed: { doubled() { return this.count * 2; } }
};
Reactivity Fundamentals
// ref - for primitives and single values
const count = ref(0);
count.value++; // access with .value
// reactive - for objects
const state = reactive({ count: 0, name: 'Vue' });
state.count++; // direct access
// computed - derived state
const doubled = computed(() => count.value * 2);
// watch - side effects
watch(count, (newVal, oldVal) => {
console.log(`Count changed from ${oldVal} to ${newVal}`);
});
Component Communication
// Props (parent → child)
defineProps<{ message: string }>();
// Emits (child → parent)
const emit = defineEmits<{ submit: [data: FormData] }>();
emit('submit', formData);
// Provide/Inject (ancestor → descendant)
// Parent
provide('theme', ref('dark'));
// Child
const theme = inject<Ref<string>>('theme');
Essential Checklist
Setup & Configuration
- Vue 3 with Vite or Vue CLI
- TypeScript integration
- ESLint + Prettier configured
- Vue Router installed
- Pinia for state management
- Vitest + Vue Test Utils for testing
Component Development
- Use Composition API with
<script setup> - Define props with TypeScript types
- Emit typed events
- Implement proper lifecycle hooks
- Use composables for reusable logic
Routing & Navigation
- Define routes with lazy loading
- Implement route guards (auth, permissions)
- Handle 404 and error pages
- Use typed router with generics
State Management
- Define Pinia stores with TypeScript
- Use composition stores for complex logic
- Implement persistence for user preferences
- Handle async actions properly
What ships with it
10 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- config/vitest.config.ts 5.5 KB runs code
- REFERENCE.md 22 KB
- resources/accessibility-checklist.md 9.0 KB
- resources/performance-checklist.md 12 KB
- resources/README.md 20 B
- scripts/README.md 18 B
- templates/component.test.ts 11 KB runs code
- templates/composition-component.vue 9.4 KB
- templates/pinia-store.ts 8.4 KB runs code
- templates/README.md 20 B
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.
- yesterday First seen · 481 lines · 9 tokens per session scan A da65eac96efb
vue-frontend is a skill published in the GitHub repository williamzujkowski/standards (18 stars, last pushed 1mo ago), licensed MIT. It adds 9 tokens to every session and 2,685 once invoked, about $0.0000 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-29.
Other skills, from other repositories
shadcn-svelte
Pre-built shadcn-svelte components for json-render Svelte apps. Use when working with @json-render/shadcn-svelte, adding standard UI components to a Svelte catalog, or building Svelte web UIs with shadcn-svelte + Tailwind CSS components.
moai-domain-uiux
UI/UX design systems specialist covering accessibility, icons, theming, design tokens, and user experience patterns. Use when working on design systems, WCAG compliance, ARIA patterns, or dark mode theming.
moai-domain-frontend
Frontend development specialist covering React 19, Next.js 16, Vue 3.5, and modern UI/UX patterns with component architecture. Use when building web UIs, implementing components, optimizing frontend performance, or integrating state management.
v3-create-crud
A page generator for standard create, read, update, and delete screens, commonly called CRUD screens. It uses Element Plus, a Vue user-interface library, to build tables, searches, pagination, forms, and delete confirmations.
v3-use-composables
Documentation for reusable Vue functions in a project, covering device detection, asynchronous dropdown data, loading screens, pagination, routing, themes, page titles, and watermarks.
frontend-conventions
Frontend convention reference (SvelteKit / Svelte 5). Auto-injected into frontend-aware agents - not user-invocable.