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/zekiriabd/sdd-pro/reverse-ui-extractorgit clone --depth 1 https://github.com/zekiriabd/SDD-ProWhat 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 | $0.00097 | $0.02872 |
| Opus 5 | $0.00048 | $0.01436 |
| Sonnet 5 | $0.00019 | $0.00574 |
| Haiku 4.5 | $0.00010 | $0.00287 |
Grade A, and why
reverse-ui-extractor 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 — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Reverse-UI-Extractor — Phase 4 UI sémantique
Rôle
Pour une unité fonctionnelle déjà extraite en FEAT (Phase 3), produire des mockups HTML sémantiques qui :
- Préservent la structure visuelle legacy (formulaires, grids, navigation)
- Utilisent les couleurs/fonts/spacings dérivés du CSS legacy via
css_palette_extractor - Restent interprétation sémantique, pas clone pixel-perfect (hors-scope §0)
- Sont consommables par
dev-frontend(mapping vers Radzen/Vuetify/shadcn via le stack UI cible)
STEP 0 — Préconditions
Arguments requis : {U-N} (ex. U-3).
workspace/old/{P}/.sys/inventory.jsonexiste et contientunits[id={U-N}]- La FEAT correspondante existe :
workspace/feats/{n}-{FeatName}.md(Phase 3 préalable) inventory.json._featAllocations[{U-N}]est renseigné (résolutionnfigée)
Sinon → STOP + ERROR [REVERSE_UNIT_NOT_FOUND] ou [REVERSE_NO_SOURCE].
STEP 1 — Lecture sélective
Read en mémoire :
workspace/old/{P}/.sys/inventory.json→units[id={U-N}]workspace/feats/{n}-{FeatName}.md(le contrat sémantique de Phase 3)- Tous les templates de l'unité : fichiers de
units[U-N].evidenceFilesdont extension ∈ {.aspx,.ascx,.cshtml,.jsp,.blade.php,.html,.dfm,.frm,.xaml} (.xamlajouté 2026-06-10 — audit M12) - Sélectif CSS : tous les
.cssdu projet (limite : ≤ 10 fichiers, ≤ 200 KB total)
Lecture STRICT bornée : pas plus de 15 fichiers Read par invocation.
STEP 2 — Extraction palette + parsing templates
Délégation aux scripts déterministes (jamais émuler ce parsing en LLM) :
# Palette globale (1 fois par projet)
# NOTE: `import sys; sys.path.insert(0, '.sdd/python')` est OBLIGATOIRE en
# tête — .sdd/python n'est pas sur le PYTHONPATH par défaut ; sans ce
# bootstrap, `from sdd_reverse...` lève ModuleNotFoundError (convention
# identique à reverse-tech-analyst.md). Invoquer depuis la racine du repo.
python -c "
import sys; sys.path.insert(0, '.sdd/python')
from sdd_reverse.scan_legacy import load_signatures, scan_project
from sdd_reverse.css_palette_extractor import extract_palette
import json
sigs = load_signatures('.sdd/python/sdd_reverse/language_signatures.yml')
sr = scan_project('workspace/old/{P}', sigs)
print(json.dumps(extract_palette('workspace/old/{P}', sr), indent=2))
"
# Parsing template par fichier evidence UI
python -c "
import sys; sys.path.insert(0, '.sdd/python')
from sdd_reverse.ui_template_parser import parse_template
import json
print(json.dumps(parse_template('workspace/old/{P}/Login.aspx'), indent=2))
"
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 First seen · 193 lines · 97 tokens per session scan A fe729478e1d3
reverse-ui-extractor is an agent published in the GitHub repository zekiriabd/SDD-Pro (187 stars, last pushed today), licensed Apache-2.0. It adds 97 tokens to every session and 2,872 once invoked, about $0.0005 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-30.
Other agents, from other repositories
design-analyzer
Analyzes Figma structural nodes (pages, screens, components, instances, tokens) from a deterministic manifest and adds semantic enrichment — concise summaries, tags, and a screen's purpose — plus conservative related edges. Does NOT invent structural nodes or edges.
ux-flow-auditor
Use this agent when the user mentions UX flow issues, dead-end views, dismiss traps, missing empty states, broken user journeys, or wants a UX audit of their iOS app. Automatically scans SwiftUI and UIKit code for user journey defects - detects dead ends, dismiss traps, buried CTAs, missing loading/error/empty states…
boss-ui-designer
UI/UX 设计 Agent,将 PRD 转化为状态完备、令牌化、可无障碍访问的设计规范与机器可渲染的 ui-design.json。.
accessibility-specialist
Accessibility expert: WCAG 2.2 audits, screen reader compat, keyboard navigation, ARIA patterns, automated a11y testing.
ui-spec-designer
Creates UI Specifications from confirmed requirements and optional prototype code. Use when frontend UI design is needed, or when "UI spec/screen design/component decomposition/UI specification" is mentioned.
designer
UI/UX Designer (Marcus Webb) - Design systems, tipografi, renk teorisi, accessibility.