Borrowing it
Nothing to install: this file belongs to xsovad06/sova. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/xsovad06/sova/main/.agents/skills/design-system/SKILL.mdgit clone --depth 1 https://github.com/xsovad06/sovaWrote 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/xsovad06/sova/design-system)<a href="https://agentmods.dev/skills/xsovad06/sova/design-system"><img src="https://agentmods.dev/badge/skills/xsovad06/sova/design-system/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/xsovad06/sova/design-system"><img src="https://agentmods.dev/badge/skills/xsovad06/sova/design-system.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.00038 | $0.00490 |
| Opus 5.5 | $0.00015 | $0.00196 |
| Sonnet 5.5 | $0.00008 | $0.00098 |
| Haiku 4.5 | $0.00004 | $0.00049 |
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 21d 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.
- 21d ago Changed · -1 lines · -2 tokens per session a1af424e92ec
- 22d ago Changed 84e3ffa9f75a
- 2mo 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 yesterday), licensed Apache-2.0. It adds 38 tokens to every session and 490 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
find-simplifications
Use for a periodic repo-wide sweep of qwen-code for accumulated excess surface — dead components and files, orphaned locale keys, exports nothing consumes, added-then-removed scaffolding — filing candidates on a tracking issue and landing only what a maintainer has said yes to. Repo-wide and evidence-first; every…
code-review
You are a senior code reviewer. You receive diffs via stdin.
agent-debug-ci
Investigate failed scheduled or nightly GitHub Actions runs on the default branch, determine whether the failure is reproducible and repository-owned, implement the smallest evidence-backed fix, validate it, and open a pull request. Use when a failed nightly CI event starts an agent, or when the standard CI or…
audit-ci
Run and analyze Elements cold CI performance profiles and propose evidence-backed build, test, lint, and dependency-graph improvements. Use whenever asked to profile or benchmark pnpm run ci, rerun ci:profile, create a CI performance audit, compare CI timings, find bottlenecks or the completion path, investigate a CI…
review
Adversarial review of an increment before it ships, by a fresh context or another model family; every finding cites path:line and is re-verified. Use for "review", "qa", "critique this".
tech-debt-ci-review
Codex adapter for deep technical-debt and CI-stability audits. Use when asked to find test theater, flaky tests, missing or mis-scoped tests, brittle CI/toolchain behavior, structural debt blocking green PRs, or a remediation order for opencode-swarm.