Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/event4u-app/agent-confignpx agentmods add skills/event4u-app/agent-config/fe-designWrote 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/event4u-app/agent-config/fe-design)<a href="https://agentmods.dev/skills/event4u-app/agent-config/fe-design"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/fe-design.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.00045 | $0.03626 |
| Opus 5 | $0.00023 | $0.01813 |
| Sonnet 5 | $0.00009 | $0.00725 |
| Haiku 4.5 | $0.00005 | $0.00363 |
Grade A, and why
fe-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 yesterday.
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 — 265 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Design Skill
Ad-hoc mode — outside the engine, YOU run this loop now
One question decides which mode you are in: is a /implement-ticket run
dispatching this?
| Situation | Who owns the UI write | This skill is |
|---|---|---|
| A ticketed run — the UI directive set is dispatching | directives/ui/* |
a reference it cites |
| Anything else — "build me the page", "improve this form", "implement the approved design" | you, in this turn | the executor |
| A renderer axis is in play — WebGL / Three.js / canvas / scroll-scrubbed video | still you — the renderer is a grounding question, not a second executor | the executor, grounded via search_stack |
The third row is an axis, not an owner. Renderer selection resolves through
machinery that already exists: search_stack in
corpus-grounding
(scripts/decision_engine.ts), whose stack corpus carries threejs.csv among
its stacks, read beside the register in
design-intelligence
§ Register. No second frontend executor is declared, and none is needed: a
renderer changes what you ground against, never who writes the UI.
Outside the engine, nothing else owns the design quality of a UI write. Reading this skill and then writing the UI from priors is the failure it exists to prevent — the loop below is not optional context, it is the work.
Skip only when the change is ui-trivial, decidable off the diff: ≤ 1 file,
≤ 5 changed lines, no new component, no new state, no new dependency. Anything
else runs the loop.
The loop
- Audit first — run
existing-ui-audit. What already exists (components, tokens, layout conventions) outranks every heuristic below. Reinventing an existing component is the #1 failure mode. - Brief — cover the same five keys the engine requires before any code:
layout,components,states,microcopy,a11y.statesmeans all five ofempty,loading,error,success,disabled— a brief missing one is unfinished, not concise. - Inventory — only when an artifact was provided, and before you build.
List the artifact's interactions, keyframes, and script includes from its
source (
design-fidelity-mechanics§ Data-basis ladder — read it, do not look at a picture of it). Then place every listed item in exactly one bucket, using the engine's own names (apply.ts,COVERAGE_BUCKETS) so the two surfaces read the same. Nothing enforces that they stay the same — this is a copied vocabulary, not a shared constant, and no test pins it; renaming a bucket in the engine leaves this list stale and silent:
What ships with it
5 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.
- yesterday Changed · +3 lines 97b4b77b3dd6
- 3d ago First seen · 262 lines · 45 tokens per session scan A bc2e67a2bb91
fe-design is a skill published in the GitHub repository event4u-app/agent-config (10 stars, last pushed today), licensed MIT. It adds 45 tokens to every session and 3,626 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
frontend-ui-engineering
Builds production-quality, accessible, responsive user-facing UIs. Use when building or modifying interfaces and pages, creating components, implementing layouts, meeting WCAG accessibility requirements, managing state, or when the output needs to look and feel production-quality rather than AI-generated.
brand-landingpage
Brand-first landing page designer — runs a brand-identity interview (colors, typography, shape language), then generates and iterates on a polished landing page via Stitch with deployment-ready HTML. Use when the user asks to create, design, or build a landing page, homepage, or marketing page and has no established…
21st-ui
Find, install, and generate UI with 21st.dev. Use when the user asks for a UI component (pricing table, hero, navbar, dashboard, form, etc.), wants design inspiration, needs a brand logo as an SVG component, or wants to generate new UI from a prompt.
tailwind-design-system
Build scalable design systems with Tailwind CSS v4, design tokens, component libraries, and responsive patterns. Use when creating component libraries, implementing design systems, or standardizing UI patterns.
interaction-skill
Layer A interaction-mechanics reference anchored to the beui.dev catalog. Stacks on any style skill whenever work adds or changes motion or interaction — micro-interactions, animated components, transitions, gestures, hover/press/state feedback, loading/success/error morphs, 'make it feel alive'. Mandates reading the…
layout-skill
Layer A layout-mechanics reference. Stacks on any style skill when the screen is an app shell, dashboard, settings, list-detail, mail/inbox, or any layout with fixed regions plus a scrolling body — or when a layout breaks under long, empty, or unbroken content. Owns spatial structure and scroll ownership; owns zero…