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 skills add vadimcomanescu/codex-skills --skill frontend-designgit clone --depth 1 https://github.com/vadimcomanescu/codex-skillsWrote 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/vadimcomanescu/codex-skills/frontend-design)<a href="https://agentmods.dev/skills/vadimcomanescu/codex-skills/frontend-design"><img src="https://agentmods.dev/badge/skills/vadimcomanescu/codex-skills/frontend-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.00048 | $0.01765 |
| Opus 5 | $0.00024 | $0.00882 |
| Sonnet 5 | $0.00010 | $0.00353 |
| Haiku 4.5 | $0.00005 | $0.00177 |
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 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.
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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Design
Build memorable, functional interfaces with a clear point-of-view (no generic templates). Commit to one aesthetic direction, define tokens, ship accessible + responsive UI, and keep changes scoped.
Preferred Targets (choose the best fit)
- Next.js (TypeScript): preferred for production app/marketing routes and design system work.
- React (TypeScript): preferred for SPA/component libraries outside Next.js.
- Vanilla HTML/CSS/JS: great for static demos, prototypes, and standalone embeds.
Quick Start (do this first)
- Ask up to 4 questions:
- What user and job-to-be-done (what should feel “easy” after the change)?
- Where does it live (component/route) and what stack? Prefer Next.js/React; vanilla is fine for standalone pages or prototypes.
- In Next.js: assume App Router (
app/). Any server/client constraints? - Any hard constraints (brand tokens, light/dark, motion limits, must-keep UI parts, perf budgets)?
- Pick an aesthetic direction + one signature move. If vague, propose 2–3 options from
references/aesthetic-playbook.md. - Define tokens (type, palette, spacing, radius, shadows, motion). Keep accents to 1–2.
- Build structure first (semantic markup + layout), then motion, then polish + QA.
Guardrails (avoid footguns)
- Keep scope tight: redesign only what the user asked for.
- Reuse existing tokens/components if working in an existing repo; do not introduce a new global styling system unless requested.
- Match complexity to the vision: refined minimalism needs restraint; maximalism needs deliberate structure (not random decoration).
- Respect
prefers-reduced-motionfor all animations. - Avoid “AI slop” defaults. If the repo already uses a generic font, keep it unless the user explicitly wants new typography.
- Enforce token semantics: error/success/warning colors are for meaning, not decoration; keep contrast accessible in light/dark.
- Default to shipping code that is easy to maintain: small components, clear hierarchy, minimal dependencies.
- Don’t add new packages (animation libs, UI kits, icon sets) unless the user explicitly asks or the repo already uses them.
- Default to one primary CTA per view; demote the rest (secondary/tertiary) to avoid competing actions.
What ships with it
19 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.
- assets/nextjs-app-router-starter/app/globals.css 1.5 KB
- assets/nextjs-app-router-starter/app/layout.tsx 422 B
- assets/nextjs-app-router-starter/app/page.module.css 4.4 KB
- assets/nextjs-app-router-starter/app/page.tsx 3.4 KB
- assets/nextjs-app-router-starter/components/AssistantRail.module.css 3.8 KB
- assets/nextjs-app-router-starter/components/AssistantRail.tsx 5.7 KB
- assets/nextjs-app-router-starter/README.md 465 B
- assets/react-component-starter/DesignPanel.module.css 3.8 KB
- assets/react-component-starter/DesignPanel.tsx 1.6 KB
- assets/vanilla-starter/index.html 5.0 KB
- assets/vanilla-starter/script.js 332 B runs code
- assets/vanilla-starter/style.css 8.0 KB
- LICENSE.txt 1.0 KB
- references/aesthetic-playbook.md 2.8 KB
- references/ai-native-ui-patterns.md 1.5 KB
- references/anti-patterns.md 1.0 KB
- references/implementation-patterns.md 2.4 KB
- references/react-next-best-practices.md 1.3 KB
- references/tokens-and-semantics.md 1.6 KB
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 · 111 lines · 48 tokens per session scan A 0d3b665df0fe
frontend-design is a skill published in the GitHub repository vadimcomanescu/codex-skills (24 stars, last pushed 7mo ago), licensed MIT. It adds 48 tokens to every session and 1,765 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-08-30.
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…
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ralph with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
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.
reveal-hover-effect
Build cursor-following spotlight reveals that expose a second aligned image through a soft radial mask. Use for hover-to-color, before-and-after, x-ray, material, texture, product-detail, and illustrated hero effects where a desaturated or embossed base image should remain visible while another treatment follows an…
frontend-visual-qa
Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…
better-colors
Helps you build a color system and answer anything about color in your project. You can generate palettes, use semantic tokens, convert between formats, check contrast and more.