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 skills/tryghost/ghost/shade-new-componentnpx skills add TryGhost/Ghost --skill shade-new-componentgit 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.00047 | $0.01146 |
| Opus 5 | $0.00023 | $0.00573 |
| Sonnet 5 | $0.00009 | $0.00229 |
| Haiku 4.5 | $0.00005 | $0.00115 |
Grade A, and why
Shade new component 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Shade — new component / pattern checklist
Before marking a Shade component or pattern done, this checklist must pass.
Files and naming
- File: kebab-case (
dropdown-menu.tsx) — matches ShadCN CLI output. Don't rename for casing. - Exported identifier: PascalCase (
DropdownMenu). - Hooks, functions, variables: camelCase.
- Sibling
<name>.stories.tsxis required (same folder). - Inside Shade itself, import via the
@/alias (@/lib/utils,@/components/ui/input-surface).
Storybook title prefix
| Layer | Title |
|---|---|
| Primitive | Primitives / <Name> |
| Component | Components / <Name> |
| Recipe | Recipes / <Name> |
| Pattern | Patterns / <Name> |
| Token gallery | Tokens / <Topic> |
Required on every story file:
tags: ['autodocs']parameters.docs.description.component— short one-line summary- Per-story
parameters.docs.description.story— one-liner explaining when to use that variant - One story per important variant/state. Many small focused stories > one prose-heavy story.
Component shape
import * as React from 'react';
import {cva, type VariantProps} from 'class-variance-authority';
import {cn} from '@/lib/utils';
const thingVariants = cva('base-classes-here', {
variants: {
variant: {default: '...', destructive: '...'},
size: {default: '...', sm: '...'}
},
defaultVariants: {variant: 'default', size: 'default'}
});
export interface ThingProps
extends React.HTMLAttributes<HTMLDivElement>,
VariantProps<typeof thingVariants> {}
const Thing = React.forwardRef<HTMLDivElement, ThingProps>(
({className, variant, size, ...props}, ref) => (
<div
ref={ref}
className={cn(thingVariants({variant, size, className}))}
{...props}
/>
)
);
Thing.displayName = 'Thing';
export {Thing, thingVariants};
Hard requirements:
classNameforwarded and merged viacn()— never overwritten, never dropped. Applies to every component that renders DOM.- Visual/interactive props only (
variant,size,loading). No workflow props (isMembersPage,layoutMode) — those mean you actually need a Pattern wrapper. - Multi-region components expose compound subcomponents (
.Title,.Actions,.Body) — not a prop bag.
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 · 118 lines · 47 tokens per session scan A da66a256389d
Shade new component is a skill published in the GitHub repository TryGhost/Ghost (55,095 stars, last pushed yesterday), licensed MIT. It adds 47 tokens to every session and 1,146 once invoked, about $0.0002 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 skills, from other repositories
write-concept
Write or review JavaScript concept documentation pages for the 33 JavaScript Concepts project, following strict structure and quality guidelines.
seo-review
Perform a focused SEO audit on JavaScript concept pages to maximize search visibility, featured snippet optimization, and ranking potential.
test-writer
Generate comprehensive Vitest tests for code examples in JavaScript concept documentation pages, following project conventions and referencing source lines.
fact-check
Verify technical accuracy of JavaScript concept pages by checking code examples, MDN/ECMAScript compliance, and external resources to prevent misinformation.
resource-curator
Find, evaluate, and maintain high-quality external resources for JavaScript concept documentation, including auditing for broken and outdated links.
debug-task
Diagnose and fix moon tasks that are broken, misconfigured, or behaving unexpectedly. Use this skill when a moon task is failing, not running, skipped, hanging, producing stale or wrong output, cached when it shouldn't be, re-running every time when it should be cached, or when outputs are empty or missing after a…