Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/PMDevSolutions/Aureliusnpx agentmods add skills/pmdevsolutions/aurelius/figma-intakeWrote 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/pmdevsolutions/aurelius/figma-intake)<a href="https://agentmods.dev/skills/pmdevsolutions/aurelius/figma-intake"><img src="https://agentmods.dev/badge/skills/pmdevsolutions/aurelius/figma-intake/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/pmdevsolutions/aurelius/figma-intake"><img src="https://agentmods.dev/badge/skills/pmdevsolutions/aurelius/figma-intake.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.00000 | $0.03091 |
| Opus 5.5 | $0.00000 | $0.01236 |
| Sonnet 5.5 | $0.00000 | $0.00618 |
| Haiku 4.5 | $0.00000 | $0.00309 |
Grade A, and why
figma-intake 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 yesterday.
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 — 299 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Figma Intake — Structured Discovery
Purpose
Gather everything needed to build a React app from a Figma design in a single structured pass. Auto-discovers what it can, asks the user only what it must, and outputs a machine-readable build-spec.json that downstream skills consume without re-asking questions.
When to Use
- First phase of
/build-from-figmapipeline - Any time a user provides a Figma URL and wants to build from it
- When you need to understand a Figma file's structure before generating code
Inputs
- Required: Figma file URL (with optional node-id)
- Optional: Existing project directory to integrate into
Process
Step 0: Conversation Fast-Path (Skip the Interview)
If .claude/plans/build-spec.json already exists with "source": "conversation", the spec was produced by the conversation-intake skill and the Figma file was generated from it by design-brief-to-figma — the interview already happened in /build-from-conversation. Do not re-interview the user. Instead:
1. Verify the spec's figma block is populated (fileKey, url) and matches the
URL this skill was invoked with. Mismatch → ask which file wins.
2. Verify the file is reachable: get_metadata(fileKey).
3. Backfill any pages[].figmaNodeId that is still null from the metadata
(match generated frames to pages by name/order).
4. Keep "source": "conversation" unchanged — downstream phases treat the spec
exactly like a Figma-sourced one; the source value preserves provenance.
5. Expect no Figma variables in the generated file: token extraction
(design-token-lock) will fall back to computed styles, which is correct
here because the captured mockups were rendered from the design brief's
exact values.
6. Skip Steps 1-3 below entirely and proceed to Step 4 validation /
Step 5 confirmation only if the spec is incomplete; otherwise report
"fast-path: spec reused" and hand control back to the pipeline (Phase 2).
If the file at figma.url no longer exists, fall through to the normal flow below using the URL the user provided.
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.
- yesterday Changed · +1 lines 555aa5e51349
- 1mo ago First seen · 298 lines · 0 tokens per session scan A b4c541b25d0e
figma-intake is a skill published in the GitHub repository PMDevSolutions/Aurelius (9 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,091 tokens. 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-04.
Other skills, from other repositories
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 Developer
Extract components from Figma, convert designs to React components, sync design tokens, and generate code from designs. Bridge the gap between design and code with automated workflows.
high-plains-drifter
Align a design to your real Storybook components instead of reconstructing it. Use when turning a Figma frame into React built from an existing component library (Build mode), or when pulling scrappy exploratory code into line with the library once a direction feels right (Align mode). Triggers include "build this…
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.…
figma-to-code
Generate production-ready React/Next.js code from Figma designs. Instructs proper Figma MCP tool usage, component reuse strategies, and variant mapping. CRITICAL: ALWAYS use this skill when user provides a Figma link or mentions implementing/redesigning from Figma design. Never attempt manual implementation without…
vibefigma
Convert Figma designs to production-ready React components with Tailwind CSS. Use when user provides a Figma URL, asks to convert Figma designs to React/code, wants to extract components from Figma, or mentions "vibefigma". Requires a Figma access token (via --token flag, FIGMATOKEN env var, or .env file).