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 punkadillo/figma-code-composer --skill figma-analyze-framegit clone --depth 1 https://github.com/punkadillo/figma-code-composerWrote 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/punkadillo/figma-code-composer/figma-analyze-frame)<a href="https://agentmods.dev/skills/punkadillo/figma-code-composer/figma-analyze-frame"><img src="https://agentmods.dev/badge/skills/punkadillo/figma-code-composer/figma-analyze-frame.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.00019 | $0.02048 |
| Opus 5 | $0.00010 | $0.01024 |
| Sonnet 5 | $0.00004 | $0.00410 |
| Haiku 4.5 | $0.00002 | $0.00205 |
Grade A, and why
figma-analyze-frame 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 3d 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 — 296 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyze Figma Frame
Name
figma:figma-analyze-frame - Analyze Figma frame structure and implementation guidance
Synopsis
Analyze a Figma frame's hierarchy, styling, layout, interactivity, and provide comprehensive implementation recommendations including HTML structure, CSS approach, component breakdown, accessibility considerations, and responsive strategy.
Description
You are tasked with analyzing a Figma frame to understand its structure, properties, and provide implementation guidance. This command provides detailed technical analysis to help engineers understand how to implement a design.
Implementation
Uses Figma Desktop MCP server to access frame properties, layers, styling, and layout information. Analyzes component instances, auto-layout configurations, constraints, and design tokens to generate actionable implementation guidance.
Your Task
-
Access the Frame:
- Use Figma MCP tools to access the specified frame
- Accept either selection-based or link-based input
- If neither provided, ask the user to select a frame or provide a URL
-
Analyze Structure:
- Identify the frame hierarchy (parent-child relationships)
- List all layers and their types (text, rectangle, group, component, etc.)
- Note frame layout method (auto-layout, fixed, absolute positioning)
- Identify any component instances used
-
Analyze Styling:
- Extract colors (fills, strokes, shadows)
- Note typography properties (font, size, weight, line height)
- Identify spacing and sizing values
- Check for design token usage
- Note effects (shadows, blurs, etc.)
-
Analyze Layout:
- Describe layout system (flexbox equivalent, grid, absolute)
- Note responsive behavior (constraints, resizing rules)
- Identify spacing patterns (padding, gaps, margins)
- Check alignment and distribution
-
Analyze Interactivity:
- Identify interactive elements (buttons, links, inputs)
- Note any prototyping connections or interactions
- Check for states (hover, active, disabled, etc.)
- Identify any component variants for different states
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.
- 3d ago First seen · 296 lines · 19 tokens per session scan A 1d0df2140efb
figma-analyze-frame is a skill published in the GitHub repository punkadillo/figma-code-composer (3 stars, last pushed 19d ago), licensed MIT. It adds 19 tokens to every session and 2,048 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
mcp-host-styling-integration
Integrates MCP App UI with host theming system. Applies host CSS variables, handles onhostcontextchanged, safe area insets, display mode detection, and fullscreen configuration.
moai-design-tools
Design tool integration specialist covering Figma MCP, Pencil renderer, and Pencil-to-code export. Use when fetching design context from Figma, rendering Pencil designs, or exporting to React/Tailwind code.
ux-design
Create comprehensive UX design with user flows, wireframes, and design systems.
moai-domain-uiux
UI/UX design systems specialist covering accessibility, icons, theming, design tokens, and user experience patterns. Use when working on design systems, WCAG compliance, ARIA patterns, or dark mode theming.
figma-codegen
Generate framework-aware code from a Figma design. Reads the project's stack profile and emits code matching the existing framework (React/Vue/Svelte/Next/etc.) and styling (Tailwind/CSS/CSS-in-JS), reusing existing components and design tokens instead of regenerating from scratch. Triggers whenever the user wants a…
figma-build
Build a Figma design from code or a description — the reverse of figma-codegen. Reuses the connected file's existing design system (components, variables, styles) instead of drawing primitives with hardcoded values. Triggers whenever the user wants something created or updated IN Figma from code or a spec — e.g.…