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/ytvee-dev/webdev-agent-kit/frontend-design-intelligencenpx skills add ytvee-dev/webdev-agent-kit --skill frontend-design-intelligencegit clone --depth 1 https://github.com/ytvee-dev/webdev-agent-kitWhat 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.00045 | $0.01055 |
| Opus 5 | $0.00023 | $0.00528 |
| Sonnet 5 | $0.00009 | $0.00211 |
| Haiku 4.5 | $0.00005 | $0.00105 |
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 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 — 127 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;
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.
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/**. - Must not use Figma MCP.
Workflow
- Identify product category, audience, page type, and single job.
- If required facts are missing, infer the smallest useful assumption and label it.
- Select a likely page pattern from the user job, not from a generic style catalog.
- Set design dials: visual variance, motion intensity, and information density.
- Identify domain UX risks.
- Identify product-specific anti-patterns and generic template risks.
- Produce a compact Design Intelligence Brief.
- Hand off to
frontend-design-directorwhen visual direction is needed.
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.
- 2d 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 (5 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 45 tokens to every session and 1,055 once invoked, about $0.0002 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
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…
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…
shipping-reproducible-results
Package completed data analysis and ML work so an independent recipient can reproduce the claimed results, verify artifact lineage, and operate the handoff within its stated scope. Use when finalizing a project, study, model package, or review bundle; not for deploying to a live system.
actions-reusable-workflows
Wire a repository to the bitwise-media-group/github-workflows reusable workflows — thin, SHA-pinned caller workflows for CI, security (CodeQL) scanning, release (release-please/GoReleaser/Zensical docs), the signature-preserving fast-forward /merge + merge-review-ack + merge-notice flows, and add-to-project — plus the…
go-style
Modern Go code style for stdlib-first programs — error wrapping with %w, sentinel errors, structured logging with log/slog, context threading, consumer-defined interfaces, nil-safe constructors, net/http servers with method-pattern routing, flag/env configuration for services, and cobra commands with viper…
workflow-skill-evals
Write the evolve evaluation suite for an agent skill: its triggers (triggers.json — Tier 1 activation tests) and behavioral evals (evals.json — Tier 2 task tests), under evals/ /. Use when asked to generate, write, author, scaffold, or balance an eval suite, evals, or triggers for a skill; to create or edit a…