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 skills add The-AI-Directory-Company/agents-and-skills --skill component-design-specgit clone --depth 1 https://github.com/The-AI-Directory-Company/agents-and-skillsWrote 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/the-ai-directory-company/agents-and-skills/component-design-spec)<a href="https://agentmods.dev/skills/the-ai-directory-company/agents-and-skills/component-design-spec"><img src="https://agentmods.dev/badge/skills/the-ai-directory-company/agents-and-skills/component-design-spec/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/the-ai-directory-company/agents-and-skills/component-design-spec"><img src="https://agentmods.dev/badge/skills/the-ai-directory-company/agents-and-skills/component-design-spec.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.00027 | $0.01415 |
| Opus 5 | $0.00014 | $0.00707 |
| Sonnet 5 | $0.00005 | $0.00283 |
| Haiku 4.5 | $0.00003 | $0.00142 |
Grade A, and why
component-design-spec 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 8d 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Component Design Spec
Before you start
Gather the following from the user. If anything is missing, ask before proceeding:
- What component is being specified? — Name and one-sentence purpose
- Where does it appear? — Pages, layouts, or parent components that will consume it
- What design system does it belong to? — Existing system with tokens, or standalone
- What are the usage scenarios? — The 2-5 most common ways this component will be used
- Are there existing implementations? — Current components being replaced or extended
- What are the constraints? — Framework, browser support, performance budgets, package size limits
Spec template
1. Component Overview
Name: [PascalCase component name]
Purpose: [One sentence — what it does and why it exists]
Category: [Primitive / Composite / Pattern]
Status: [Proposed / In Review / Approved / Implemented]
Categories: Primitive (low-level, no domain logic: Button, Input), Composite (combines primitives: SearchField, DatePicker), Pattern (opinionated layout: DataTable, NavigationBar).
2. Props API
Define every prop with type, default, and description. Example format:
interface ComponentProps {
children: React.ReactNode;
variant: 'primary' | 'secondary' | 'ghost' | 'danger';
size?: 'sm' | 'md' | 'lg'; // default: 'md'
disabled?: boolean; // default: false
loading?: boolean; // default: false
onClick?: (event: React.MouseEvent) => void;
}
Rules: name props after what they control (variant="danger" not color="red"), default booleans to false, use string literal enums, follow onAction callback convention. If >10 props, consider composition.
3. States
| State | Trigger | Visual Change | Behavior Change |
|---|---|---|---|
| Default | Initial render | Base styling | Fully interactive |
| Hover | Mouse enter | Background darkens | Tooltip may appear |
| Focus | Keyboard tab | Focus ring visible | Accepts Enter/Space |
| Active | Mouse down / Enter | Scale down slightly | Action fires on release |
| Disabled | disabled={true} |
Opacity reduced | No events fire |
| Loading | loading={true} |
Spinner replaces icon | No events fire |
| Error | Validation failure | Red border, error icon | Error message shown |
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 130 lines · 27 tokens per session scan A 0bcad23ec178
component-design-spec is a skill published in the GitHub repository The-AI-Directory-Company/agents-and-skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 27 tokens to every session and 1,415 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-09-03.
Other skills, from other repositories
generic-react-ux-designer
Professional UI/UX design expertise for React applications. Covers design thinking, user psychology (Hick's/Fitts's/Jakob's Law), visual hierarchy, interaction patterns, accessibility, performance-driven design, and design critique. Use when designing features, improving UX, solving user problems, or conducting design…
frontend-enhancer
This skill should be used when enhancing the visual design and aesthetics of web applications. It provides modern UI components, design patterns, color palettes, animations, and layout templates. REQUIRES ui-research skill first. Use this skill for tasks like improving styling, creating responsive designs…
generic-design-system
Complete design system reference for any project - colors, typography, spacing, components, animations. Adapts to project theme and tech stack. Use when implementing UI, choosing colors, creating animations, or ensuring brand consistency. For new design systems, use ui-research skill first.
generic-react-design-system
Complete design system reference for React applications. Covers colors, typography, spacing, component patterns, glassmorphism effects, GPU-accelerated animations, and WCAG AA accessibility. Use when implementing UI, choosing colors, applying spacing, creating components, or ensuring brand consistency.
generic-fullstack-ux-designer
Professional UI/UX design expertise for full-stack applications. Covers design thinking, user psychology (Hick's/Fitts's/Jakob's Law), visual hierarchy, interaction patterns, accessibility, performance-driven design, and design critique. Use when designing features, improving UX, solving user problems, or conducting…
generic-fullstack-design-system
Complete design system reference for full-stack applications. Covers colors, typography, spacing, component patterns (shadcn/ui), effects, GPU-accelerated animations, and WCAG AA accessibility. Use when implementing UI, choosing colors, applying spacing, creating components, or ensuring brand consistency.