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 memi-design/design-skills --skill component-cataloggit clone --depth 1 https://github.com/memi-design/design-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/memi-design/design-skills/component-catalog)<a href="https://agentmods.dev/skills/memi-design/design-skills/component-catalog"><img src="https://agentmods.dev/badge/skills/memi-design/design-skills/component-catalog/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/memi-design/design-skills/component-catalog"><img src="https://agentmods.dev/badge/skills/memi-design/design-skills/component-catalog.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.00037 | $0.00399 |
| Opus 5.5 | $0.00015 | $0.00160 |
| Sonnet 5.5 | $0.00007 | $0.00080 |
| Haiku 4.5 | $0.00004 | $0.00040 |
Grade A, and why
component-catalog 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 26d 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.
What it actually says
Component catalog
When to use
Use for a bounded product surface with repeated patterns, or when a supplied design does not clearly map to existing components. For implementation of one Figma or Paper selection, use design-to-code-handoff first. Do not use a universal inventory as a build list.
Workflow
- Inventory actual routes, workflows, states, and repeated patterns. Read local instructions, component APIs, tokens, existing stories or component previews, and consumers. Record where each candidate appears.
- Use the component catalog as a vocabulary check. Identify the smallest semantic component that covers observed behavior. Do not assume Atomic Design or shadcn/ui is installed; use either only when the repository follows it.
- For each candidate choose reuse, extend, or new. Reuse when semantics, interaction, accessibility, and states fit. Extend when the API can support a missing state without breaking current callers. Add only when the needed behavior has a distinct contract. Record the alternative considered and why it fails.
- Specify the public API, supported variants, states, composition, keyboard behavior, focus management, responsive behavior, and token dependencies. Keep visual variants separate from semantic behavior.
- Verify the decision with representative callers and a Storybook story or existing component preview. Test keyboard and touch interaction for controls. Check that the proposed API covers observed states without one-off overrides.
Output
| Pattern and evidence | Existing component | Decision and reason | Required states and contract | Verification | Unresolved |
|---|
Name missing source evidence or unavailable previews. A component count is not evidence of coverage; report the observed workflows and states that are covered instead.
What ships with it
2 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.
- 26d ago Changed · +6 lines · +10 tokens per session ae179964ac99
- 1mo ago First seen · 20 lines · 27 tokens per session scan A f8585f20660e
component-catalog is a skill published in the GitHub repository memi-design/design-skills (7 stars, last pushed 27d ago), licensed MIT. It adds 37 tokens to every session and 399 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-31.
Other skills, from other repositories
accessibility-per-component
Audit one design system component's accessibility against WCAG 2.2 AA: keyboard, screen reader, contrast, focus, ARIA, target size. Trigger: a11y audit, is this accessible, WCAG check, screen reader support, keyboard navigation check. Not for page- or product-wide audits.
figma-variable-audit
Audit Figma variable collections: tier mapping, naming, alias chains, modes, orphans; can fix in place with Figma Console MCP. Triggers: audit my Figma variables, review variable collections, Figma variable health. For token files in code use token-audit.
theme-audit
Audit theme parity: tokens missing or unchanged per theme, component tokens bypassing semantics, contrast within each theme, resolver contexts, theme-switch regressions. Triggers: dark mode audit, theme coverage, brand variant parity. For general token structure use token-audit.
token-audit
Audit how design tokens are defined: tiers, naming, alias chains, raw values, orphans, DTCG readiness. Triggers: audit my tokens, token architecture review, token health check. Not for code consuming tokens (token-compliance), theme parity (theme-audit) or Figma variables (figma-variable-audit).
token-compliance
Find hardcoded colour, spacing and type values and wrong-tier token references in consuming code. Trigger: find hardcoded values, any hex in the code, are we using tokens correctly, token compliance. Do NOT use for token definitions — token-audit; token file format — schema-validator.
ai-component-description
Write a six-section prose description (purpose, props, anti-patterns, composition, accessibility, examples) for a Figma component's description field so LLMs read it via MCP. Triggers: describe this component for AI, Figma MCP description. JSON metadata files: use metadata-schema-generator.