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 scott-fryxell/brayness --skill vuetify-to-semanticgit clone --depth 1 https://github.com/scott-fryxell/braynessWrote 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/scott-fryxell/brayness/vuetify-to-semantic)<a href="https://agentmods.dev/skills/scott-fryxell/brayness/vuetify-to-semantic"><img src="https://agentmods.dev/badge/skills/scott-fryxell/brayness/vuetify-to-semantic/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/scott-fryxell/brayness/vuetify-to-semantic"><img src="https://agentmods.dev/badge/skills/scott-fryxell/brayness/vuetify-to-semantic.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.00094 | $0.01249 |
| Opus 5 | $0.00047 | $0.00624 |
| Sonnet 5 | $0.00019 | $0.00250 |
| Haiku 4.5 | $0.00009 | $0.00125 |
Grade A, and why
vuetify-to-semantic 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 12d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vuetify to Semantic
Refactor a seeq-app Vue page or component from Vuetify to semantic HTML5, Schema.org microdata, and Stylus element selectors. Follows the work/realness pattern: no utility classes, no replacement component library, styles applied via element and attribute selectors only.
Process
1. Read the target file
Read the full .vue file. Identify:
- Every
v-*component used - Every Vuetify utility class (
pa-*,ma-*,d-flex,text-h*,elevation-*, etc.) - Every
useTheme/useDisplayimport from'vuetify' - What real-world entities the page represents (projects, stories, people, organizations)
2. Map components to semantic elements
Use references/component-map.md for the full mapping.
Key decisions:
v-row/v-col-> remove both; apply CSS Grid to the parent element directlyv-card-><article>with the correct Schema.orgitemtypefor the entityv-sheet-><section>or<aside>based on rolev-list/v-list-item-><ul>/<li>only when content is truly a list; use<article>per item when each stands alonev-btnwithto=-><a>; withoutto=-><button>v-icon-><svg class="icon"><use href="/icons.svg#name" /></svg>v-dialog-><dialog>v-navigation-drawer-><nav>v-app-bar-><header>
3. Add Schema.org microdata
Use references/microdata-entities.md for Seeq entity types.
Rules:
- Add
itemscope itemtype="https://schema.org/X"to the container element - Add
itempropto child elements that carry data fields - Use
<time datetime="...">for dates - Use
<data value="...">for machine-readable values not in visible text - Do not add microdata to layout-only elements
4. Rewrite the template
Output a clean <template> block:
- No
v-*components - No Vuetify utility classes on any element
- Semantic elements with correct hierarchy
- Schema.org attributes on entity containers and their fields
data-*attributes for JS state hooks where needed- ARIA only where native HTML cannot express the needed behavior
- Keep all Vue directives (
v-if,v-for,v-model,@click,:src, etc.) intact
What ships with it
5 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.
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.
- 12d ago First seen · 128 lines · 94 tokens per session scan A c1030e3647d4
vuetify-to-semantic is a skill published in the GitHub repository scott-fryxell/brayness (121 stars, last pushed 3d ago), licensed MIT. It adds 94 tokens to every session and 1,249 once invoked, about $0.0005 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-30.
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.
shadcn-svelte
Manages shadcn-svelte components and projects — adding, updating, fixing, debugging, styling, and composing UI. Provides project context, component docs, and usage examples. Applies when working with shadcn-svelte, the CLI, design-system presets, or any project with a components.json file. Also triggers for…
nuxt-ui
Build UIs with @nuxt/ui v4 — 125+ accessible Vue components with Tailwind CSS theming. Use when creating interfaces, customizing themes to match a brand, building forms, or composing layouts like dashboards, docs sites, and chat interfaces.
league-akari-ui-components
Use when implementing or reviewing League Akari renderer UI components, especially consistency across related components, i18n component interpolation, multiple independent pluralized counts, Tailwind utility usage in templates or SFC style blocks, or native semantic HTML elements in the Naive UI renderer.
vue-base-skill
A parent guide for building Vue interface components with shared rules for cards, buttons, labels, and tables. It requires these components to sit inside a base card and use shared CSS design values.
b24-ui-nuxt
Build UIs with @bitrix24/b24ui-nuxt v2 — 130+ accessible Vue components with Tailwind CSS theming. Use when creating interfaces, building forms, or composing layouts for a Bitrix24 application.