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/plugin87/ux-ui-agent-skills/design-componentnpx skills add plugin87/ux-ui-agent-skills --skill design-componentgit clone --depth 1 https://github.com/plugin87/ux-ui-agent-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/plugin87/ux-ui-agent-skills/design-component)<a href="https://agentmods.dev/skills/plugin87/ux-ui-agent-skills/design-component"><img src="https://agentmods.dev/badge/skills/plugin87/ux-ui-agent-skills/design-component.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 | $0.00079 | $0.02544 |
| Opus 5 | $0.00039 | $0.01272 |
| Sonnet 5 | $0.00016 | $0.00509 |
| Haiku 4.5 | $0.00008 | $0.00254 |
Grade A, and why
design-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 4d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 4d ago First seen · 80 lines · 79 tokens per session scan A e35325764a67
design-component is a skill published in the GitHub repository plugin87/ux-ui-agent-skills (871 stars, last pushed 8d ago), with no licence file. It adds 79 tokens to every session and 2,544 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-30.
Other skills, from other repositories
releasing
Authoring a changeset, or cutting a release for @vuetify/v0 and the @paper/ design systems. Use when writing a .changeset/.md file, deciding what belongs in changelog copy, re-entering or exiting changesets pre/beta mode, or reviewing a Version Packages PR. Covers the changeset content contract, the two version…
angular-best-practices
Official Angular v22 coding best practices — signals, standalone, native control flow, zoneless, host bindings, Signal Forms, inject(), and accessibility (WCAG AA / AXE). Use whenever writing, generating, or reviewing Angular/TypeScript code in this repo.
update-component
Audits and updates an existing component — source, story, and spec doc — fixing violations, story gaps, and spec drift. Always plans changes and waits for approval before writing any files. Use when a component needs to be brought up to standard, or when asked to fix, update, or improve a specific existing component.
add-component-source
Creates the source file, barrel index, and package export for a new component in @agentic-ds/core or @agentic-ds/agents — with the correct ARIA live region, semantic tokens, and CSS scoping applied from the start. Use when creating just a component's implementation file (no story, tests, or docs), or as step 1 of the…
add-component-spec
Creates the colocated .doc.ts spec next to an existing component's source — a typed ComponentDoc object with token inventory, props, and accessibility requirements with WCAG SC references. Use when a component is missing its doc, when documenting a component, or as step 4 of the /add-component flow.
verify-component-figma
Pixel-compares a component's live Storybook rendering against its Figma design node and reports a numeric diff percentage plus a saved diff image — actual visual fidelity, not a props/token read. Use whenever the user asks whether a component "matches Figma," "looks right compared to the design," wants a "Figma diff"…