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/vuetify4npx skills add dmitrypost/VuetifySkills --skill vuetify4git 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/vuetify4)<a href="https://agentmods.dev/skills/dmitrypost/vuetifyskills/vuetify4"><img src="https://agentmods.dev/badge/skills/dmitrypost/vuetifyskills/vuetify4.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.00313 |
| Opus 5 | $0.00026 | $0.00156 |
| Sonnet 5 | $0.00010 | $0.00063 |
| Haiku 4.5 | $0.00005 | $0.00031 |
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 5d 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
The corpus lives outside this skill directory (shared with the Copilot and OpenAI exports). Read it from these paths, relative to this SKILL.md:
- ../../../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 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.
- 5d ago First seen · 44 lines · 52 tokens per session scan A 8b056bf0594b
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 313 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
phoenix-intent
Decompose a high-level vague intent into N concrete /goal instances (≤5), each with its own phoenixsense acceptance check, proven complete via composite phoenixaccept (all N sawred AND greenafterred AND currentlygreen). Use when a task is multi-faceted (build + integrate + configure + notify) with independent or…
phoenix-mission
Run an N-goal DAG under the Phoenix supervisor — dependency-ordered execution with worktree isolation, lease fencing, budgets, a durable run ledger, and per-goal trace chains, on the local machine or dispatched to GitHub Copilot cloud agents. Use when goals have prerequisites, when a failure must contain its blast…
phoenix
The meta-skill that routes a task to the right Phoenix lifecycle skill and enforces the non-negotiable operating laws. Use at the start of any session or task to decide which Phoenix skill applies. Phoenix is a self-healing, token-efficient engineering harness — every stage verifies its work with an objective check…
phoenix-deps
Dependency and supply-chain hygiene where the clean-room install is the objective gate — audit every package manager in the repo, rank remediation by exploitation evidence rather than severity label, disclose any manager that could not be audited, and stop at the no-op boundary instead of opening an empty dependency…
phoenix-context
Assemble the cheapest sufficient context for a task — route structural questions (who calls X, what breaks if I change Y, what inherits from Z) to the prebuilt code graph instead of grepping and re-reading files, and pull the relevant subgraph/snippet rather than whole directories. Use on any non-trivial codebase…
phoenix-doctor
Diagnose and repair a Phoenix install with the same objective discipline Phoenix gives the agent — check whether the installed agent, skills, and MCP registration match what this build ships, and re-sync any drift with a snapshot-backed fix that is re-verified red→green. Use when Copilot says "No such agent: phoenix"…