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-intelligencegit 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-intelligence)<a href="https://agentmods.dev/skills/ytvee-dev/webdev-agent-kit/frontend-design-intelligence"><img src="https://agentmods.dev/badge/skills/ytvee-dev/webdev-agent-kit/frontend-design-intelligence/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-intelligence"><img src="https://agentmods.dev/badge/skills/ytvee-dev/webdev-agent-kit/frontend-design-intelligence.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.00039 | $0.01307 |
| Opus 5.5 | $0.00016 | $0.00523 |
| Sonnet 5.5 | $0.00008 | $0.00261 |
| Haiku 4.5 | $0.00004 | $0.00131 |
Grade A, and why
frontend-design-intelligence 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Design Intelligence
Purpose
Create a compact design intelligence brief before visual direction when a UI task needs product-category grounding, page-pattern choice, density decisions, or domain-specific anti-pattern checks.
This skill adapts design-system reasoning into the WebDev Agent Kit model without becoming a UI framework, CLI generator, or package installer.
When To Use
Use after prompt intent routing when the task is Standard Workflow or Deep Workflow and one or more are true:
- product type, page type, audience, or user job is vague;
- the user asks for visual style, landing structure, dashboard structure, or distinctive UI direction;
- the page needs visual variance, motion, or density decisions;
- inspected designs leave transitions, forms, states, or product behavior unclear;
frontend-design-directorneeds better grounding before writing a Design Direction Contract.
When Not To Use
Do not use for Fast Lookup, tiny edits, purely technical bugfixes, code implementation, live Figma inspection, package installation, or new styling systems.
Required Context
- Read
AGENTS.md. - Read
common/prompt-intent-routing-rules.mdwhen workflow level is unclear. - Read relevant project overlays when present.
- Read only relevant references from this skill:
references/product-pattern-matrix.md;references/design-dials.md;references/product-anti-patterns.md.
- Read supplied screenshots, briefs, inspect notes, or existing route files only when they materially affect the brief.
- Read
skills/design-screenshot-spec/references/product-behavior-review.mdwhen reviewing flows or unresolved product/design decisions. If supplied visual sources have not been inspected, usedesign-screenshot-specfirst.
Tool Contract
- May read project overlays and relevant source files.
- Must not run design generators or external CLIs.
- Must not create or edit app source code.
- Must not create a global design system unless explicitly requested, and then only inside
.agents/project/**. - Delegate live source acquisition to
design-screenshot-spec; consume its component evidence and report missing coverage before product review.
What ships with it
4 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 · +18 lines · -6 tokens per session 7e548a176b24
- 1mo ago First seen · 127 lines · 45 tokens per session scan A e9072953fb9f
frontend-design-intelligence 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 39 tokens to every session and 1,307 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.