Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/andrewvaughan/agent-councilnpx agentmods add skills/andrewvaughan/agent-council/setup-design-systemWrote 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/andrewvaughan/agent-council/setup-design-system)<a href="https://agentmods.dev/skills/andrewvaughan/agent-council/setup-design-system"><img src="https://agentmods.dev/badge/skills/andrewvaughan/agent-council/setup-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/andrewvaughan/agent-council/setup-design-system"><img src="https://agentmods.dev/badge/skills/andrewvaughan/agent-council/setup-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.00049 | $0.02089 |
| Opus 5.5 | $0.00020 | $0.00836 |
| Sonnet 5.5 | $0.00010 | $0.00418 |
| Haiku 4.5 | $0.00005 | $0.00209 |
Grade A, and why
setup-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 1mo 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 — 260 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design System Workflow
Initialize or extend the project's design system with properly accessible, consistent UI components using Tailwind CSS and shadcn/ui.
Step 0: Verify Feature Branch
Ensure we are on a feature branch based on the latest main:
git fetch origin main
If on main, create a new feature branch:
git checkout -b feature/design-system origin/main
If already on a feature branch, rebase onto latest origin/main:
git status --porcelain
If the working tree is dirty, stash before rebasing:
git stash push -m "setup-design-system: stash before rebase"
git rebase origin/main
git stash pop
If the working tree is clean, rebase directly:
git rebase origin/main
Step 1: Assess Current State
Check if a design system already exists:
- Look for
packages/ui/directory structure - Check for shadcn/ui configuration (
components.json) - Check Tailwind configuration (
src/index.cssfor@themedirectives in v4, ortailwind.config.*for v3) - Identify existing components and their patterns
- Check for design tokens (colors, spacing, typography definitions)
Ask the user:
- Initializing a new design system or extending the existing one?
- If extending: what components or patterns are needed?
- Any brand guidelines, color palette, or Figma designs to reference?
- Dark mode support needed?
Step 2: Product Council Design Review (for initialization or major changes)
If initializing the design system or making significant structural changes, activate a Product Council subset:
Model Selection: See the Model Selection section in README.md for mapping agent model specs to Task tool parameters.
Design Lead (Lead) — consult: ui-design
- Brand Identity: Color palette, typography, visual language
- Component Hierarchy: Primitives vs composed components
- Design Tokens: Token architecture (colors, spacing, typography, shadows)
- Recommendations: Design system structure and principles
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.
- 1mo ago First seen · 260 lines · 49 tokens per session scan A fc3ed499f7a4
setup-design-system is a skill published in the GitHub repository andrewvaughan/agent-council (15 stars, last pushed 7mo ago), licensed MIT. It adds 49 tokens to every session and 2,089 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-30.
Other skills, from other repositories
anti-slop-design
Autonomous Principal Design Technologist. Cures vibe-coded software from AI frontend slop using curated token archetypes and 7-axis quality gating.
antigravity-design-expert
Core UI/UX engineering skill for building highly interactive, spatial, weightless, and glassmorphism-based web interfaces using GSAP and 3D CSS.
muse
Defining and managing design tokens, applying token systems to existing codebases, building design system foundations. Use for spacing, color, typography, dark mode, cross-platform output.
pixel
Generating pixel-accurate HTML/CSS code from image mockups (PNG/JPG/screenshots) and performing visual verification for faithful reproduction. Use when mockup-to-code generation is needed.
mockup-extraction
Extract reusable components from approved HTML mockups during implementation. Identifies patterns, maps CSS to Tailwind, and populates prototype-patterns.md for visual fidelity. Use at start of /implement for UI-first features.
shadcn-integration
Integration guide for shadcn/ui components with OKLCH design tokens. Use when setting up shadcn, customizing themes, or adding components to Next.js projects. Auto-trigger on /init --tokens --shadcn flag.