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 PMDevSolutions/Aurelius --skill design-brief-to-figmagit clone --depth 1 https://github.com/PMDevSolutions/AureliusWrote 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/design-brief-to-figma)<a href="https://agentmods.dev/skills/pmdevsolutions/aurelius/design-brief-to-figma"><img src="https://agentmods.dev/badge/skills/pmdevsolutions/aurelius/design-brief-to-figma.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.00122 | $0.01940 |
| Opus 5 | $0.00061 | $0.00970 |
| Sonnet 5 | $0.00024 | $0.00388 |
| Haiku 4.5 | $0.00012 | $0.00194 |
Grade A, and why
design-brief-to-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 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Brief to Figma — Generated Design Files
Purpose
Turn the design-brief.json produced by conversation-intake into an actual Figma file, so the standard /build-from-figma pipeline can run against it unchanged. The mechanism is HTML-mockup capture: mcp__figma__generate_figma_design imports a rendered web page into an existing Figma file pixel-perfectly, so this skill renders the brief as static HTML first, then captures each page. The generated file becomes the single visual source of truth — Phase 5 pixel-diffs the built app against frames created here.
When to Use
- Phase C1 of
/build-from-conversation, immediately afterconversation-intake - Any time a confirmed
design-brief.json+build-spec.jsonpair exists and a Figma file needs to be generated from it
Inputs
- Required:
.claude/plans/design-brief.jsonand.claude/plans/build-spec.json(with"source": "conversation") - Reads:
.claude/pipeline.config.json→conversation.designGeneration(mockupDir,mockupServerPort,reviewBeforeHandoff,maxRegenerationAttempts,capturePollIntervalMs,capturePollMaxAttempts) andconversation.retry
Process
Step 1: Preflight — Figma Auth and Plan
1. Call mcp__figma__whoami
→ Confirms authentication and returns the user's plans
2. Resolve planKey:
- Exactly one plan → use its `key` field verbatim
- Multiple plans → ask the user which team/organization to use (one question)
3. If the Figma MCP is unavailable or unauthenticated, stop here —
report it and leave the brief/spec artifacts intact for a later resume
Step 2: Render the Brief as HTML Mockups
Dispatch the conversation-designer agent to write one self-contained HTML mockup per page in build-spec.json > pages[] into conversation.designGeneration.mockupDir (default .claude/design-mockups/):
For each page: <mockupDir>/<route-slug>.html (e.g. dashboard.html, settings.html)
The agent definition owns the mockup quality bar (deterministic, no JS, exact brief values, real text content, data-section landmarks). After generation, record each page's mockupPath in build-spec.json.
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 · 145 lines · 0 tokens per session scan A 052d0d011f6e
design-brief-to-figma is a skill published in the GitHub repository PMDevSolutions/Aurelius (8 stars, last pushed 23d ago), licensed MIT. It adds 122 tokens to every session and 1,940 once invoked, about $0.0006 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-04.
Other skills, from other repositories
mk:figma
Read-first Figma gateway via Figma MCP: analyze designs, implement Figma-to-code for 1–3 screens, extract design tokens, produce a Figma Evidence Packet for planning handoff, screenshot fallback. Advanced operations (Code Connect, canvas writes, design-system/library patterns) are gated references loaded only on…
taiyi-ui-design
A design-planning guide for describing how an application's user interface should look and behave. It produces a UI-DESIGN.md document covering layouts, components, interactions, accessibility, and error states.
taiyi-diagram-arch
A workflow for turning written system or product architecture into readable, version-controlled diagrams using Mermaid or exported SVG and PNG files. Architecture diagrams show components, boundaries, data flows, and deployment relationships.
taiyi-restyle
A planning guide for breaking a large user-interface redesign into smaller, independently reviewable tasks. A user interface is the part of an application that people see and use.
taiyi-diagram-render
A tool for rendering existing C4 or architecture Mermaid diagrams as SVG or PNG images. C4 is a way to show software systems at different levels, while Mermaid is a text format for diagrams.
taiyi-diagram-pipeline
A pipeline that creates and updates architecture diagrams in three stages: a C4 model from the code, an engineering architecture diagram, and an exported PNG image. C4 is a way to describe software architecture at several levels of detail.