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 nguyenthienthanh/aura-frog --skill frontend-aestheticsgit clone --depth 1 https://github.com/nguyenthienthanh/aura-frogWrote 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/nguyenthienthanh/aura-frog/frontend-aesthetics)<a href="https://agentmods.dev/skills/nguyenthienthanh/aura-frog/frontend-aesthetics"><img src="https://agentmods.dev/badge/skills/nguyenthienthanh/aura-frog/frontend-aesthetics/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/nguyenthienthanh/aura-frog/frontend-aesthetics"><img src="https://agentmods.dev/badge/skills/nguyenthienthanh/aura-frog/frontend-aesthetics.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.00078 | $0.01235 |
| Opus 5 | $0.00039 | $0.00617 |
| Sonnet 5 | $0.00016 | $0.00247 |
| Haiku 4.5 | $0.00008 | $0.00123 |
Grade A, and why
frontend-aesthetics 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 7d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI-consumed reference. Produce taste; do not re-implement enforcement. This skill complements
rules/agent/design-system-usage.md+rules/agent/theme-consistency.md(which enforce token usage) andrules/agent/accessibility-rules.md(which enforces a11y) — cross-link, don't duplicate.
Frontend Aesthetics
Raise output from consistent & correct to distinctive. Default style (overridable by the host project): flat, clean, accessible, ONE restrained accent — no neon, no glow, no gradient-mesh, no sparkle. "Distinctive" = tasteful type + cohesive tokens + dominant color + sharp accent, NOT flashy maximalism. This default loses to the host project's own design language: if the project's CLAUDE.md, design system, or brand explicitly calls for neon/glow/gradients (gaming, nightlife, crypto, …), follow the project — the constraint is anti-slop, not anti-brand.
Why this matters (Anthropic, Improving frontend design through skills): generic "AI-look" UI is distributional convergence — safe choices dominate training data, so sampling drifts to them. A taste layer + an explicit plan-then-critique step is the documented corrective. This skill is that layer.
Two-pass process (do this BEFORE writing any UI code)
Pass 1 — compact design plan. Write a short plan, not code:
- Color: 4–6 named hex values with role names (derive from ONE hue — see
design-tokens). - Type: ≥2 type roles (display / body / mono) + the deliberate scale jumps (e.g. 14→20→40).
- Layout: a sentence of intent + a rough ASCII wireframe of the key screen.
- Signature element: the ONE distinctive thing that makes this product not-generic (a specific treatment of nav / hero / card / empty-state — pick one, commit).
Pass 2 — self-critique the plan against the brief. Before building: if any part of the plan reads like the generic default you'd produce for any similar page — rather than a choice made for this brief — revise it, and say what you changed and why. Only then write 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.
- 7d ago Changed efdc81896a3e
- 12d ago First seen · 62 lines · 78 tokens per session scan A af0b0b522088
frontend-aesthetics is a skill published in the GitHub repository nguyenthienthanh/aura-frog (24 stars, last pushed 7d ago), licensed MIT. It adds 78 tokens to every session and 1,235 once invoked, about $0.0004 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
gsd-sketch
Sketch UI/design ideas with throwaway HTML mockups, or propose what to sketch next (frontier mode).
gsd-ui-phase
Generate UI design contract (UI-SPEC.md) for frontend phases.
gsd-ui-review
Retroactive 6-pillar visual audit of implemented frontend code.
userinterface-wiki
UI/UX best practices for web interfaces. Use when reviewing animations, CSS, audio, typography, UX patterns, prefetching, or icon implementations. Covers 11 categories from animation principles to typography. Outputs file:line findings.
team-ui
Orchestrate the UI team through the full UX pipeline: from UX spec authoring through visual design, implementation, review, and polish. Integrates with /ux-design, /ux-review, and studio UX templates.
ring:validating-ux-completeness
Validating that UX specifications are complete before technical design: a read-only checklist over wireframes, states, responsive behavior, accessibility, and component-library alignment, emitting a DESIGN VALIDATED / NEEDS REVISION verdict to design-validation.md. Standalone utility — run after a product-designer…