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 textura-agency/next16-claude-starter --skill figma-to-sectiongit clone --depth 1 https://github.com/textura-agency/next16-claude-starterWrote 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/textura-agency/next16-claude-starter/figma-to-section)<a href="https://agentmods.dev/skills/textura-agency/next16-claude-starter/figma-to-section"><img src="https://agentmods.dev/badge/skills/textura-agency/next16-claude-starter/figma-to-section/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/textura-agency/next16-claude-starter/figma-to-section"><img src="https://agentmods.dev/badge/skills/textura-agency/next16-claude-starter/figma-to-section.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00095 | $0.01205 |
| Opus 5 | $0.00048 | $0.00602 |
| Sonnet 5 | $0.00019 | $0.00241 |
| Haiku 4.5 | $0.00010 | $0.00120 |
Grade A, and why
figma-to-section 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 13d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Figma → section
Build from live Figma data, never from a text description, a summary you wrote earlier, or memory. Descriptions lose exactly the values that matter.
1. Extract, in this order
get_metadata— file structure, pages, top-level frames. Gives you thefileKeyand the node IDs.get_design_contexton the target node — exact text, colours, typography, spacing, layout, asset URLs. This is the source of truth for values.get_screenshoton the same node — the source of truth for layout: column count, direction, alignment, order, positioning.
Both. get_design_context will not tell you a layout reads as three columns;
the screenshot will not tell you the gap is 28px.
2. Record what you fetched
Write DESIGN-MAP.md at the repo root (gitignored or committed, user's call):
**Figma file key:** `<fileKey>`
**Source URL:** <url>
**Frame width:** <px> ← the design base width; check it against the adaptive grid
| Section | Node ID | View / component | Background | Notes |
|---------|---------|------------------|------------|-------|
| Hero | `1:234` | views/home → Hero | full-bleed image | h1 lives here |
Every section needs its node ID. QA and any later pass re-fetch from these — a section without a node ID cannot be verified against its design later.
3. Assets
get_design_context returns asset URLs that expire (~7 days). Download
immediately.
- Save to
public/assets/<section>/— one folder per section (obsidian/architecture/folder-structure.md). Meta/PWA assets stay atpublic/root. - kebab-case, prefixed by section:
hero-background.webp,team-jane-doe.webp,icon-arrow.svg. - Verify each file after download: run
file <path>. Figma often returns an SVG where you asked for a raster, or a PNG named.jpg. Rename to match the real type — a mismatched extension renders as a broken image. - Sanity-check size: a content photo under ~5KB is almost certainly a vector placeholder, not the intended export. Flag it; do not ship it.
- Prefer
.webp/.aviffor photos.next/imagewith explicitwidth/height. - If a download fails: use a placeholder, add a comment saying why, and tell the user immediately — never silently skip an asset.
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.
- 13d ago First seen · 99 lines · 95 tokens per session scan A 863eafa7db00
figma-to-section is a skill published in the GitHub repository textura-agency/next16-claude-starter (117 stars, last pushed 4d ago), licensed Unlicense. It adds 95 tokens to every session and 1,205 once invoked, about $0.0005 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
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…
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ultragoal with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
frontend-visual-qa
Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.
refactoring-ui
Audit and fix visual hierarchy, spacing, color, and depth in web UIs. Use when the user mentions "my UI looks off" (or amateur/unprofessional), "fix the design", "Tailwind styling", "color palette", "visual hierarchy", "design system", "spacing scale", or "component styling". Also trigger when building consistent…
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.