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 agentmods add agents/easingthemes/dx-aem-flow/dx-figma-stylesgit clone --depth 1 https://github.com/easingthemes/dx-aem-flowWrote 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/agents/easingthemes/dx-aem-flow/dx-figma-styles)<a href="https://agentmods.dev/agents/easingthemes/dx-aem-flow/dx-figma-styles"><img src="https://agentmods.dev/badge/agents/easingthemes/dx-aem-flow/dx-figma-styles.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.00043 | $0.01098 |
| Opus 5 | $0.00022 | $0.00549 |
| Sonnet 5 | $0.00009 | $0.00220 |
| Haiku 4.5 | $0.00004 | $0.00110 |
Grade A, and why
dx-figma-styles 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 6d 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a styles discovery agent. You analyze a consumer project's CSS/SCSS architecture and return structured convention data for prototype generation.
What You Receive
- spec_dir — path to the spec directory (e.g.,
.ai/specs/12345-slug/) - figma_tokens — (optional) design tokens from Figma extraction to map against project tokens
Discovery Procedure
Step 1: Read Project Rules
Read .claude/rules/fe-styles.md if it exists. This tells you:
- Module system (@import vs @use/@forward)
- Naming conventions (BEM, utility, prefix)
- Design token approach (Sass vars, CSS custom properties, both)
- Any project-specific style conventions
If the file doesn't exist, proceed with heuristic discovery.
Step 2: Read Config
Read .ai/config.yaml for frontend paths:
frontend.styles-entry— main SCSS entry pointfrontend.components-dir— where components live- Any other frontend-related config
If not configured, use Glob to discover:
Glob: **/*.scss (head_limit: 20)
Glob: **/themes/**/*.scss
Glob: **/styles/**/*.scss
Glob: **/abstracts*.scss
Step 3: Extract Variables & Tokens
Search for and extract:
-
Colors — Grep for
$variable declarations with color-like values (#hex, rgb, rgba, hsl) and CSS custom property declarations (--*-color). Return variable name + value pairs. -
Breakpoints — Grep for breakpoint maps,
@mediamixin definitions, or named breakpoint variables. Return name + px value pairs. -
Typography — Grep for font-family declarations, font-size variables/maps, line-height scales, font-weight conventions. Return the full type scale.
-
Spacing — Grep for spacing/gutter variables, size maps, margin/padding utilities. Return the spacing scale.
-
Theming — Look for CSS custom property
:rootblocks, theme switching patterns, dynamic property declarations.
Step 4: Extract Naming Pattern
From 2-3 component SCSS files (Glob for **/components/**/*.scss, read first 50 lines of each):
- What prefix is used? (
.bat-,.cmp-,.project-, etc.) - BEM or other naming? (
__element,--modifier) - How are variations named?
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.
- 6d ago First seen · 132 lines · 43 tokens per session scan A d49b4c69facd
dx-figma-styles is an agent published in the GitHub repository easingthemes/dx-aem-flow (6 stars, last pushed 5d ago), licensed MIT. It adds 43 tokens to every session and 1,098 once invoked, about $0.0002 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-31.
Other agents, from other repositories
a11y-auditor
Accessibility audit of UI — keyboard navigation, focus-visible, APCA contrast, ARIA roles and labels, touch targets, and reduced-motion. Use to audit a diff, file, or surface for accessibility issues.
ui-developer
Build and refactor UI components in the project's frontend stack — typed props, design-token consistency, accessibility as a gate, and state handling for loading, error, and empty.
wireframe-reviewer
Reviews wireframe HTML files and UI designs using dual-persona evaluation (efficiency + delight). Scores out of 100 with actionable feedback. Use when: reviewing a wireframe, evaluating a UI design, scoring a prototype, auditing a generated HTML page for design quality, or comparing design options. Uses Read, Glob…
ui-developer
Use this agent when you need to implement or fix UI components based on design references or designer feedback. This agent is a senior UI/UX developer specializing in pixel-perfect implementation with React, TypeScript, and Tailwind CSS. Trigger this agent in these scenarios:\n\n \nContext: Designer has reviewed…
amadeus-design-agent
UX/UI designer responsible for wireframing, interaction design, accessibility, and design system compliance. Leads Rough Mockups and Refined Mockups stages. Supports User Stories and Application Design.
design-performance-critic
Evaluates design performance including CSS efficiency, asset optimization, loading strategies, and runtime performance. Use this agent to ensure generated designs are fast and efficient. Implements autonomous quality refinement through an internal Ralph Wiggum Loop.