Borrowing it
Nothing to install: this file belongs to watt-mind/coach. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/watt-mind/coach/master/.gemini/commands/nuxt/ui.tomlgit clone --depth 1 https://github.com/watt-mind/coachWrote 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/commands/watt-mind/coach/ui)<a href="https://agentmods.dev/commands/watt-mind/coach/ui"><img src="https://agentmods.dev/badge/commands/watt-mind/coach/ui.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.00000 | $0.00287 |
| Opus 5 | $0.00000 | $0.00143 |
| Sonnet 5 | $0.00000 | $0.00057 |
| Haiku 4.5 | $0.00000 | $0.00029 |
Grade A, and why
ui 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 3d 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
description = "Review recent Nuxt UI component usage against official documentation" prompt = """ You are a Nuxt UI expert. Your task is to verify that recent component usage adheres to the official Nuxt UI documentation.
Instructions:
-
Identify Components:
- Scan the recently modified files (or files provided in '{{args}}') for Nuxt UI components (e.g.,
UButton,USelect,UCard). - If no files are specified, check the most recently edited Vue files in the project.
- Scan the recently modified files (or files provided in '{{args}}') for Nuxt UI components (e.g.,
-
Consult Documentation:
- Use the
get-componenttool from the Nuxt UI MCP server for each identified component. - Example:
get-component(componentName='Select')(Note: component names in docs are often PascalCase without the 'U' prefix, verify this pattern).
- Use the
-
Verify Usage:
- Compare the props, slots, and events used in the code against the documentation returned by the tool.
- Look for deprecated props, incorrect types, or missing required attributes.
- Specifically check for version mismatches (e.g., v3 vs v4 prop names like
close-buttonvsclose).
-
Report & Fix:
- If usage is correct, confirm it.
- If errors are found, explain the discrepancy citing the documentation and propose or apply a fix. """
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.
- 3d ago First seen · 23 lines · 0 tokens per session scan A e492799cd35d
ui is a command published in the GitHub repository watt-mind/coach (83 stars, last pushed 5d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 287 tokens. 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-04.
Other commands, from other repositories
component-gen
Generate React or Vue components with prop types, styling, accessibility, and tests.
setup
Interactive setup for Vue.js LSP development environment.
setup
Interactive setup for Svelte LSP development environment.
svelte:storybook-troubleshoot
Diagnose and fix common Storybook issues in SvelteKit projects, including build errors, module problems, and configuration issues.
svelte:migrate
Migrate Svelte/SvelteKit projects between versions, adopt new features like runes, and handle breaking changes.
test
Generate Vitest tests for Vue components or functions.