agentmods.dev

sova: Command for Claude Code

.claude/commands/design.md

design is a command for Claude Code from xsovad06/sova. It costs 15 tokens per session (938 once invoked), scanned A, original, Apache-2.0.

A coding command that applies the SOVA design system, a set of shared rules for dashboard colors, layouts, components, and icons.

In plain words
What is it for?
Creating or modifying dashboard UI elements while consulting SOVA's CSS, templates, components, icons, JavaScript utilities, and design documentation.
Why use it?
It helps keep new or changed dashboard screens consistent with the existing SOVA interface instead of introducing unrelated styles.

Command for Claude Code

Written for Claude Code: user-invocable in frontmatter.

This is xsovad06/sova's own configuration. It tells Claude Code how to work on sova itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything sova configures →

not rated 2repo changed 16d ago A scan 15 tokens original Apache-2.0
View source ↗ xsovad06/sova
Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/xsovad06/sova/main/.claude/commands/design.md
Clone the repo
git clone --depth 1 https://github.com/xsovad06/sova

Made for: Claude Code.

Wrote 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.

agentmods badge for design

README.md
[![agentmods](https://agentmods.dev/badge/commands/xsovad06/sova/design/github.svg)](https://agentmods.dev/commands/xsovad06/sova/design)
Your own site
<a href="https://agentmods.dev/commands/xsovad06/sova/design"><img src="https://agentmods.dev/badge/commands/xsovad06/sova/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.

agentmods 80×15 button for design

Your own site · 80×15
<a href="https://agentmods.dev/commands/xsovad06/sova/design"><img src="https://agentmods.dev/badge/commands/xsovad06/sova/design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 938 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00015 $0.00938
Opus 5.5 $0.00006 $0.00375
Sonnet 5.5 $0.00003 $0.00188
Haiku 4.5 $0.00002 $0.00094

Measured 16d ago against content hash fb822bb553cf, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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 16d 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.

.claude/commands/design.md · 85 lines

How it starts

The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.

SOVA UI Design Standards

Apply the SOVA design system to the specified UI work. Context: $ARGUMENTS

1. Load the Design System

Read these files before making any UI decisions:

  • sova/dashboard/static/style.css: CSS variables (Catppuccin Mocha), component classes
  • sova/dashboard/templates/base.html: layout, Tailwind config, icon macro, notification panel
  • sova/dashboard/templates/_head.html: shared Tailwind config (centralized)
  • sova/dashboard/templates/_icons.html: icon macro (Heroicons v2 outline)
  • sova/dashboard/templates/_components.html: Jinja2 component macros (stat_card, card_header)
  • sova/dashboard/static/app.js: SOVA_COLORS, toast system, browser notifications, shared utilities
  • docs/design-system.md: full design system reference

Optionally view the living style guide at /style-guide in the running dashboard.

2. Mandatory Rules

Colors

  • Every color must come from the Catppuccin Mocha palette defined as CSS variables in style.css
  • Tailwind classes use RGB vars: bg-accent, text-accent-green, border-accent/30
  • JS uses window.SOVA_COLORS.accent (populated from CSS vars at init)
  • Never hardcode hex values in templates or JS
  • Semantic meanings:
    • Blue (accent): primary, links, active state
    • Green: success, done, money
    • Red: error, failed, danger
    • Yellow: warning, running, action needed
    • Purple (mauve): metadata, researcher role

Buttons (3 main variants)

  • Primary: .sova-btn .sova-btn-primary or bg-accent/20 text-accent hover:bg-accent/30
  • Danger: .sova-btn .sova-btn-danger
  • Success: .sova-btn .sova-btn-success
  • Warning: .sova-btn .sova-btn-warning
  • Never invent new button color combinations

Cards

  • Container: .sova-card or bg-surface-card rounded-lg border border-gray-700/50
  • Header: .sova-card-header or use the card_header() macro
  • Stat: .sova-stat + .sova-stat-label + .sova-stat-value or use the stat_card() macro

Typography (6 roles)

  • Page heading: text-2xl font-semibold
  • Section heading: text-lg font-semibold
  • Label: text-sm font-medium
  • Body: text-sm (default)
  • Caption: text-xs text-gray-500
  • Data/numbers: font-mono font-semibold

Read the full file on GitHub · 85 lines

Changes

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.

  1. 16d ago Changed fb822bb553cf
  2. 2mo ago First seen · 85 lines · 15 tokens per session scan A eca0e5ed780c

Subscribe to this mod's changes

design is a command published in the GitHub repository xsovad06/sova (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 15 tokens to every session and 938 once invoked, about $0.0001 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.

Analytics and metricsCode reviewDesign and UXFrontendai-agentsautomationautonomous-developmentclideveloper-tools
Related

Other commands, from other repositories

aitask-screen-recording

Turn a screen-recording video (.mp4, .mov, .webm, .mkv from a phone, emulator or desktop) into labelled contact sheets, key frames, a timeline, and measured animation timing and easing, because coding agents can read images but not video files. Use this whenever the user gives, attaches or mentions a video or screen…

beyondeye/aitasks · 143 tokens

greptile-review

Execute the full Greptile review cycle on a PR, looping until score meets threshold or circuit breaker triggers.

opensesh/KARIMO · 0 tokens

review-branch

Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.

damusix/atomic-claude · 35 tokens

advanced-code-review-context

Advanced Code Review Phase 2: Context Analysis - load previous reviews, PR history, declined items.

axiomantic/spellbook · 19 tokens

mach12:issue-review

Read a GitHub issue and all comments, review the implementation plan, and present findings.

LeanAndMean/scramjet · 17 tokens

plan-levels

At standard and lean, each row sets one phase's spawns. A phase with no row runs as written. A row only removes or merges agents.

dean0x/devflow · 0 tokens