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 ytvee-dev/webdev-agent-kit --skill frontend-design-directorgit clone --depth 1 https://github.com/ytvee-dev/webdev-agent-kitWrote 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/ytvee-dev/webdev-agent-kit/frontend-design-director)<a href="https://agentmods.dev/skills/ytvee-dev/webdev-agent-kit/frontend-design-director"><img src="https://agentmods.dev/badge/skills/ytvee-dev/webdev-agent-kit/frontend-design-director/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/ytvee-dev/webdev-agent-kit/frontend-design-director"><img src="https://agentmods.dev/badge/skills/ytvee-dev/webdev-agent-kit/frontend-design-director.svg" alt="Reviewed on agentmods" width="80" 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.00043 | $0.02238 |
| Opus 5.5 | $0.00017 | $0.00895 |
| Sonnet 5.5 | $0.00009 | $0.00448 |
| Haiku 4.5 | $0.00004 | $0.00224 |
Grade A, and why
frontend-design-director 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 — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Design Director
Purpose
Define a concrete, subject-grounded frontend design direction before implementation when a task requires visual judgment.
This skill prevents generic AI-generated UI by making deliberate choices about audience, single job, lead thesis, visual position, typography, color, layout, structure, motion, interface copy, and anti-template risks.
It does not implement code by default. It creates a Design Direction Contract that can be handed to frontend-layout-implementer and verified by frontend-visual-qa or frontend-quality-reviewer.
Design Lead Stance
Act as a design lead, not a style randomizer.
For supplied designs, establish fidelity constraints through
design-screenshot-spec before critique. Read
skills/design-screenshot-spec/references/product-behavior-review.md for unresolved visual or behavior choices.
Preserve observed design intent; recommendations, polish, and accessibility
deviations require user resolution before entering the implementation contract.
Creative guidance below shapes proposals only where the user requests design work.
- The page needs a point of view that fits this subject and audience.
- Take one real visual risk only when it can be justified.
- Spend boldness in one place and keep the rest disciplined.
- The hero or lead section must express the page thesis.
- Typography, structure, motion, and copy are design material, not filler.
- Structural devices such as numbers, dividers, badges, grids, and labels must encode meaning.
When To Use
Use this skill after prompt intent routing when the task is Standard Workflow or Deep Workflow and includes visual judgment.
Use this skill when the user asks to create, redesign, polish, critique, make distinctive, or define visual acceptance criteria for a rendered frontend surface.
When Not To Use
Do not use this skill for one small bug, one obvious type error, one direct file-scope edit, one isolated code refactor, purely technical debugging, UI library selection, package installation, or testing workflows.
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.
- 1mo ago Changed · +24 lines 74717f232d63
- 1mo ago First seen · 195 lines · 43 tokens per session scan A 1995466242a0
frontend-design-director is a skill published in the GitHub repository ytvee-dev/webdev-agent-kit (7 stars, last pushed 4d ago), licensed Apache-2.0. It adds 43 tokens to every session and 2,238 once invoked, about $0.0002 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-31.
Other skills, from other repositories
design-dna
Extract, define, and apply design DNA across three dimensions: design system (tokens), design style (qualitative feel), and visual effects (Canvas, WebGL, 3D, particles, shaders, scroll effects, etc.). Use this skill when: (1) a user wants to see the full 3-dimension design structure/schema, (2) a user provides…
harness-design
Quality harness for design-dna Phase 3 output with browser-based visual verification. After an agent generates a design from a Design DNA JSON + user content, this skill acts as a verification and scoring layer — collecting all page resources via console/network inspection, performing section-by-section screenshot…
hmi-design-full
Comprehensive ISA-101 design rules for Human Machine Interfaces in process automation, with detailed reference files covering color design, display hierarchy, navigation, alarms, human factors, performance, and lifecycle management. Use when designing, building, reviewing, or generating code for HMIs, control system…
hmi-design-light
ISA-101 design rules for Human Machine Interfaces in process automation, covering display hierarchy, color standards, alarm integration, navigation, and situation awareness. Use when designing, building, reviewing, or generating code for HMIs, control system displays, SCADA screens, operator dashboards, or industrial…
baoyu-diagram
Create professional, dark-themed SVG diagrams of any type — architecture diagrams, flowcharts, sequence diagrams, structural diagrams, mind maps, timelines, illustrative/conceptual diagrams, and more. Use this skill whenever the user asks for any kind of technical or conceptual diagram, visualization of a system…
understand-figma
Analyze a Figma file via the Figma REST API and generate an interactive design knowledge graph (pages, screens, components, component sets, instances, design tokens) with a kind:"design" dashboard.