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 vanessamarely/ai-playbook-reposito --skill figma-component-buildergit clone --depth 1 https://github.com/vanessamarely/ai-playbook-repositoWrote 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/vanessamarely/ai-playbook-reposito/figma-component-builder)<a href="https://agentmods.dev/skills/vanessamarely/ai-playbook-reposito/figma-component-builder"><img src="https://agentmods.dev/badge/skills/vanessamarely/ai-playbook-reposito/figma-component-builder/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/vanessamarely/ai-playbook-reposito/figma-component-builder"><img src="https://agentmods.dev/badge/skills/vanessamarely/ai-playbook-reposito/figma-component-builder.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.00069 | $0.02217 |
| Opus 5 | $0.00034 | $0.01108 |
| Sonnet 5 | $0.00014 | $0.00443 |
| Haiku 4.5 | $0.00007 | $0.00222 |
Grade A, and why
figma-component-builder 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 11d 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: figma-component-builder
Purpose
- Automate conversion of Figma designs into React/TypeScript components and supporting artifacts for the selected project scope.
- Use the Figma MCP server to fetch design context and the Chrome MCP server to verify and test produced components in a running dev server.
Primary capabilities
- Retrieve design context (code snippets, screenshots, tokens) from Figma via the MCP endpoints.
- Map Figma nodes to existing code components (prefer reuse from the component library provided in the prompt).
- Generate
apply_patch-compatible diffs that add/modify component files (.tsx,.styles.ts,.test.tsx,.stories.tsx) inside the requestedscope:project folder. - Run Chrome MCP checks (visual snapshots, accessibility
axeaudits, console/network checks) against a dev server URL you provide.
Required initial prompt context
- The initial prompt MUST include all fields below so the skill can work in any client/project:
scope(required): target project folder under workspace root.destination_folder(required): exact destination folder name for generated component files.component_library(required): name of the preferred reusable UI/component library for this scope (usenoneif no shared library exists).client_context(required): short project-specific coding conventions (naming, tokens, styling approach, export rules).
Inputs
scope(required): target project folder under workspace root.destination_folder(required): exact folder where component files should be created or updated.component_library(required): preferred library/package/folder to reuse components from (ornone).client_context(required): project conventions and constraints for this request.figma_urlor{fileKey,nodeId}(required): Figma design URL or extracted fileKey + nodeId.screenshot_image(optional fallback): attached design screenshot to use when Figma access is unavailable.dev_url(optional): local dev server URL to test components (for example,http://localhost:3000).create_mode(optional):preview(generate patches only) |apply(generate patches and ask to apply).preferences(optional): additional coding preferences that override or refineclient_context.
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.
- 11d ago First seen · 137 lines · 69 tokens per session scan A 12a6378f4db9
figma-component-builder is a skill published in the GitHub repository vanessamarely/ai-playbook-reposito (2 stars, last pushed 1mo ago), licensed MIT. It adds 69 tokens to every session and 2,217 once invoked, about $0.0003 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
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…
frontend-ui-dark-ts
Build dark-themed React applications using Tailwind CSS with custom theming, glassmorphism effects, and Framer Motion animations. Use when creating dashboards, admin panels, or data-rich interfaces with a refined dark aesthetic.
cobejs
Use when adding a lightweight interactive globe with cobe (canvas setup, markers, interaction, performance, integration with React/Next.js).
stitch::react-components
Converts Stitch designs into modular Vite and React components, or syncs/updates existing React components to align with the latest Stitch designs, using system-level networking and AST-based validation.
seed-design
An integration guide for SEED Design, covering shared component specifications and foundations plus React and Lynx implementation guidance.
ss-studio
Turn a product brief and optional references into three distinct creative directions, a human-selected StyleSeed interaction plan, generated image/video asset jobs, a working UI prototype, and a verified prototype-first showcase reel. Use for client concepts, app interaction exploration, trendy but coherent UI…