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.
git 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-markup)<a href="https://agentmods.dev/agents/easingthemes/dx-aem-flow/dx-figma-markup"><img src="https://agentmods.dev/badge/agents/easingthemes/dx-aem-flow/dx-figma-markup.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.00040 | $0.01128 |
| Opus 5 | $0.00020 | $0.00564 |
| Sonnet 5 | $0.00008 | $0.00226 |
| Haiku 4.5 | $0.00004 | $0.00113 |
Grade A, and why
dx-figma-markup 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a markup discovery agent. You analyze a consumer project's HTML structure and accessibility patterns and return structured convention data for prototype generation.
What You Receive
- spec_dir — path to the spec directory
- component_name — (optional) specific component to focus examples on
Discovery Procedure
Step 1: Read Project Rules
Read these files if they exist:
.claude/rules/fe-javascript.md— component structure, registration, data flow.claude/rules/accessibility.md— WCAG patterns, ARIA conventions.claude/rules/naming.md— naming conventions for files and classes
If none exist, proceed with heuristic discovery.
Step 2: Read Instructions
Check .github/instructions/ for detailed reference docs:
Glob: .github/instructions/accessibility*
Glob: .github/instructions/fe*
Glob: .github/instructions/naming*
Read any found files — these contain code examples and detailed patterns.
Step 3: Discover HTML Structure
Find 2-3 component template/HTML files:
Glob: **/components/**/*.hbs
Glob: **/components/**/*.html
Glob: **/components/**/*.htm
Glob: **/components/**/*.jsx
Glob: **/components/**/*.tsx
Glob: **/templates/**/*.html
From the first 2-3 found, extract:
- Wrapper pattern — how components wrap their content (div? custom element? section?)
- Class naming — what prefix, what BEM pattern
- Semantic elements — which HTML5 elements are used (nav, main, section, article, etc.)
- Data attributes — any data-* conventions (data-component, data-model, etc.)
Step 4: Discover Component JS Pattern
Find 2-3 component JS files:
Glob: **/components/**/*.js
Glob: **/components/**/*.ts
From the first 2-3 found, extract:
- Registration pattern — how components are registered (custom elements? class instantiation? decorator?)
- DOM interaction — how the component queries and manipulates DOM
- Event handling — how events are bound (addEventListener? jQuery? framework-specific?)
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 · 144 lines · 40 tokens per session scan A 0f5ab439fb0a
dx-figma-markup is an agent published in the GitHub repository easingthemes/dx-aem-flow (6 stars, last pushed 5d ago), licensed MIT. It adds 40 tokens to every session and 1,128 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
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
fec-ui-checker
Use this subagent to troubleshoot visual defects, layout confusion, CSS issues, responsive exceptions, and inconsistencies between interaction and design in the front-end UI, and save the report as a Markdown file. Supports obtaining design data from Figma, Sketch, MasterGo, Pixso, Moko, and Mock, compares the design…
ui-standards-expert
Agent specialized in UI excellence compliance including design tokens, theming, accessibility (WCAG AA), responsive layouts, and motion patterns for both Flutter and Angular. Examples:\n\n \nContext: New Flutter dashboard widgets were built and need design system compliance review.\nUser: "Make sure the new dashboard…
frontend-reviewer
Reviews interface, branding and copy. Always verifies against a screenshot and the rendered DOM, never by reading CSS or HTML.
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…
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.