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 irahardianto/awesome-agv --skill frontend-designgit clone --depth 1 https://github.com/irahardianto/awesome-agvWrote 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/irahardianto/awesome-agv/frontend-design)<a href="https://agentmods.dev/skills/irahardianto/awesome-agv/frontend-design"><img src="https://agentmods.dev/badge/skills/irahardianto/awesome-agv/frontend-design/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/irahardianto/awesome-agv/frontend-design"><img src="https://agentmods.dev/badge/skills/irahardianto/awesome-agv/frontend-design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00067 | $0.02241 |
| Opus 5.5 | $0.00027 | $0.00896 |
| Sonnet 5.5 | $0.00013 | $0.00448 |
| Haiku 4.5 | $0.00007 | $0.00224 |
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 1mo 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Design Skill
This skill guides creation of distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics. Follow the phased workflow below. Each phase has concrete reference material — use it, don't invent from scratch.
Phased Workflow
Phase 1: Design Direction
Before touching any code, commit to a clear aesthetic direction. Answer these:
Context questions:
- What problem does this interface solve? Who uses it?
- What's the one thing someone will remember about this design?
- What aesthetic direction fits? (Choose ONE — don't blend randomly)
Aesthetic directions to pick from: Brutally minimal · Maximalist chaos · Retro-futuristic · Organic/natural · Luxury/refined · Playful/toy-like · Editorial/magazine · Brutalist/raw · Art deco/geometric · Soft/pastel · Industrial/utilitarian · Sci-fi/cyberpunk
CRITICAL: Every generation must make a fresh choice. Never default to the same direction twice. Vary light/dark themes, fonts, and palettes across generations.
Deliverables from Phase 1:
- ✓ Named aesthetic direction (e.g., "editorial luxury, dark theme")
- ✓ Font pairing selected from
references/typography.md - ✓ Color palette selected from
references/color-palettes.md - ✓ Layout composition(s) selected from
references/layout-compositions.md
Phase 2: Token System
Set up the design token foundation before writing any component code.
- Copy
examples/design-tokens.cssinto the project - Override the palette primitives with your chosen palette's HSL values
- Override
--font-displayand--font-bodywith your chosen font pairing - Add the Google Fonts
@importto your HTML<head>(with preconnect hints)
<!-- Always preconnect BEFORE the font stylesheet -->
<link rel="preconnect" href="https://fonts.googleapis.com">
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
<link rel="stylesheet" href="[your @import from typography.md]">
Deliverables from Phase 2:
- ✓
design-tokens.css(or equivalent) in place with chosen palette/fonts - ✓ All colors, spacing, typography, shadows, and motion defined as CSS variables
- ✓ No hardcoded color values or magic numbers anywhere in component code
What ships with it
11 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.
- examples/design-tokens.css 18 KB
- frameworks/html-css.md 11 KB
- frameworks/vue.md 11 KB
- references/color-palettes.md 11 KB
- references/frontend-layout.md 6.9 KB
- references/layout-compositions.md 9.2 KB
- references/mobile-responsive.md 20 KB
- references/motion-patterns.md 12 KB
- references/pwa-checklist.md 23 KB
- references/typography.md 16 KB
- scripts/visual-audit.sh 18 KB runs code
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.
- 1mo ago First seen · 175 lines · 67 tokens per session scan A d4479f0d6ac1
frontend-design is a skill published in the GitHub repository irahardianto/awesome-agv (156 stars, last pushed 13d ago), licensed MIT. It adds 67 tokens to every session and 2,241 once invoked, about $0.0003 per session on Opus 5.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
02-设计规范
A set of standards for designing public web interfaces, including layout, colors, typography, interaction states, animation, and accessibility.
common-ui-design
Design distinctive, production-grade frontend UI with bold aesthetic choices. Use when building web components, pages, interfaces, dashboards, or applications in any framework (React, Next.js, Angular, Vue, HTML/CSS).
03-组件规范
A set of rules and reference materials for building reusable user-interface components such as buttons, forms, charts, dialogs, tabs, and status labels. It covers web, mobile, mini-program, and external-facing interfaces, with a separate standard for admin panels.
product-ux-quality
Making software feel finished — UI states, forms, mobile, errors users can act on, accessibility, and the polish gap between "works" and "quality product". Use when building any user-facing screen or flow, reviewing UX, handling forms/validation, or when the user says "polish", "UX", "user experience", "looks…
ui-web
Web UI - glassmorphism, Tailwind, dark mode, accessibility.
frontend-ui-ux-system
A company-level guide for designing web interfaces and user experiences. It covers visual styles, design tokens (named values for colors, spacing, and typography), layout, interaction, accessibility, motion, and review checks.