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 skills/dmitrypost/vuetifyskills/claudenpx skills add dmitrypost/VuetifySkills --skill claudegit clone --depth 1 https://github.com/dmitrypost/VuetifySkillsWrote 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/dmitrypost/vuetifyskills/claude)<a href="https://agentmods.dev/skills/dmitrypost/vuetifyskills/claude"><img src="https://agentmods.dev/badge/skills/dmitrypost/vuetifyskills/claude.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.00052 | $0.00278 |
| Opus 5 | $0.00026 | $0.00139 |
| Sonnet 5 | $0.00010 | $0.00056 |
| Haiku 4.5 | $0.00005 | $0.00028 |
Grade A, and why
vuetify4 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.
What it actually says
Vuetify 4 Agent Guide
Pinned release: 4.0.5 Pinned docs build: bf53f9e Total pages: 394
Use this corpus only for Vuetify 4 questions. Prefer guide and component pages for usage patterns and implementation examples. Prefer API pages for props, events, slots, directives, composables, and source links. If guide prose and API enrichment differ, prefer the API-enrichment section and linked source file.
Section Order
- Introduction
- Getting started
- Features
- Styles and animations
- Common concepts
- Components
- API
- Directives
- Labs
- Resources
- About
Primary Files
- skills/vuetify4/manifest.json
- skills/vuetify4/README.md
- skills/vuetify4/pages/**
Response Rules
- Answer with Vuetify 4-only guidance.
- Use guide pages for examples and API pages for contract details.
- Mention the generated page path and linked source file when the answer depends on source behavior.
What ships with it
1 file 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.
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 · 41 lines · 52 tokens per session scan A 37db532c46c4
vuetify4 is a skill published in the GitHub repository dmitrypost/VuetifySkills (5 stars, last pushed 3mo ago), licensed MIT. It adds 52 tokens to every session and 278 once invoked, about $0.0003 per session on Opus 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-08-31.
Other skills, from other repositories
create-vue-component
Integrate a Vue 3 component into a Symfony admin page for complex UX sections. This is an exception pattern — most pages use initComponents with standard components. Vue is only needed when a section requires rich interactivity that standard form types cannot provide (e.g. combination listing, dynamic range tables).…
deploy-svelte
Use this skill when an agent needs to deploy this sveltekit app on build.host and return SvelteKit adapter-node, websockets and server actions live.
deploy-vue
Use this skill when an agent needs to deploy this nuxt app on build.host and return Nuxt 3 with Nitro, edge or node target - your choice.
nuxt-development
Standards for Nuxt.js 3 development with auto-imports, file-based routing, and SSR/SSG capabilities. Use when working with Nuxt projects, pages/, layouts/, composables/ directories, or when the user asks about Nuxt-specific patterns, server-side rendering, or Nuxt configuration.
vue-development
Coding standards and conventions for Vue.js 3 development with Composition API. Use when working with .vue files, Vue components, composables, or when the user asks about Vue.js patterns, single-file components, script setup syntax, or Vue-specific best practices.
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.