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 AnmarHani/SwarmVault --skill swarm-design-uigit clone --depth 1 https://github.com/AnmarHani/SwarmVaultWrote 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/anmarhani/swarmvault/swarm-design-ui)<a href="https://agentmods.dev/skills/anmarhani/swarmvault/swarm-design-ui"><img src="https://agentmods.dev/badge/skills/anmarhani/swarmvault/swarm-design-ui/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/anmarhani/swarmvault/swarm-design-ui"><img src="https://agentmods.dev/badge/skills/anmarhani/swarmvault/swarm-design-ui.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.00090 | $0.01179 |
| Opus 5 | $0.00045 | $0.00589 |
| Sonnet 5 | $0.00018 | $0.00236 |
| Haiku 4.5 | $0.00009 | $0.00118 |
Grade A, and why
swarm-design-ui 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 9d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
swarm-design-ui — UI/UX design phase
Gate: validated SRS declaring a user interface. Runs alongside swarm-design. The goal is intentional, consistent design decided with the user — not templated defaults.
Load only what you need (token economy): the per-interface reference for the type at hand
(references/web.md, references/mobile.md, references/desktop.md, references/tui-cli.md),
and — for graphical UIs — references/style-menu.md, the on-demand catalog of product
categories, style families, layout patterns, and design resources (checklist.design, UX laws,
color/type/psychology tools).
1. Interview first
Audience and context of use; brand personality; platform conventions to honor; accessibility requirements; existing brand assets. Keep it light and options-first — the point is to understand the product, not to quiz.
2. Propose a design system (offer ≥2 directions)
Don't jump to one look. Using the product's category and personality (see
references/style-menu.md for the vocabulary), synthesize a recommended design system and
at least one distinct alternative — e.g. "clinical precision" vs "warm craft" — so the user
chooses with something concrete in front of them. Present each as a compact panel:
DESIGN SYSTEM — <recommended | alternative>
Pattern/layout : <e.g. Hero-centric + social proof> why: <conversion/trust rationale>
Style : <e.g. Soft UI evolution> best for: <fit>
Colors : primary / surface / accent / semantic / bg / text (WCAG-AA checked)
Typography : <display / body pairing> mood: <…>
Effects : <shadows, motion timing, hover>
Avoid : <anti-patterns for this domain — see style-menu>
The style/category menu is a guide, not a cage: if the product's needs point elsewhere, design for them. Resolve the picked direction into the tokens below.
3. Produce the design-system doc (docs/design-ui.md)
Everything as tokens and scales, never per-screen ad-hoc values:
What ships with it
5 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.
- 9d ago First seen · 87 lines · 0 tokens per session scan A 147608068774
swarm-design-ui is a skill published in the GitHub repository AnmarHani/SwarmVault (5 stars, last pushed 1mo ago), licensed MIT. It adds 90 tokens to every session and 1,179 once invoked, about $0.0005 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
mcp-host-styling-integration
Integrates MCP App UI with host theming system. Applies host CSS variables, handles onhostcontextchanged, safe area insets, display mode detection, and fullscreen configuration.
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI).…
web-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
frontend-design
Produce intentional, responsive, accessible UI work and perform visual QA instead of generic component assembly.
tutti-ui-system
Use when working with @tutti-os/ui-system components, replacing local UI with shared components, querying component ids or metadata, promoting UI into shared base or business components, or maintaining UI-system storyboard inventory.
moai-design-tools
Design tool integration specialist covering Figma MCP, Pencil renderer, and Pencil-to-code export. Use when fetching design context from Figma, rendering Pencil designs, or exporting to React/Tailwind code.