Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add yonatangross/orchestkit/plugin install orkWrote 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/commands/yonatangross/orchestkit/design-stylecards)<a href="https://agentmods.dev/commands/yonatangross/orchestkit/design-stylecards"><img src="https://agentmods.dev/badge/commands/yonatangross/orchestkit/design-stylecards.svg" alt="Measured on agentmods" 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.00086 | $0.01050 |
| Opus 5 | $0.00043 | $0.00525 |
| Sonnet 5 | $0.00017 | $0.00210 |
| Haiku 4.5 | $0.00009 | $0.00105 |
Grade A, and why
design-stylecards 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 7d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auto-generated from skills/design-stylecards/SKILL.md
Source: https://github.com/yonatangross/orchestkit
Design Stylecards
Specs beat vibes. A stylecard is a named aesthetic recipe with exact values — the difference
between "add a nice shadow" (reinvented differently every session) and elevation/md (identical
every time, reviewed once, versioned forever).
/ork:design-stylecards list # Catalog index
/ork:design-stylecards elevation/md # Show one recipe
/ork:design-stylecards apply glass/dark to src/components/Panel.tsx
Why declarative recipes
Pipeline skills (design-to-code, design-context-extract) answer how to produce design output.
Stylecards answer what good looks like — as literal values an agent pastes, not adjectives it
interprets. Inspired by MengTo/Skills' stylecard micro-skills (MIT), consolidated into one catalog
to avoid manifest sprawl.
Workflow
1. Resolve the request to a recipe
Read("${CLAUDE_PLUGIN_ROOT}/skills/design-stylecards/references/stylecards.md") # The catalog — always read before choosing
# Match the user's intent to ONE recipe by its Use-When line.
# No match → say so and offer the closest two; never freehand values.
2. Show or apply
- Show: print the recipe verbatim — values, Use-When, Avoid. No paraphrasing values.
- Apply: edit the target file using the recipe's exact values. Adapt only the syntax (Tailwind arbitrary class ↔ plain CSS ↔ CSS custom property), never the numbers.
3. Respect the recipe's Avoid block
Every recipe ends with falsifiable Avoid rules (e.g. "never stack two elevation recipes on one element"). Violating an Avoid rule to satisfy a user request requires saying so explicitly.
Catalog index
Full recipes with exact values: references/stylecards.md.
| Recipe | Use when |
|---|---|
elevation/sm md lg |
Layered neutral shadows — compact controls / cards / hero surfaces |
glass/dark |
Frosted glass panel on a dark backdrop |
border/gradient |
1px gradient border without a wrapper hack |
background/mesh |
2–3 hue radial mesh page background |
type/editorial |
Display + body + mono role split with tracking values |
motion/budget |
The four allowed durations + the one-signature-moment rule |
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.
- 7d ago First seen · 100 lines · 86 tokens per session scan A b6770207b3d7
design-stylecards is a command published in the GitHub repository yonatangross/orchestkit (229 stars, last pushed today), licensed MIT. It adds 86 tokens to every session and 1,050 once invoked, about $0.0004 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-30.
Other commands, from other repositories
pn-audit-a11y
Surgical frontend accessibility audit — WCAG contrast, keyboard navigation, ARIA roles, focus management, and screen-reader compatibility. Standalone or chained by pn-frontend-audit.
pn-audit-typography
Surgical frontend typography audit — type scale, font choices, loading strategy, hierarchy, and accessibility. Standalone or chained by pn-frontend-audit.
lavra-design
Orchestrate the full design pipeline -- brainstorm, plan, research, revise, review, lock.
refactor
Refactor code while maintaining compliance (Phase 3.5).
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.