Ghost is a publishing platform for creating websites, blogs, memberships, subscriptions, and newsletters. Publishers and developers can use it through managed hosting or run it themselves, while contributors work on its monorepo, themes, and API.
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.
git clone --depth 1 https://github.com/TryGhost/GhostWrote 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/tryghost/ghost/shadcn-add)<a href="https://agentmods.dev/commands/tryghost/ghost/shadcn-add"><img src="https://agentmods.dev/badge/commands/tryghost/ghost/shadcn-add/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/commands/tryghost/ghost/shadcn-add"><img src="https://agentmods.dev/badge/commands/tryghost/ghost/shadcn-add.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.00014 | $0.02200 |
| Opus 5.5 | $0.00006 | $0.00880 |
| Sonnet 5.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 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 — 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.
- 1mo 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,561 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.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
add-layout
Create a new Quiver layout named: $ARGUMENTS.
add-theme
Add a new visual theme to this Quiver app: $ARGUMENTS.
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.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.