shadcn-add

A command for adding a ShadCN/UI component to the Shade design system and creating its Storybook stories. Storybook is a development tool for viewing and documenting interface components in isolation.

In plain words
What is it for?
Adding new UI components, retrieving their ShadCN documentation, preventing duplicate files, and documenting them in Storybook.
Why use it?
It checks for existing components and follows the project's documentation, installation, and design-system rules before adding anything.

Command for Claude Code

Install

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.

agentmods
npx agentmods add commands/tryghost/ghost/shadcn-add
Clone the repo
git clone --depth 1 https://github.com/TryGhost/Ghost

Made for: Claude Code.

Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,200 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00014 $0.02200
Opus 5 $0.00007 $0.01100
Sonnet 5 $0.00003 $0.00440
Haiku 4.5 $0.00001 $0.00220

Measured 2d ago against content hash 8373d0c63ca1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

shadcn-add 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 2d 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.

apps/shade/.claude/commands/shadcn-add.md · 311 lines

How it starts

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

Add ShadCN Component to Shade

You are tasked with adding a new ShadCN/UI component to the Shade design system. Follow these steps carefully:

Important Guidelines

ALWAYS read and follow the instructions in AGENTS.md - this file contains critical information about:

  • Component structure and naming conventions
  • Build and test commands
  • Coding style requirements
  • ShadCN installation guardrails
  • Storybook documentation standards

Step 1: Check if Component Already Exists

First, check if the component already exists in Shade:

  1. Search for the component file in src/components/ui/{{component-name}}.tsx
  2. Search for similar named files (e.g., for "input-otp" check for "input-otp.tsx", "otp.tsx", etc.)
  3. If the component exists, STOP and inform the user that the component already exists and provide the file path

Step 2: Fetch ShadCN Documentation

Use Puppeteer to retrieve the component documentation (if Puppeteer is not available use Webfetch):

  1. Fetch https://ui.shadcn.com/docs/components/{{component-name}}
  2. Extract:
    • Component description and use case
    • Installation command (npx shadcn@latest add ...)
    • All code examples with full code blocks
    • Component variants (default, outline, ghost, etc.)
    • Size options (sm, md, lg, icon, etc.)
    • Props and TypeScript types
    • Usage patterns and best practices
  3. Use this information to create comprehensive Storybook stories

Step 3: Install the Component

  1. Create a git branch first (safety measure):

    git checkout -b shadcn-add-{{component-name}}
    
  2. Run the installation command from the ShadCN docs:

    npx shadcn@latest add {{component-name}}
    
  3. CRITICAL: When prompted about overwriting existing files, always choose "No" or "Skip"

    • NEVER overwrite existing Shade components
    • If conflicts occur, stop and inform the user
  4. After installation, run:

    pnpm && pnpm lint --fix
    
  5. Fix linter errors in component file:

Read the full file on GitHub · 311 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. 2d ago First seen · 311 lines · 14 tokens per session scan A 8373d0c63ca1

Subscribe to this mod's changes

shadcn-add is a command published in the GitHub repository TryGhost/Ghost (55,095 stars, last pushed today), licensed MIT. It adds 14 tokens to every session and 2,200 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-08-30.