Borrowing it
Nothing to install: this file belongs to brianmontanaweb/agentic-design-system. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/brianmontanaweb/agentic-design-system/main/.claude/skills/add-component-source/SKILL.mdgit clone --depth 1 https://github.com/brianmontanaweb/agentic-design-systemWrote 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/brianmontanaweb/agentic-design-system/add-component-source)<a href="https://agentmods.dev/skills/brianmontanaweb/agentic-design-system/add-component-source"><img src="https://agentmods.dev/badge/skills/brianmontanaweb/agentic-design-system/add-component-source.svg" alt="Measured on agentmods" 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.00085 | $0.01168 |
| Opus 5 | $0.00043 | $0.00584 |
| Sonnet 5 | $0.00017 | $0.00234 |
| Haiku 4.5 | $0.00009 | $0.00117 |
Grade A, and why
add-component-source 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 7d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add Component Source
Create the component source and exports given $ARGUMENTS in the format <ComponentName> [core|agents]. Extra context (ARIA pattern, MCP states) may follow — use it instead of re-deriving.
If the package is not specified, infer it using the package inference rules in the shared conventions reference (Step 2).
Gotchas
- Never
import React from 'react'— use named type imports (import type { ReactElement, ReactNode } from 'react'); writeleftIcon?: ReactElement, neverReact.ReactElement. - ARIA is mandatory from the first line — apply the correct live region while writing the component, not in a later audit pass.
color.on.accentand similar token names are not hex violations — only flag#-prefixed literal values.- Light/dark support is free if you stay on semantic tokens — never read color mode in the component and never read single-mode values off the raw
colorModesexport for styling. If a needed color has no semantic token, follow the token addition steps in the Theming section of the shared conventions reference (add the color to bothtokens/color.dark.jsonandcolor.light.json→npm run tokens:generate→ use the token name). - No approval gate — this skill creates exactly the files listed below; proceed without asking. The
/add-componentorchestrator owns plan approval for full scaffolds.
Step 1 — Check for existing component
ls packages/core/src/<ComponentName>/<ComponentName>.tsx packages/agents/src/<ComponentName>/<ComponentName>.tsx 2>/dev/null
If any output is produced, stop immediately and respond:
## Already exists: <ComponentName>
`<path shown in ls output>` already exists.
Use `/update-component <ComponentName>` to audit and update it instead.
Do not read, write, or modify any files.
Step 2 — Read context
Read:
.claude/skills/shared/references/conventions.md— file layout, package inference, import/export/token rules.claude/skills/shared/references/aria-patterns.md— ARIA pattern per component type, MCP statespackages/<package>/src/index.ts— current export pattern- One existing component source in the target package (e.g.
packages/agents/src/ThinkingIndicator/ThinkingIndicator.tsx) — code style
What ships with it
1 file 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.
- 7d ago First seen · 101 lines · 85 tokens per session scan A 5938b6589147
add-component-source is a skill published in the GitHub repository brianmontanaweb/agentic-design-system (3 stars, last pushed 18d ago), licensed MIT. It adds 85 tokens to every session and 1,168 once invoked, about $0.0004 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-31.
Other skills, from other repositories
handoff-spec
Write the implementation handoff — measurements, behaviours, assets, states, and edge cases. Use when engineering picks up the work. For verifying the result afterwards use design-qa-checklist; for reusable library components use component-spec (design-systems).
animation-principles
Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use motion-system (design-systems); for a full interaction spec use micro-interaction-spec.
readable-measure
Set line length and measure for comfortable reading across type sizes and breakpoints. Use when tuning body text. Covers measure only — for the full size and weight scale, use typography-scale.
von-restorff-effect
Apply the Von Restorff Effect — the element that differs from its neighbours is the one remembered. Use when a single action must dominate. For overall ordering rather than single-element emphasis, use visual-hierarchy.
color-system
Build a product colour system — tonal scales, semantic roles, and contrast compliance. Use when defining or rebuilding colour from scratch. For dark-mode adaptation use dark-mode-design; for chart palettes use data-visualization; for multi-brand token architecture use theming-system (design-systems).
dark-mode-design
Adapt an existing palette to dark mode — surface elevation, contrast rebalancing, and desaturation rules. Use when you already have a light palette to translate. For building the base palette first, use color-system.