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 agentmods add commands/tryghost/ghost/shadcn-addgit clone --depth 1 https://github.com/TryGhost/GhostWhat 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 | $0.00014 | $0.02200 |
| Opus 5 | $0.00007 | $0.01100 |
| Sonnet 5 | $0.00003 | $0.00440 |
| Haiku 4.5 | $0.00001 | $0.00220 |
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.
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:
- Search for the component file in
src/components/ui/{{component-name}}.tsx - Search for similar named files (e.g., for "input-otp" check for "input-otp.tsx", "otp.tsx", etc.)
- 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):
- Fetch
https://ui.shadcn.com/docs/components/{{component-name}} - 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
- Use this information to create comprehensive Storybook stories
Step 3: Install the Component
-
Create a git branch first (safety measure):
git checkout -b shadcn-add-{{component-name}} -
Run the installation command from the ShadCN docs:
npx shadcn@latest add {{component-name}} -
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
-
After installation, run:
pnpm && pnpm lint --fix -
Fix linter errors in component file:
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.
- 2d ago First seen · 311 lines · 14 tokens per session scan A 8373d0c63ca1
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.
Other commands, from other repositories
sonicjs-pr-maker
You are a specialized agent that creates Pull Requests for SonicJS, monitors CI/CD pipelines, analyzes failures, and automatically fixes issues including E2E test failures.
sonicjs-release-announcement
You are a specialized agent that creates compelling release announcements for SonicJS across multiple platforms. Your primary responsibilities are.
sonicjs-pr-fixer
You are a specialized agent that helps fix and merge problematic PRs in the SonicJS repository. This includes PRs from forks that need cherry-picking, Dependabot PRs that need e2e tests enabled, and any PR that needs fixes before merging.
sonicjs-seo
You are an SEO expert agent for SonicJS, a modern headless CMS built for Cloudflare's edge platform. Your goal is to help SonicJS rank for relevant keywords and grow organic traffic through legitimate, high-quality content strategies.
sonicjs-seo-blog
Generate a high-quality, SEO-optimized blog post for SonicJS on the topic: $ARGUMENTS.
sonicjs-seo-discord-sync
Help surface valuable Discord discussions as searchable web content for SEO benefits.