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 skills add Dragoon0x/everything-design-taste --skill card-designgit clone --depth 1 https://github.com/Dragoon0x/everything-design-tasteWrote 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/dragoon0x/everything-design-taste/card-design)<a href="https://agentmods.dev/skills/dragoon0x/everything-design-taste/card-design"><img src="https://agentmods.dev/badge/skills/dragoon0x/everything-design-taste/card-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/dragoon0x/everything-design-taste/card-design"><img src="https://agentmods.dev/badge/skills/dragoon0x/everything-design-taste/card-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.00021 | $0.00477 |
| Opus 5 | $0.00010 | $0.00238 |
| Sonnet 5 | $0.00004 | $0.00095 |
| Haiku 4.5 | $0.00002 | $0.00048 |
Grade A, and why
card-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 6d 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
Card Design
Anatomy
┌─────────────────────┐
│ [Media/Image] │ Optional: visual anchor
│ │
│ Category Label │ Optional: metadata
│ Heading │ Required: primary info
│ Description text │ Optional: supporting info
│ │
│ [Metadata/Footer] │ Optional: date, author, tags
│ [Actions] │ Optional: buttons, links
└─────────────────────┘
Rules
- Consistent height in grids or use masonry. Mixed heights in regular grids look broken.
- One primary action per card. The whole card can be clickable, or have a single CTA.
- Don't overload. If a card needs more than 4-5 pieces of information, it might need a different format.
- Image ratios matter. Pick one ratio (16:9, 4:3, 1:1) and stick with it across the grid.
- Hover states should indicate interactivity (subtle lift, border change, or background shift).
Card Variants
| Variant | Use Case |
|---|---|
| Content card | Blog posts, articles, products |
| Action card | Dashboard widgets, quick actions |
| Profile card | Team members, user profiles |
| Stat card | KPIs, metrics, numbers |
| Media card | Video, image, audio thumbnails |
Grid Layouts
- 2 columns: Side-by-side comparison, editorial
- 3 columns: Product listings, blog archives (most common)
- 4 columns: Dense grids, small cards, dashboards
- Masonry: Pinterest-style, variable height content
Anti-Patterns
- Cards with 3 different clickable areas (confusing targets)
- Drop shadows so heavy they dominate the page
- Border-radius: 24px (too much, 8-12px is usually right)
- Cards that are just styled divs with no interactive purpose
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.
- 6d ago First seen · 50 lines · 21 tokens per session scan A 94e7aaa116bc
card-design is a skill published in the GitHub repository Dragoon0x/everything-design-taste (11 stars, last pushed 5mo ago), licensed MIT. It adds 21 tokens to every session and 477 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
scroll-craft
Build premium scroll-driven landing pages for service, product, food, and drink brands. Plan the visitor journey, page grammar, emotional peak, and bespoke signature move. Create dimensional heroes with independent visual planes, restrained motion, and separate mobile composition. Use supplied photos and footage or…
generate-ui-from-brand
Pipeline skill — turns a URL or DESIGN.md into a concrete UI structure with decisions already made. Extracts live design tokens, normalizes them into a semantic system, applies UX principles, and outputs an actionable UI spec. Use when building UI for an existing brand from scratch, auditing a design system, or…
micro-interactions
Micro-interactions are small, purposeful animations and responses that reward the user and make the interface feel alive — an animated icon, a satisfying toggle, a subtle reveal. Borrowed from the natural world, they add delight without distraction. Use when designing interactive components, success states, toggles…
tab-navigation
Tabs organise related content under a shared context — switching tabs swaps the view without leaving the page. Use when a screen has multiple distinct content areas that share a common header or action set, and when the user needs to switch between them frequently. Use when designing tabbed layouts, content panels…
elevation-and-depth
Elevation — subtle shadows and layering — communicates visual hierarchy by lifting elements above the surface. Combined with border-radius, it creates the tactile quality of cards, modals, and interactive surfaces. Use when designing cards, dropdowns, modals, tooltips, or any floating UI element.
status-colors-and-errors
Keep status and error colours minimal and consistent — too many semantic colours confuse users. Each colour must mean exactly one thing. Errors should be recoverable, large failures must be prevented, and the UI should always give the user a path forward. Use when designing status indicators, error states, form…