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/xsovad06/sova/design-systemnpx skills add xsovad06/sova --skill design-systemgit clone --depth 1 https://github.com/xsovad06/sovaWhat 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.00040 | $0.00508 |
| Opus 5 | $0.00020 | $0.00254 |
| Sonnet 5 | $0.00008 | $0.00102 |
| Haiku 4.5 | $0.00004 | $0.00051 |
Grade A, and why
design-system 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.
What it actually says
Design System Conventions
When creating or modifying frontend templates, CSS, or UI components, follow these conventions.
Visual Hierarchy
- Establish clear heading hierarchy (h1 > h2 > h3) with distinct sizes
- Use whitespace to separate logical sections -- generous padding over cramped layouts
- Primary actions must be visually distinct from secondary actions (size, color, weight)
- Data tables: header row visually distinct, alternating row backgrounds for readability
Typography
- Limit to 2 font families maximum (one for headings, one for body)
- Body text: 14-16px minimum, 1.5-1.6 line height
- Do not use font weights below 400 for body text
- Headings: use weight contrast (600-700) rather than excessive size
Spacing
- Use a consistent spacing scale (4px base: 4, 8, 12, 16, 24, 32, 48)
- Containers: minimum 16px padding on all sides
- Between sections: minimum 24px gap
- Between related items: 8-12px gap
Color
- Maintain WCAG AA contrast ratios (4.5:1 for text, 3:1 for large text)
- Use semantic color names in CSS (--color-primary, --color-danger) not raw values
- Status indicators: green=success, yellow=warning, red=error, blue=info
- Dark mode: never use pure black (#000) backgrounds -- use dark grays
Anti-Slop Rules
- No centered-everything layouts -- use left-aligned text with intentional centering
- No generic card grids without hierarchy -- vary card sizes to show importance
- No walls of same-sized buttons -- establish visual priority
- No unstyled form elements -- every input needs focus states and consistent borders
- Animations: subtle and purposeful (150-300ms transitions), never decorative
Responsive
- Mobile-first: design for smallest viewport, enhance for larger
- Touch targets: minimum 44x44px on mobile
- Do not hide critical information behind hover states on touch devices
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 · 52 lines · 40 tokens per session scan A a5efe8f9bd15
design-system is a skill published in the GitHub repository xsovad06/sova (2 stars, last pushed 3d ago), licensed Apache-2.0. It adds 40 tokens to every session and 508 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
creative-design
Use when creating new UIs from scratch — landing pages, marketing sites, prototypes, or any greenfield frontend work where no existing design system applies. Also triggers for portfolio sites, product launches, campaign pages, microsites, or any page where visual distinction and memorability matter as much as…
design-guide
Paperclip UI design system guide for building consistent, reusable frontend components. Use when creating new UI components, modifying existing ones, adding pages or features to the frontend, styling UI elements, or when you need to understand the design language and conventions. Covers: component creation, design…
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
material-ui-tailwind
Integrates Material UI with Tailwind CSS v4 using cascade layers (enableCssLayer, @layer order) and documents Tailwind v3 interoperability (preflight, important, injectFirst, portals). Use when combining MUI with Tailwind utilities, slotProps className, or theme token bridges.
author-component
Create or review Blazor components (.razor files) with correct architecture. USE FOR: writing new Blazor components that do NOT involve JavaScript interop, implementing parameters and EventCallback, RenderFragment slots, component lifecycle (OnInitializedAsync, OnParametersSet), async patterns, IAsyncDisposable…
obsidian-layout-adjustment
Workflow for working with the user on changing how Obsidian looks using CSS snippets. Use this whenever the user asks to restyle Obsidian, tune a vault's visual layout, adjust tabs, sidebars, note surfaces, properties, backlinks, graph panes, file explorer rows, icons, links, shadows, active states, or CSS snippets.…