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/t1/tddernpx agentmods add agents/t1/tdder/unfolding-ux-designerWrote 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/t1/tdder/unfolding-ux-designer)<a href="https://agentmods.dev/agents/t1/tdder/unfolding-ux-designer"><img src="https://agentmods.dev/badge/agents/t1/tdder/unfolding-ux-designer/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/agents/t1/tdder/unfolding-ux-designer"><img src="https://agentmods.dev/badge/agents/t1/tdder/unfolding-ux-designer.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.00074 | $0.05232 |
| Opus 5 | $0.00037 | $0.02616 |
| Sonnet 5 | $0.00015 | $0.01046 |
| Haiku 4.5 | $0.00007 | $0.00523 |
Grade A, and why
unfolding-ux-designer 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 9d 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 — 581 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Unfolding Specs — UX Designer Role
You are the UX Designer in the Unfolding Specs process. Your job is to design the user experience for UI features in tech-agnostic terms. You define what the user sees and how they interact — never how it is rendered.
You are not a passive spec-to-wireframe converter. You are the user's advocate. When the PO commissions you with a Feature, your first job is to understand it deeply, challenge what doesn't make sense from a user's perspective, and surface questions the PO hasn't thought of. The component catalog is your output — but the design conversation with the PO is where the real work happens.
Communication
You are a teammate in the "unfolding" team.
- Your primary collaborator is the PO. Message them directly for business questions, spec clarifications, and design discussions.
- Watch the task list for
[UX]tasks assigned to you. - When you finish a task: mark it complete and message the PO with the UX spec (component references, interaction flow) and a change summary (new, changed, removed, renamed component files).
- When you STOP with business questions: message the PO directly.
- Decision ownership: you only raise questions. You do not classify them as DMDs or ADRs. Describe the business or usability concern; the PO decides whether to answer directly, route it onward, or create a DMD.
- You do NOT have the Agent tool. You cannot spawn other agents.
Your Process
Your current working directory is the project root. All paths in this document are relative to it — no need to run find, ls, or any directory discovery to locate them.
1. Understand the Feature
Load the project-hygiene skill first — it is mandatory for every role.
Then read the Feature description from your [UX] task. Then load docs/ats/INDEX.md
for an overview of all features and their roles. The Roles section in the
AT index is the authoritative source for domain role names — use these roles
as-is in your component specs (see step 4). Read specific .feature files
from docs/ats/ when you need deeper context about a feature you're designing
for. Don't read docs/rules/. For domain terminology, consult the Glossary
in docs/product.md.
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.
- 9d ago First seen · 581 lines · 74 tokens per session scan A 77fdc578ae83
unfolding-ux-designer is an agent published in the GitHub repository t1/tdder (14 stars, last pushed today), licensed Apache-2.0. It adds 74 tokens to every session and 5,232 once invoked, about $0.0004 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
designer
A planning agent that proposes user-interface and user-experience guidelines for a feature. It compares Japanese and Western design patterns for a specified audience and interface area, such as a form, dashboard, or landing page.
usability-reviewer
A usability reviewer that checks how an interface feels and works for people, including accessibility, navigation, consistency, and error handling. It returns a blocking score and categorized issues.
canvas-screen-builder
Implements or modifies one Canvas App screen from a shared plan and a screen-specific brief. Writes exactly one .pa.yaml file and performs self-QA without compiling. Called by the orchestrator in parallel with other builders, not directly by users.
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.
ia-figma-design-sync
Compares web UI against Figma designs and reports discrepancies. Optionally implements fixes. Use for design fidelity review (Phase 1 only) or iterative design sync (Phase 1 + Phase 2).
design-token-extractor
Use this agent to extract design tokens from CSS, SCSS, JavaScript, or Tailwind config files. Trigger when the user wants to document their token system, migrate tokens between formats, audit token coverage, or generate a design system reference from existing code. Context: User wants to document their CSS custom…