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 G1Joshi/Agent-Skills --skill vuetifygit clone --depth 1 https://github.com/G1Joshi/Agent-SkillsWrote 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/g1joshi/agent-skills/vuetify)<a href="https://agentmods.dev/skills/g1joshi/agent-skills/vuetify"><img src="https://agentmods.dev/badge/skills/g1joshi/agent-skills/vuetify/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/g1joshi/agent-skills/vuetify"><img src="https://agentmods.dev/badge/skills/g1joshi/agent-skills/vuetify.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.00040 | $0.01609 |
| Opus 5.5 | $0.00016 | $0.00644 |
| Sonnet 5.5 | $0.00008 | $0.00322 |
| Haiku 4.5 | $0.00004 | $0.00161 |
Grade A, and why
vuetify 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 26d 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 — 237 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vuetify
Vuetify is the comprehensive UI toolkit for Vue. v3 (Titan) is built for Vue 3 and Vite, offering massive performance improvements over v2.
When to Use
- Material Design 3 Applications in Vue 3: Enterprise business applications implementing Google Material Design.
- Complex Enterprise Data Tables: Server-side pagination, sorting, filtering, and row expansion with
v-data-table-server. - Administrative Portals & Dashboards: Pre-built form inputs, navigation drawers, app bars, and dialogs.
- Accessible Multi-Theme Applications: Switching seamlessly between light and dark themes with custom primary colors.
Quick Start
<template>
<v-app>
<v-main>
<v-container>
<v-card class="pa-4" elevation="2">
<v-card-title>Vuetify Card</v-card-title>
<v-card-text
>Ready-to-use Material Design components for Vue 3.</v-card-text
>
<v-btn color="primary" @click="showAlert">Action</v-btn>
</v-card>
</v-container>
</v-main>
</v-app>
</template>
<script setup>
function showAlert() {
alert("Vuetify action triggered");
}
</script>
Core Concepts
Theme Configuration & Component Blueprint Setup
Setting up Vuetify 3 with Material Design 3 tokens:
// plugins/vuetify.ts
import "vuetify/styles";
import { createVuetify } from "vuetify";
import * as components from "vuetify/components";
import * as directives from "vuetify/directives";
export const vuetify = createVuetify({
components,
directives,
theme: {
defaultTheme: "light",
themes: {
light: {
colors: {
primary: "#1867C0",
secondary: "#5CBBF6",
surface: "#FFFFFF",
},
},
dark: {
colors: {
primary: "#2196F3",
secondary: "#424242",
surface: "#121212",
},
},
},
},
});
Server-Side Data Table with v-data-table-server
Displaying remote paginated data with sorting:
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.
- 26d ago Changed · +5 lines b74884d7f0c8
- 1mo ago Changed · +187 lines · +21 tokens per session 0029ef12d9cd
- 1mo ago First seen · 45 lines · 19 tokens per session scan A e5396d1a093b
vuetify is a skill published in the GitHub repository G1Joshi/Agent-Skills (15 stars, last pushed 26d ago), licensed MIT. It adds 40 tokens to every session and 1,609 once invoked, about $0.0002 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
frontend-ui-engineering
Builds production-quality, accessible, responsive user-facing UIs. Use when building or modifying interfaces and pages, creating components, implementing layouts, meeting WCAG accessibility requirements, managing state, or when the output needs to look and feel production-quality rather than AI-generated.
awesome-accessibility-audit
Read-only WCAG audit of UI and markup with a concrete fix per finding. Use when asked to check accessibility, a11y, keyboard or screen-reader support, or contrast.
frontend-ui-engineering
Front-load UI construction decisions — component boundary and prop API, state placement, required states, responsiveness, accessibility. Use when creating or refactoring a component, page, or design-system primitive. Don't use for pure logic (/tdd), throwaway exploration (/prototype), or auditing finished UI…
prototype
Build a throwaway prototype — a shareable HTML demo for state/logic questions, or several UI variations toggleable from one route. Use when comparing design directions before committing, or the user says "prototype", "mock up", "try a few approaches". Don't use for production code (/build, /tdd).
frontend-ui-engineering
Builds production-quality UIs. Use when building or modifying user-facing interfaces. Use when creating components, implementing layouts, managing state, or when the output needs to look and feel production-quality rather than AI-generated.
context-engineering
Optimizes agent context setup. Use when starting a new session, when agent output quality degrades, when switching between tasks, or when you need to configure rules files and context for a project.