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 datit309/supergraph --skill frontend-designgit clone --depth 1 https://github.com/datit309/supergraphWrote 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/datit309/supergraph/frontend-design)<a href="https://agentmods.dev/skills/datit309/supergraph/frontend-design"><img src="https://agentmods.dev/badge/skills/datit309/supergraph/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/datit309/supergraph/frontend-design"><img src="https://agentmods.dev/badge/skills/datit309/supergraph/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.00077 | $0.00673 |
| Opus 5.5 | $0.00031 | $0.00269 |
| Sonnet 5.5 | $0.00015 | $0.00135 |
| Haiku 4.5 | $0.00008 | $0.00067 |
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 12d 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics. Implement real working code with exceptional attention to aesthetic detail and creative choices.
Announce: "🎨 /supergraph:frontend-design — designing [component/page]..."
When to Use
- User asks to build a component, page, application, landing page, dashboard, or any web UI
- Styling or beautifying an existing interface
- Creating HTML/CSS/JS, React, Vue, or any frontend artifact
Steps
1. Understand context
Clarify if needed: purpose, target audience, technical constraints (framework, existing design system). Do NOT start coding yet.
2. Commit to a bold aesthetic direction
Before coding, decide:
- Tone — pick an extreme: brutally minimal, maximalist, retro-futuristic, organic, luxury, editorial, brutalist, art deco, soft/pastel, industrial, etc.
- Differentiation — what is the one thing someone will remember about this UI?
- Constraints — framework, performance, accessibility requirements
CRITICAL: Choose a clear conceptual direction and execute it with precision. Bold maximalism and refined minimalism both work — the key is intentionality.
3. Implement
Produce working code (HTML/CSS/JS, React, Vue, etc.) that is:
- Production-grade and functional
- Visually striking and memorable
- Cohesive with a clear aesthetic point-of-view
- Meticulously refined in every detail
4. Handoff
Deliver the working code. If the user is in a supergraph workflow:
- Static component → no further steps needed
- Interactive feature →
/supergraph:browser-agentto verify UI behavior
Design Reference (condensed)
Purpose/Tone/Constraints/Differentiation — pick one bold direction (minimal/maximalist/retro/luxury/brutalist etc) and execute with precision.
Guidelines: distinctive typography (not Arial/Inter), cohesive CSS variables, CSS-only motion with staggered reveals, asymmetric/spatial composition, atmospheric backgrounds (gradients/noise/mesh/shadows). Avoid generic AI slop (purple gradients, cookie-cutter layouts). Match complexity to vision — maximalist = elaborate, minimal = precise.
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.
- 12d ago Changed 42acb0baf05b
- 1mo ago First seen · 57 lines · 77 tokens per session scan A 52c912d0f6d6
frontend-design is a skill published in the GitHub repository datit309/supergraph (23 stars, last pushed 5d ago), licensed MIT. It adds 77 tokens to every session and 673 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
icon-composer-app-icon-workflow
Design, preview, validate, and integrate Apple app icons with Icon Composer. Use when a task mentions Icon Composer, .icon documents, Liquid Glass app icons, ictool preview exports, app icon design for iOS, iPadOS, macOS, or watchOS, or guided Icon Composer GUI work through Computer Use.
apple-typography-workflow
Guide Apple platform typography decisions and implementation across SwiftUI Font, UIKit UIFont, AppKit NSFont, San Francisco system fonts, SF Pro, SF Compact, SF Mono, SF Pro Rounded, New York serif design, Dynamic Type, text styles, fontDesign, fontWeight, fontWidth, monospaced digits, custom font bundle integration…
apple-ui-accessibility-workflow
Guide Apple UI accessibility implementation and review for SwiftUI-first code, with UIKit and AppKit bridge guidance plus explicit verification expectations and testing handoffs. Use when the user wants help making Apple UI accessible, reviewing accessibility semantics, shaping the accessibility tree, or planning…
core-animation-layer-workflow
Guide Core Animation layer-backed rendering and animation decisions for Apple apps, including CALayer trees, layer-backed AppKit and UIKit views, SwiftUI bridges, implicit and explicit CAAnimation, CATransaction, CAMediaTiming, model versus presentation layers, shape, gradient, replicator, emitter, text, tiled, and…
sf-symbols-workflow
Guide SF Symbols selection, inspection, customization, rendering modes, variable color, symbol effects, animated symbols, custom symbols, accessibility semantics, availability checks, and Apple app integration. Use when a task mentions SF Symbols, the SF Symbols app, systemImage names, symbolRenderingMode…
macos-window-management-workflow
Design, implement, and validate SwiftUI and AppKit macOS window behavior. Use when choosing window scenes, toolbar or title-bar treatment, drag regions, placement, resizing, restoration, document or utility windows, and focused window ownership.