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/evoelsewhere/evoflux/frontend-designnpx skills add evoelsewhere/evoflux --skill frontend-designgit clone --depth 1 https://github.com/evoelsewhere/evofluxWhat 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.00062 | $0.00546 |
| Opus 5 | $0.00031 | $0.00273 |
| Sonnet 5 | $0.00012 | $0.00109 |
| Haiku 4.5 | $0.00006 | $0.00055 |
Grade A, and why
frontend-design 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design and build a frontend
Make the interface specific to its subject, audience, and primary job. Preserve existing product conventions when editing an established application; novelty must not break usability or brand coherence.
State machine
1. FRAME
Identify the primary user, page or flow job, content hierarchy, required states, platform constraints, existing design system, and supplied visual direction. Choose non-blocking details from context. Ask only when missing assets, brand rules, or incompatible interpretations would materially change the result.
2. DIRECT
Write a compact design contract before implementation:
- 4–6 color tokens with semantic roles;
- display, body, and utility type roles;
- layout/grid behavior across desktop and mobile;
- interaction and motion principles;
- one subject-specific signature element;
- accessibility requirements and reduced-motion behavior.
Reject choices that could be reused unchanged for any product. Structural devices, imagery, copy, and motion must communicate something true about the subject. Spend visual boldness in one place and keep surrounding elements disciplined.
3. BUILD
Use repository-native components, tokens, routing, state, and dependencies. Implement real content and all relevant loading, empty, error, disabled, hover, focus, and success states. Keep control labels action-oriented and consistent through the flow. Avoid decorative grids, gradients, cards, numbering, and animation unless they serve the hierarchy or interaction.
Preserve semantic HTML, keyboard navigation, visible focus, contrast, target sizes, responsive reflow, and reduced motion. Check CSS specificity and avoid local rules that silently cancel shared component behavior.
4. VERIFY
Run the repository's narrow checks, then inspect the rendered interface at representative desktop and mobile sizes. Exercise keyboard navigation and the main interaction path. Compare the render with the design contract and correct generic styling, clipping, overflow, unreadable density, broken states, and unnecessary decoration.
What ships with it
3 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.
- 2d ago First seen · 68 lines · 62 tokens per session scan A 7ac22882172f
frontend-design is a skill published in the GitHub repository evoelsewhere/evoflux (5 stars, last pushed 6d ago), licensed Apache-2.0. It adds 62 tokens to every session and 546 once invoked, about $0.0003 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-system
Audit, document, or extend your design system. Use when checking for naming inconsistencies or hardcoded values across components, writing documentation for a component's variants, states, and accessibility notes, or designing a new pattern that fits the existing system.
frontend-design-saas
S-tier SaaS dashboard and product UI reference. Use this skill when building application shells, data tables, settings panels, billing pages, dashboards, auth flows, admin tools, or any internal/customer-facing SaaS product UI. Inspired by Stripe, Linear, Vercel, Airbnb, Notion. Covers neutral-led design tokens…
frontend-design
Produce intentional, responsive, accessible UI work and perform visual QA instead of generic component assembly.
openbot-screen-layout
The default layout for every OpenBot configuration screen — PageShell and its prose/wide widths, PageSection and PageRows, Item row composition, the settings-row pattern where a summary and a chevron open a dialog, and the size and variant vocabulary. This is what a new screen looks like unless an instruction says…
web-design
Penguin visual language for generated web pages and app UIs — GitHub-style simplicity with a single blue accent, light and pure-black dark themes, design tokens, component and chat-interface recipes, plus an opt-in warm paper editorial theme.
gsap-scrolltrigger
Official GSAP skill for ScrollTrigger — scroll-linked animations, pinning, scrub, triggers. Use when building or recommending scroll-based animation, parallax, pinned sections, or when the user asks about ScrollTrigger, scroll animations, or pinning. Recommend GSAP for scroll-driven animation when no library is…