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 VKirill/claude-lane-stack --skill design-tastegit clone --depth 1 https://github.com/VKirill/claude-lane-stackWrote 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/vkirill/claude-lane-stack/design-taste)<a href="https://agentmods.dev/skills/vkirill/claude-lane-stack/design-taste"><img src="https://agentmods.dev/badge/skills/vkirill/claude-lane-stack/design-taste/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/vkirill/claude-lane-stack/design-taste"><img src="https://agentmods.dev/badge/skills/vkirill/claude-lane-stack/design-taste.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.00117 | $0.01571 |
| Opus 5.5 | $0.00047 | $0.00628 |
| Sonnet 5.5 | $0.00023 | $0.00314 |
| Haiku 4.5 | $0.00012 | $0.00157 |
Grade A, and why
design-taste 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design taste
Lane adapter of taste-skill. It reviews landing pages, portfolios, and redesigns, and guides isolated branded mockups. It does not write product UI, and it does not turn cabinets, admin screens, or data tables into landing pages.
Info (print and stop)
If $ARGUMENTS is info / справка, print this block verbatim, then stop:
design-taste — визуальный аудит и направление для изолированного макета.
1) Design read: kind / audience / job / vibe / evidence from the brief, screen and DESIGN.md.
2) Three dials: DESIGN_VARIANCE / MOTION_INTENSITY / VISUAL_DENSITY. Existing tokens win.
3) Evidence audit: type, color, layout/rhythm, assets, states, motion, a11y.
4) Preflight: every finding has evidence, impact and an owner.
Агент: design-lead MODE=audit или MODE=mockup
Чинить: UI-ран после «делай»
Роутер: /lane-stack:web-design info
Design read (before the checklist)
Read the brief, requested route or screenshot, relevant DESIGN.md, current
components, and the project's stack before judging taste. Identify:
- page kind and user job (landing, portfolio, editorial, redesign, cabinet);
- audience, references, vibe, brand assets, tokens, and existing component language;
- accessibility, responsive, performance, and product constraints.
Write one line: Reading this as: <kind> for <audience>, serving <job>, with a <vibe> language, using evidence from <paths/screenshots>.
For an existing UI, describe what is already true before proposing change.
Preserve information architecture, working accessibility patterns, and the
project's brand unless the brief asks for a change. If evidence is missing,
write DEGRADED: <missing evidence> and make the smallest safe recommendation.
Ask one question only when two plausible design reads would lead to different work.
Three dials
Use the existing DESIGN.md reading when it exists. Otherwise choose a starting
range from the brief; these are review dials, not quotas:
What ships with it
1 file 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 · +56 lines · +18 tokens per session 9c202eb38bb2
- 1mo ago First seen · 75 lines · 99 tokens per session scan A 1d54fd926a31
design-taste is a skill published in the GitHub repository VKirill/claude-lane-stack (125 stars, last pushed 5d ago), licensed MIT. It adds 117 tokens to every session and 1,571 once invoked, about $0.0005 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-09-11.
Other skills, from other repositories
brand-tokens
A reference library of visual design rules for well-known brands, including colors, fonts, corner shapes, and explanations of each brand's visual style. Design tokens are reusable values that keep an interface's appearance consistent.
ui-aesthetic
A set of visual design rules for making web pages and components look consistent and readable. It covers icons, colors, typography, spacing, text, accessibility contrast, layout, and restrained animation.
creation-flow-prototype
A workflow for creating an interactive prototype before building a medium-sized or larger project with a user interface. It uses the prototype to confirm what the product should look and do like.
web-stylebook-design
Improve existing frontend UIs using researched design judgment, actual edits, verification, and before/after reporting. Also supports explicitly requested reviews and new visual directions.
amby-design
Design the UI — wireframes, component specs, and design tokens — with a sign-off gate.
republic-design
Republic-style UX design reviewer and scorer for pitch decks, landing pages, and investor-facing materials. Applies Republic.com's design DNA (financial-grade trust, data-forward, restrained elegance) to score and improve any visual artifact. Use when user says "republic", "republic style", "score design", "polish…