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 agentmods add skills/datit309/supergraph/frontend-designnpx skills add datit309/supergraph --skill frontend-designgit clone --depth 1 https://github.com/datit309/supergraphWhat 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 | $0.00077 | $0.00673 |
| Opus 5 | $0.00039 | $0.00336 |
| Sonnet 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 2d 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:webapp-testingto 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.
- 2d ago First seen · 57 lines · 77 tokens per session scan A 52c912d0f6d6
frontend-design is a skill published in the GitHub repository datit309/supergraph (21 stars, last pushed 4d ago), licensed MIT. It adds 77 tokens to every session and 673 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
playwright-cli
Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or…
migrate
Inventory an existing spec-driven project and apply bounded migrations to jig defaults: report, adopt-layout, rename-decisions, split-slices, slice-to-spec, seed-decisions, and copy-machinery. Use when the user says migrate this project to jig, adopt jig here, this repo already has specs — set up jig, scaffold-init…
adr-workflow
Scaffold, accept, index, and link Architectural Decision Records (ADRs). Use when the user says "write an ADR", "record this decision", "resolve [deferred item] with an ADR", "supersede ADR-NNNN", or otherwise wants to capture a hard-to-reverse decision in docs/decisions/. Also use when a refinement-todo entry needs…
bug-fix
Drive the teeth-gated lifecycle for reported defects: diagnose root cause, prove it, and prevent regression through REPORTED → DIAGNOSING → ROOTCAUSED → FIXING → REVIEWED → DONE, with VERIFIED, ESCALATED, and RESOLVEDONMAIN paths where needed. Auto-fires on fix this bug, debug this, root-cause this, this regressed…
analyze
Cross-artifact consistency report for jig specs — a non-destructive six-category audit at CRITICAL/HIGH/MEDIUM/LOW severity, covering duplication, ambiguity, underspecification, principle violations, coverage gaps, and terminology drift. Auto-triggers when you say analyze this spec, check for inconsistencies, audit…
arch-review
Team baseline for architecture, design-doc, and RFC review — produces summary, strengths, concerns, and open questions. Auto-triggers when you say review this design, review this architecture, review this proposal, review my RFC, poke holes in this proposal, is this design sound, or critique this tech spec. Defers to…