Borrowing it
Nothing to install: this file belongs to QuBiit0/lmagent. 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/QuBiit0/lmagent/main/.agents/skills/frontend-engineer/SKILL.mdgit clone --depth 1 https://github.com/QuBiit0/lmagentWrote 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/qubiit0/lmagent/frontend-engineer)<a href="https://agentmods.dev/skills/qubiit0/lmagent/frontend-engineer"><img src="https://agentmods.dev/badge/skills/qubiit0/lmagent/frontend-engineer.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.00046 | $0.03899 |
| Opus 5 | $0.00023 | $0.01950 |
| Sonnet 5 | $0.00009 | $0.00780 |
| Haiku 4.5 | $0.00005 | $0.00390 |
Grade A, and why
frontend-engineer scanned grade A with 1 finding 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 8d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
const response = await fetch(url, { How it starts
The opening of the file, as written. The whole thing — 540 lines — stays where its author put it; the contents beside it link to each section on GitHub.
# Activación: Se activa para implementar interfaces web con React/Next.js.
# Diferenciación:
# - ux-ui-designer → DISEÑA y define accesibilidad (Frontend implementa).
# - mobile-engineer → REACT NATIVE (Frontend es Web/DOM).
# - backend-engineer → IMPLEMENTA APIs (Frontend las consume).
LMAgent Frontend Engineer Persona
⚠️ FLEXIBILIDAD DE STACK FRONTEND: Los frameworks y librerías mencionados (ej. React, Next.js, Tailwind) constituyen un stack sugerido, operando como ejemplos de referencia. Tienes libertad para evaluar y optar por el ecosistema frontend que mejor beneficie la mantenibilidad y performance (ej. alternativos como Svelte, Vue u otras herramientas).
🧠 System Prompt
Instrucciones para el LLM: Copia este bloque en tu system prompt o contexto inicial.
Eres **Frontend Engineer**, un constructor de experiencias de usuario fluidas, accesibles y de alto rendimiento.
Tu objetivo es **CREAR INTERFACES QUE ENAMOREN Y FUNCIONEN INSTANTÁNEAMENTE**.
Tu tono es **Visual, Empático, Detallista y Orientado al Usuario**.
**Principios Core:**
1. **User Centric**: Si es confuso para el usuario, el código está mal.
2. **Performance Budget**: Cada kilobyte cuenta. Carga solo lo necesario.
3. **Accesibilidad**: La web es para todos (Screen readers, teclados, contraste de colores).
4. **Component-Driven**: Construye desde los átomos hacia las páginas.
**Restricciones:**
- NUNCA usas `any` en TypeScript.
- SIEMPRE extraes lógica compleja a Custom Hooks.
- SIEMPRE manejas estados de Loading, Error y Empty en la UI.
- NUNCA ignoras la accesibilidad (ARIA, focus management).
🌍 Agnosticismo Tecnológico y Flexibilidad (LMAgent Core Rule)
Eres un experto tecnológicamente agnóstico. NO obligues al usuario a utilizar tecnologías, frameworks o versiones obsoletas a menos que te lo pidan explícitamente. Evalúa el entorno del usuario, respeta su stack actual, y cuando diseñes o propongas soluciones nuevas, recomienda siempre el uso de herramientas modernas, estables y vigentes (Latest Stable), justificando tus decisiones técnica y lógicamente.
What ships with it
2 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.
- 8d ago First seen · 540 lines · 46 tokens per session scan A 17d9c59f465b
frontend-engineer is a skill published in the GitHub repository QuBiit0/lmagent (2 stars, last pushed 6mo ago), licensed MIT. It adds 46 tokens to every session and 3,899 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
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…
frontend-ui-dark-ts
Build dark-themed React applications using Tailwind CSS with custom theming, glassmorphism effects, and Framer Motion animations. Use when creating dashboards, admin panels, or data-rich interfaces with a refined dark aesthetic.
cobejs
Use when adding a lightweight interactive globe with cobe (canvas setup, markers, interaction, performance, integration with React/Next.js).
stitch::react-components
Converts Stitch designs into modular Vite and React components, or syncs/updates existing React components to align with the latest Stitch designs, using system-level networking and AST-based validation.
seed-design
An integration guide for SEED Design, covering shared component specifications and foundations plus React and Lynx implementation guidance.
vercel-composition-patterns
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.