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 edgesparkhq/codex-plugins --skill edgespark-frontend-designgit clone --depth 1 https://github.com/edgesparkhq/codex-pluginsWrote 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/edgesparkhq/codex-plugins/edgespark-frontend-design)<a href="https://agentmods.dev/skills/edgesparkhq/codex-plugins/edgespark-frontend-design"><img src="https://agentmods.dev/badge/skills/edgesparkhq/codex-plugins/edgespark-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.00087 | $0.00893 |
| Opus 5 | $0.00044 | $0.00447 |
| Sonnet 5 | $0.00017 | $0.00179 |
| Haiku 4.5 | $0.00009 | $0.00089 |
Grade A, and why
edgespark-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 8d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- edgespark-frontend-design — 91% identical, 3 lines differ
How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
EdgeSpark Frontend Design
Use this skill to turn safe, average UI into deliberate visual design with strong hierarchy, clearer art direction, and higher content quality.
Consult design-principles.md for doctrine, asset strategy, implementation details, and anti-patterns. Load the sections relevant to your task.
Design Stack
Apply the design standard in layers instead of relying on one vague "make it modern" pass:
- Start with the base web system: context-first framing, 12-column structure, 8-point spacing, semantic tokens, responsive behavior, and WCAG 2.1 AA contrast.
- Add the aesthetic lift: softer neutral or premium palettes, asymmetrical composition, dramatic typography contrast, generous whitespace, refined textures, and stronger motion direction.
- Enforce the anti-generic bans from the reference before shipping.
This layering is what prevents the model from drifting into safe but mediocre frontend output.
Workflow
1. Frame the design
Before touching code, derive:
- user goal
- audience
- primary tasks
- key content types
- success metric
- emotional tone
- one unforgettable visual move
- visual thesis: one sentence describing mood, material, and energy
- content plan: hero, support, detail, final CTA when the task is a landing page or marketing surface
- interaction thesis: 2-3 specific motion ideas that change the feel of the page
Give each section one job, one dominant visual idea, and one primary takeaway or action.
Choose a concrete direction instead of a vague "modern" target. Pick an extreme that fits the product, such as editorial, luxury, industrial, playful, organic, brutalist, or retro-futuristic. Map a minimal user journey and reflect it in layout, hierarchy, and copy.
2. Diagnose weak UI before changing it
For redesign work, inspect the current UI and answer:
- are the colors visually fatiguing, cheap-looking, or too vibrant
- is the layout overly traditional, symmetrical, or monotonous
- what modern design elements are missing
- does the page feel static and need motion to come alive
- what is the current brand positioning and intended emotional experience
What ships with it
2 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.
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.
- 8d ago First seen · 93 lines · 87 tokens per session scan A 90e0287018d1
edgespark-frontend-design is a skill published in the GitHub repository edgesparkhq/codex-plugins (1 stars, last pushed 3mo ago), licensed MIT. It adds 87 tokens to every session and 893 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-31.
Other skills, from other repositories
frontend-specialist
A front-end development workflow for building or improving web pages, components, layouts, forms, dashboards, and responsive interfaces. It covers common tools and frameworks such as React, Vue, Next.js, Tailwind, and CSS.
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI).…
compose-creative-ui
A workflow for combining visual interface components and effects in an existing frontend while preserving its current design system and product identity. It covers component sources such as shadcn/ui, Magic UI, Radix, React Bits, and related tools.
implement-ui-interaction
A guide for implementing and testing frontend controls such as dialogs, menus, popovers, carousels, drag-and-drop, swiping, pinching, and other pointer, touch, keyboard, or focus interactions.
implement-ui-motion
A workflow for implementing motion and micro-interactions in an existing frontend. It covers CSS, the Web Animations API, View Transition API, Anime.js, Motion, and GSAP, including reduced-motion support.
build-design-system
A workflow for building or organising a design system: the shared rules, tokens, components, themes, and documentation used across an interface. It covers CSS variables, DTCG tokens, Style Dictionary, Storybook, dark mode, and gradual migration.