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 JansenAnalytics/claudex --skill frontend-designgit clone --depth 1 https://github.com/JansenAnalytics/claudexWrote 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/jansenanalytics/claudex/frontend-design)<a href="https://agentmods.dev/skills/jansenanalytics/claudex/frontend-design"><img src="https://agentmods.dev/badge/skills/jansenanalytics/claudex/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.00026 | $0.02459 |
| Opus 5 | $0.00013 | $0.01229 |
| Sonnet 5 | $0.00005 | $0.00492 |
| Haiku 4.5 | $0.00003 | $0.00246 |
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 3d 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 — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Design Skill
Based on Anthropic's Frontend Aesthetics research. Adapted for OpenClaw with practical tooling additions.
Core Principle
You tend toward generic, "on distribution" output. In frontend design, this creates "AI slop": white backgrounds, purple gradients, Inter font, predictable card layouts. Fight this instinct. Every frontend should feel like a human designer made deliberate, bold choices.
Design Thinking (BEFORE writing any code)
Before coding, commit to a clear aesthetic direction:
- Purpose: What problem does this interface solve? Who uses it?
- Tone: Pick a BOLD direction — don't hedge:
- Brutally minimal / Swiss design
- Maximalist chaos / Memphis Group
- Retro-futuristic / Cyberpunk
- Organic / Natural / Earthy
- Luxury / Refined / Editorial
- Playful / Toy-like / Rounded
- Industrial / Utilitarian / Terminal
- Art Deco / Geometric
- Soft / Pastel / Dreamy
- Dark mode / Moody / Cinematic
- Japanese / Scandinavian minimalism
- Newspaper / Magazine editorial
- Brutalist / Raw HTML energy
- Differentiation: What's the ONE thing someone will remember about this?
- Constraints: Framework (React/Vue/vanilla), performance, accessibility needs
Write down your aesthetic direction before coding. This prevents drift back to defaults.
Typography
NEVER use: Inter, Roboto, Arial, system-ui, system fonts, or any default sans-serif.
DO use: Distinctive, characterful fonts from Google Fonts. Pair a display font with a body font:
| Display (headings) | Body (text) | Vibe |
|---|---|---|
| Syne | DM Sans | Modern tech |
| Playfair Display | Source Serif Pro | Editorial luxury |
| Archivo Black | Work Sans | Bold industrial |
| Fraunces | Outfit | Organic warmth |
| Instrument Serif | Instrument Sans | Refined minimal |
| Space Mono | Karla | Terminal/hacker |
| Unbounded | Figtree | Playful modern |
| Cormorant Garamond | Lato | Classic elegance |
| Bebas Neue | Barlow | Poster/display |
| JetBrains Mono | IBM Plex Sans | Developer tools |
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.
- 3d ago First seen · 222 lines · 26 tokens per session scan A 8411a93450b3
frontend-design is a skill published in the GitHub repository JansenAnalytics/claudex (5 stars, last pushed 2mo ago), licensed MIT. It adds 26 tokens to every session and 2,459 once invoked, about $0.0001 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
absolute-ui
Build polished, intentional UIs with concrete CSS/Tailwind values — typography, color, layout, spacing, dark mode, accessibility, animations, components. Encodes specific, opinionated rules with exact values, not vague advice. Covers buttons, cards, forms, tables, navigation, dashboards, landing pages, onboarding, and…
popular-web-designs
54 real design systems (Stripe, Linear, Vercel) as HTML/CSS.
designlang-tokens
Use when styling UI for cal.com — references the extracted design system tokens instead of inventing colors, spacing, or typography.
design-context-extract
Extract design DNA from app screenshots, live URLs, or screen recordings using Google Stitch — color palettes, typography, spacing tokens, component patterns, and motion specs as design-tokens.json or Tailwind config. Use when the user points to a screenshot, URL, or video and asks to extract or audit the design…
css-at-property
Use when implementing animated gradients, complex CSS transitions that involve custom property values, or building a typed design token system where custom property misuse should produce visible errors.
css-custom-properties
Use when reviewing stylesheets, component styles, and responsive behavior related to Use CSS custom properties for design tokens. Check the rendered layout across breakpoints and interaction states before proposing a fix.