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/facturascripts/fs-claude-plugin/ui-designernpx skills add FacturaScripts/fs-claude-plugin --skill ui-designergit clone --depth 1 https://github.com/FacturaScripts/fs-claude-pluginWrote 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/facturascripts/fs-claude-plugin/ui-designer)<a href="https://agentmods.dev/skills/facturascripts/fs-claude-plugin/ui-designer"><img src="https://agentmods.dev/badge/skills/facturascripts/fs-claude-plugin/ui-designer.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 | $0.00165 | $0.00641 |
| Opus 5 | $0.00082 | $0.00320 |
| Sonnet 5 | $0.00033 | $0.00128 |
| Haiku 4.5 | $0.00016 | $0.00064 |
Grade A, and why
ui-designer 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.
How it starts
The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: ui-designer — Diseño de interfaces de FacturaScripts
Esta skill conecta las peticiones de diseño de interfaz del usuario con el agente
ui-designer, que tiene conocimiento profundo del sistema de XMLView, widgets, filtros
y filas de FacturaScripts.
Por qué usar el agente
El agente ui-designer conoce todos los widgets disponibles (text, number, money, date,
select, autocomplete, checkbox, etc.), sus atributos, los tipos de filtros, las filas de
estado/acciones/estadísticas, los modales y la distribución responsive con numcolumns.
Diseñar interfaces sin este conocimiento puede resultar en widgets incorrectos o layouts
mal estructurados.
Cómo invocar el agente
Agente: ui-designer
Tarea: [descripción exacta del diseño de interfaz necesario]
El agente:
- Consulta la documentación de widgets, columnas, filas y filtros
- Analiza los XMLViews existentes para mantener coherencia visual
- Diseña la estructura del XMLView con widgets apropiados
- Define filtros útiles para el controlador
- Añade filas de estado, acciones y estadísticas según corresponda
Qué tareas activan esta skill
- "Diseña el formulario de edición para mi modelo Proyecto"
- "Quiero un listado con filtros por estado, fecha y cliente"
- "Añade un widget autocomplete para buscar productos"
- "Necesito filas de colores según el estado del registro"
- "Crea un modal para importar datos desde CSV"
- "¿Qué widget debo usar para un campo de importe?"
- "Reorganiza las columnas del formulario en grupos"
- "Añade botones de acción en la barra del listado"
- Cualquier tarea sobre diseño visual de formularios o listados en FacturaScripts
Cuándo NO activar esta skill
- Plantillas Twig personalizadas, CSS o JavaScript → usa
frontend-developer - Lógica del modelo o base de datos → usa
backend-developer - Extensiones de XMLView de otros plugins → usa
extension-developer - Funcionalidades completas end-to-end → usa
fullstack-developer - Endpoints de API → usa
api-designer
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 · 61 lines · 165 tokens per session scan A efbbc480c407
ui-designer is a skill published in the GitHub repository FacturaScripts/fs-claude-plugin (8 stars, last pushed 2d ago), licensed MIT. It adds 165 tokens to every session and 641 once invoked, about $0.0008 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…