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 epam/ai-dial-ui-kit --skill figmagit clone --depth 1 https://github.com/epam/ai-dial-ui-kitWrote 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/epam/ai-dial-ui-kit/figma)<a href="https://agentmods.dev/skills/epam/ai-dial-ui-kit/figma"><img src="https://agentmods.dev/badge/skills/epam/ai-dial-ui-kit/figma/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/epam/ai-dial-ui-kit/figma"><img src="https://agentmods.dev/badge/skills/epam/ai-dial-ui-kit/figma.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.00032 | $0.01200 |
| Opus 5.5 | $0.00013 | $0.00480 |
| Sonnet 5 | $0.00006 | $0.00240 |
| Haiku 4.5 | $0.00003 | $0.00120 |
Grade A, and why
figma 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 6d 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Figma Design-to-Code
Overview
Translate Figma designs into production-ready React components that match this repository's conventions: React 19, TypeScript, Tailwind CSS + SCSS, Storybook, and Vitest in @epam/ai-dial-ui-kit.
When to Use
- User shares a
figma.comURL - User says "implement this design" or "build this screen"
- User asks to match a Figma component or layout
Workflow
Step 1 — Fetch the design
Call get_design_context with the fileKey and nodeId extracted from the URL.
URL parsing rules:
figma.com/design/:fileKey/...?node-id=:nodeId→ replace-with:in nodeIdfigma.com/board/:fileKey/...→ FigJam file, useget_figjaminstead
If the design context includes Code Connect snippets, prefer those — they map directly to codebase components.
Step 2 — Map design to existing UI kit components first
Before writing any new code, check whether existing components already cover the design:
| Design need | Check first |
|---|---|
| Buttons, inputs, popups, tabs, loaders | src/components/ |
| Types and models | src/types/ and src/models/ |
| Reusable behavior | src/hooks/ and src/utils/ |
| Icons and icon wrappers | src/assets/icons/ and src/components/Icon/ |
Search the codebase before building from scratch:
rg "Dial|ComponentName" src/components
Step 3 — Implement
- Create or update files under
src/components/<ComponentName>/ - Keep exported component names prefixed with
Dial(for example,DialButton) - Use TypeScript + TSX only
- Use Tailwind classes and existing tokens/utilities; avoid inline styles and hardcoded design values
- Use
mergeClassesfromsrc/utils/merge-classeswhen class composition is non-trivial - Keep accessibility parity with the design (labels, roles, keyboard interactions, focus handling)
- Preserve existing visual language and patterns from nearby components
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.
- 6d ago First seen · 141 lines · 32 tokens per session scan A 86439c5a1d45
figma is a skill published in the GitHub repository epam/ai-dial-ui-kit (10 stars, last pushed today), licensed Apache-2.0. It adds 32 tokens to every session and 1,200 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-09-19.
Other skills, from other repositories
forge
Forge design system for React. Use when writing any React UI in this project, when picking which component to use, when theming, when creating block templates, or when reviewing UI code for accessibility and anti-patterns. Covers components, tokens, theming, motion, patterns, a11y, and anti-patterns.
shadcn
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json…
popular-web-designs
54 real design systems (Stripe, Linear, Vercel) as HTML/CSS.
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
chakra-ui-refactor
Review, convert, and improve UI code using Chakra UI v3. Use this skill whenever a user wants to review Chakra UI code for issues, convert plain HTML/CSS, Tailwind, CSS Modules, or styled-components to Chakra UI, clean up messy Chakra components, fix layout structure or token usage, or asks anything like "is this…
tamagui
Universal React UI framework for web and native. Use when building cross-platform apps with Tamagui, creating styled components with styled(), configuring design tokens/themes, using Tamagui UI components, or working with animations. Triggers: "tamagui", "styled()", "$token", "XStack/YStack", "useTheme", "@tamagui/"…