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/frontend-developernpx skills add FacturaScripts/fs-claude-plugin --skill frontend-developergit clone --depth 1 https://github.com/FacturaScripts/fs-claude-pluginWhat 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.00140 | $0.00636 |
| Opus 5 | $0.00070 | $0.00318 |
| Sonnet 5 | $0.00028 | $0.00127 |
| Haiku 4.5 | $0.00014 | $0.00064 |
Grade A, and why
frontend-developer 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 2d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: frontend-developer — Desarrollo frontend de FacturaScripts
Esta skill conecta las peticiones de desarrollo frontend del usuario con el agente
frontend-developer, que tiene conocimiento profundo del sistema de plantillas Twig,
gestión de assets y patrones de UI de FacturaScripts.
Por qué usar el agente
El agente frontend-developer conoce la herencia de plantillas Twig específica de
FacturaScripts (MenuTemplate, MicroTemplate), las funciones Twig disponibles (trans, asset,
formToken, number, money, settings), el AssetManager para registrar CSS/JS, y los patrones
de extensión de vistas. Responder sin el agente puede generar plantillas incompatibles con
el sistema de herencia del framework.
Cómo invocar el agente
Agente: frontend-developer
Tarea: [descripción exacta de lo que necesita el usuario]
El agente:
- Consulta la documentación en
./agents/docs/(vistas HTML, herencia, AssetManager) - Analiza las plantillas existentes del plugin
- Implementa la solución frontend siguiendo las convenciones de FacturaScripts
- Crea los archivos necesarios (View/*.html.twig, Assets/CSS/, Assets/JS/)
Qué tareas activan esta skill
- "Crea una vista Twig personalizada para mi controlador"
- "Necesito un dashboard con gráficos usando JavaScript"
- "Añade un archivo CSS personalizado al plugin"
- "Crea una función Twig para formatear fechas de forma especial"
- "Necesito un formulario AJAX que envíe datos sin recargar la página"
- "Quiero extender la plantilla de EditCliente con un panel extra"
- "Añade un script JavaScript que valide el formulario en cliente"
- Cualquier tarea que involucre Twig, HTML, CSS, JavaScript o assets visuales
Cuándo NO activar esta skill
- Definición de XMLViews (columnas, widgets, filtros) → usa
ui-designer - Modelos PHP, workers o lógica de negocio → usa
backend-developer - Extensiones PHP de controladores/modelos → usa
extension-developer - Endpoints de API REST → usa
api-designer - Funcionalidades completas end-to-end → usa
fullstack-developer
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.
- 2d ago First seen · 58 lines · 140 tokens per session scan A d0872ed021ea
frontend-developer is a skill published in the GitHub repository FacturaScripts/fs-claude-plugin (8 stars, last pushed 2mo ago), licensed MIT. It adds 140 tokens to every session and 636 once invoked, about $0.0007 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
design-guide
Paperclip UI design system guide for building consistent, reusable frontend components. Use when creating new UI components, modifying existing ones, adding pages or features to the frontend, styling UI elements, or when you need to understand the design language and conventions. Covers: component creation, design…
Shade ShadCN install
Guardrails for running pnpm dlx shadcn@latest add in Shade — never overwrite existing components, fresh branch first, swap raw colours for semantic tokens after integrating. Trigger when the user proposes a shadcn add, or when a fresh ShadCN-shaped file lands in apps/shade/src/components/ui.
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
material-ui-tailwind
Integrates Material UI with Tailwind CSS v4 using cascade layers (enableCssLayer, @layer order) and documents Tailwind v3 interoperability (preflight, important, injectFirst, portals). Use when combining MUI with Tailwind utilities, slotProps className, or theme token bridges.
author-component
Create or review Blazor components (.razor files) with correct architecture. USE FOR: writing new Blazor components that do NOT involve JavaScript interop, implementing parameters and EventCallback, RenderFragment slots, component lifecycle (OnInitializedAsync, OnParametersSet), async patterns, IAsyncDisposable…
obsidian-layout-adjustment
Workflow for working with the user on changing how Obsidian looks using CSS snippets. Use this whenever the user asks to restyle Obsidian, tune a vault's visual layout, adjust tabs, sidebars, note surfaces, properties, backlinks, graph panes, file explorer rows, icons, links, shadows, active states, or CSS snippets.…