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/dashboard-design/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/dashboard-design)<a href="https://agentmods.dev/skills/xsovad06/sova/dashboard-design"><img src="https://agentmods.dev/badge/skills/xsovad06/sova/dashboard-design/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/dashboard-design"><img src="https://agentmods.dev/badge/skills/xsovad06/sova/dashboard-design.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.00066 | $0.02852 |
| Opus 5.5 | $0.00026 | $0.01141 |
| Sonnet 5.5 | $0.00013 | $0.00570 |
| Haiku 4.5 | $0.00007 | $0.00285 |
Grade A, and why
dashboard-design 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 14d 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 — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SOVA Dashboard Design System + Quality Protocol
Read this skill BEFORE writing any template HTML, CSS, or frontend JavaScript under sova/dashboard/. It combines the design system reference with quality-of-execution rules that prevent generic AI output.
0. Reference Files
Before making changes, read these:
sova/dashboard/static/style.css: CSS variables (Catppuccin Mocha), component classessova/dashboard/templates/_head.html: shared Tailwind config (centralized)sova/dashboard/templates/_icons.html: SVG icon macro (Heroicons v2 outline)sova/dashboard/templates/_components.html: Jinja2 component macros (stat_card, card_header)docs/design-system.md: full design system reference
1. Design Dials
Three dials control output. SOVA defaults (do not change without explicit user instruction):
| Dial | Value | Effect |
|---|---|---|
| DESIGN_VARIANCE | 3 (Predictable) | Symmetrical grids, equal paddings. Developers need trust, not surprise. |
| MOTION_INTENSITY | 2 (Static) | CSS :hover/:focus only. No scroll-triggered reveals, no auto-animations. Agent status data should feel stable. |
| VISUAL_DENSITY | 6 (Dense App) | Tighter spacing (p-4 to p-8). Dashboard is information-dense by nature. |
These dials mean: no masonry layouts, no parallax, no staggered scroll reveals, no ambient background motion.
2. Anti-Slop Rules (Banned Patterns)
If your generated code includes ANY of these, the output fails quality checks:
Layout
- Generic 3-equal-column grids with identical cards (the "SaaS landing page" look)
- Cards with no visual hierarchy: all same padding, same font size, same weight
- Full-width sections with no constraint (content stays within the
ml-64 p-8main area) - Centered text blocks wider than
max-w-2xl
Color
- Any color outside Catppuccin Mocha palette (no hardcoded hex, rgb, hsl)
- Gradient backgrounds on containers or sections (SOVA is flat, not glassmorphic)
- Random opacity values: use the established scale:
text-gray-500for muted,/30for borders,/20for subtle fills,/10for faint backgrounds rgba(0,0,0,...)or similar generic shadows: use Catppuccin surface colors
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.
- 14d ago Changed · +3 lines baf5011d218c
- 1mo ago Changed a79a40868761
- 2mo ago First seen · 225 lines · 66 tokens per session scan A c4aeb18942c4
dashboard-design is a skill published in the GitHub repository xsovad06/sova (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 66 tokens to every session and 2,852 once invoked, about $0.0003 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
ui-design
This skill should be used when the user asks to "design a component", "pick colors", "improve typography", "fix spacing", or discusses visual design and CSS.
beautify-with-pingfusi
Beautify or redesign an existing website through iterative pingfusi review rounds with a real human reviewer. Use when asked to "beautify this website," "make this page look professional," "polish this UI/design," "improve the visual design," or finish an AI-built page when there is no reference site to match. Do not…
accessibility
This skill should be used when the user asks to "add accessibility", "check ARIA", "handle keyboard navigation", or creates UI components, forms, or interactive elements.
fix-with-pingfusi
Fix or polish an existing website clone/draft using pingfusi review rounds. Use when the user says "fix it with pingfusi", "polish this clone", "make this match the original", or asks to finish/verify a draft built by any tool (ditto, lovable, v0, hand-written) until the review passes.
microservices-architecture
Guides service boundary analysis, communication pattern selection, data consistency design, API contract strategy, and resilience checklist for microservices systems. Complements the microservices fragment. Invoked when the user asks to design a microservices system, split a monolith, or review service boundaries.
relational-database-design
Designs or reviews a relational database schema for a given domain. Covers table structure, normalization, indexes, constraints, and migration strategy. Invoked when the user asks to design a schema, review a database structure, or optimize a data model.