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/easingthemes/dx-aem-flownpx agentmods add skills/easingthemes/dx-aem-flow/dx-figma-prototypeWrote 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/easingthemes/dx-aem-flow/dx-figma-prototype)<a href="https://agentmods.dev/skills/easingthemes/dx-aem-flow/dx-figma-prototype"><img src="https://agentmods.dev/badge/skills/easingthemes/dx-aem-flow/dx-figma-prototype/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/easingthemes/dx-aem-flow/dx-figma-prototype"><img src="https://agentmods.dev/badge/skills/easingthemes/dx-aem-flow/dx-figma-prototype.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.00048 | $0.02810 |
| Opus 5.5 | $0.00019 | $0.01124 |
| Sonnet 5.5 | $0.00010 | $0.00562 |
| Haiku 4.5 | $0.00005 | $0.00281 |
Grade A, and why
dx-figma-prototype 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 2d 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 — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You research the consumer project's frontend conventions, then generate a standalone high-fidelity HTML/CSS prototype that replaces Figma as the visual reference for all downstream implementation steps.
Use ultrathink for prototype generation — mapping design tokens to project conventions and producing pixel-accurate output requires deep reasoning.
1. Locate the Spec Directory
SPEC_DIR=$(bash .ai/lib/dx-common.sh find-spec-dir $ARGUMENTS)
If the script exits with error, ask the user for the work item ID.
2. Check Prerequisites
$SPEC_DIR/figma-extract.mdMUST exist. If not: printfigma-extract.md not found — run /dx-figma-extract firstand STOP.- Read
figma-extract.mdto confirm it has content.
3. Check Existing Output
- If
$SPEC_DIR/figma-conventions.mdAND$SPEC_DIR/prototype/index.htmlboth exist: - Check if
figma-extract.mdchanged since prototype was generated - If unchanged → print
prototype already up to date — skippingand STOP - If stale → continue (regenerate)
4. Phase A — Conventions Research
Launch three subagents in parallel using the Agent tool:
Subagent 1 — Styles (dx-figma-styles):
Agent tool:
subagent_type: dx-core:dx-figma-styles
prompt: |
Discover CSS/SCSS conventions for this project.
spec_dir: <$SPEC_DIR>
Figma design tokens to map against (from figma-extract.md):
<paste the Design Tokens section from figma-extract.md>
Return the full Styles Conventions report.
Subagent 2 — Markup (dx-figma-markup):
Agent tool:
subagent_type: dx-core:dx-figma-markup
prompt: |
Discover HTML and accessibility conventions for this project.
spec_dir: <$SPEC_DIR>
component_name: <component name from figma-extract.md>
Return the full Markup Conventions report.
Subagent 3 — Component Reuse (dx-figma-components):
Agent tool:
subagent_type: dx-core:dx-figma-components
prompt: |
Analyze the Figma design and find existing codebase components to reuse.
spec_dir: <$SPEC_DIR>
Figma design reference (from figma-extract.md):
<paste the Reference Code section and component name from figma-extract.md>
Identify every UI building block in the design (buttons, images, cards, inputs, etc.)
and search the codebase for existing components that match. Return the Component Reuse Map.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago Changed · -1 lines · -33 tokens per session afb61ec8d80a
- 19d ago Changed · -2 lines 9dc0cf185cf7
- 1mo ago First seen · 245 lines · 81 tokens per session scan A 7528cb3fa72c
dx-figma-prototype is a skill published in the GitHub repository easingthemes/dx-aem-flow (6 stars, last pushed 2d ago), licensed MIT. It adds 48 tokens to every session and 2,810 once invoked, about $0.0002 per session on Opus 5.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
anti-slop-design
Autonomous Principal Design Technologist. Cures vibe-coded software from AI frontend slop using curated token archetypes and 7-axis quality gating.
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-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.
frontend-visual-qa
Audits rendered UI and specific task/object-link handoffs; excludes ordinary source citations alone. Audits already-rendered UI and Markdown/Obsidian image layout — web app, deck/slide, dashboard, design-system, or Electron/native app — via real-browser/native-app journeys and a Playwright sweep. Use after UI…
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.