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 event4u-app/agent-config --skill design-variationsgit clone --depth 1 https://github.com/event4u-app/agent-configWrote 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/event4u-app/agent-config/design-variations)<a href="https://agentmods.dev/skills/event4u-app/agent-config/design-variations"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/design-variations/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/event4u-app/agent-config/design-variations"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/design-variations.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.00046 | $0.01628 |
| Opus 5 | $0.00023 | $0.00814 |
| Sonnet 5 | $0.00009 | $0.00326 |
| Haiku 4.5 | $0.00005 | $0.00163 |
Grade A, and why
design-variations 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 3d 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 Variations
Produce multiple substantively distinct design variations so the user can reject what they don't want and combine what they do. One design is one bet; three variations surface preferences the user didn't know they had.
When to use
- The user asks for options, alternatives, "different takes", "show me a few" on hi-fi UI work (screen, component, flow, visual treatment).
- After a
wireframeround settled the structure and the user wants styled directions on top of it.
When NOT to use: structure/flow exploration before any styling decision →
wireframe (lo-fi, disposable). Selecting ONE
grounded direction without generating alternatives →
design-intelligence. Reviewing an
existing design → design-review.
Procedure
- Baseline. Confirm what is varied (screen / component / flow / visual
treatment), the existing design context (DESIGN.md, brand tokens, UI kit —
run
existing-ui-auditwhen the output lands in a real codebase, per theui-audit-gaterule), the count (default 3, ceiling 6), and the user's priority axis. - Pick 2–4 axes to vary across: visual treatment (tone, density, shadow, radius, type weight), layout (centered/asymmetric, single/multi-column, full-bleed/inset), interaction model (single page vs multi-step, modal vs inline), hierarchy (what is primary), tone (minimal/formal/playful/ editorial), component style. Map axes onto the project's Taste Dials (Variance/Motion/Density) where DESIGN.md defines them.
- Spec each variation BEFORE building — one line per variation naming
its distinct palette family, type pairing, and layout skeleton. Left
unspecified, variations converge on one default look; variety must be
designed, not hoped for. Ground palette/type picks via
design-intelligenceand emit values as tokens perdesign-tokens. - Build basic → bold. Variation 1 = by-the-book (matches existing patterns); variation 2 = refined (same structure, one or two dimensions pushed — often the actual pick); variation 3 = novel (genuinely different layout/metaphor/aesthetic, deliberately off-distribution). Cover both ends — an all-safe set wastes the round, an all-wild set ignores the brief.
- Substantive, not cosmetic. Two variations that differ only in button color or shadow opacity are one variation — drop and replace. Litmus: the user can articulate the difference between any two variations in one sentence.
- Present in a single file with tweak controls — never
v1.html/v2.html/v3.html. Structure-sharing variants toggle via CSS custom properties + a small floating "Tweaks" panel (3–8 controls: color picker, font/variant dropdown, density slider, section toggles, copy inputs); persist chosen values inlocalStorage. Structurally distinct variants render side-by-side with labels. Even unasked, expose 1–2 tweak axes by default. - Caption each variation (1–2 sentences naming the axis it flexes) and close with a recommendation — a designer offers an opinion; the user decides.
- Quality gate. Novel ≠ sloppy: run
lint_design_slopover the emitted file (every variation individually passes; a DESIGN.md-declared direction suppresses its flags) and honor the outward-artifact hygiene floor (Q13 indesign-antipatterns.md) — no workspace paths, skill/tool names, or generator traces in the markup. Final pass before delivery →design-review.
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.
- 3d ago Changed · +2 tokens per session df95f85302fa
- 7d ago First seen · 131 lines · 44 tokens per session scan A 1a2aa457319d
design-variations is a skill published in the GitHub repository event4u-app/agent-config (10 stars, last pushed today), licensed MIT. It adds 46 tokens to every session and 1,628 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-09-03.
Other skills, from other repositories
create-chatgpt-mockup
Render pixel-accurate ChatGPT mobile (iOS) screen mockups in light mode from a thread JSON. Supports user text bubbles, user image attachments, assistant markdown prose, citation chips, the OpenAI spiral logo, the Apps-SDK GPT chip in the composer, and three header styles (model-tag, plain title, "Get Plus"). Fixed…
ui-designer/design-system
A shared set of rules for a product’s visual design, covering colors, fonts, spacing, corner shapes, shadows, and animations.
excalidraw-architect
Choose and compose the right Excalidraw diagram - architecture, flowchart, sequence, state, ER, swimlane, process, timeline, quadrant, pyramid, venn, loop, gantt, bar, line, scatter, and more - using the excalidraw-architect-mcp server. Use whenever a reader would learn more from a picture than from prose, or when…
design-review
A review procedure for checking an HTML file against the melta UI design system, which is a set of rules for how an interface should look and behave.
ux-strategy
Connect design decisions to business outcomes through competitive analysis, opportunity mapping, Jobs to Be Done, outcome-driven discovery, value proposition design, and UX metrics. Shape product direction with strategic frameworks grounded in evidence.
card
When the user wants to design, optimize, or audit card layouts for content display. Also use when the user mentions "card layout," "card component," "card grid," "product cards," "template cards," "tool cards," "feature cards," "gallery cards," "integration cards," or "card design." For grids, use grid.