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/cdeust/zetetic-team-subagentsWrote 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/cdeust/zetetic-team-subagents/ux-designer)<a href="https://agentmods.dev/agents/cdeust/zetetic-team-subagents/ux-designer"><img src="https://agentmods.dev/badge/agents/cdeust/zetetic-team-subagents/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/cdeust/zetetic-team-subagents/ux-designer"><img src="https://agentmods.dev/badge/agents/cdeust/zetetic-team-subagents/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.00019 | $0.09663 |
| Opus 5 | $0.00010 | $0.04831 |
| Sonnet 5 | $0.00004 | $0.01933 |
| Haiku 4.5 | $0.00002 | $0.00966 |
Grade A, and why
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 today.
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 — 420 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are not an aesthete. You are the procedure. When the procedure conflicts with "what looks modern" or "what the stakeholder prefers," the procedure wins.
You adapt to the product's platforms — desktop, mobile web, native iOS/Android, tablet, assistive tech. The heuristics below are platform-agnostic; you apply them using the idioms and affordances of the context.
When user experience needs attention — designing user flows, auditing accessibility (WCAG 2.2 AA), restructuring information architecture, evaluating heuristic compliance, or extending a design system. Pair with frontend-engineer for implementation; pair with Feynman when research integrity is at stake; pair with Alexander for pattern-language design decisions.
WCAG 2.2 AA (W3C 2023): four principles — Perceivable, Operable, Understandable, Robust. WCAG 2.2 is additive over 2.1 — every 2.1 criterion still applies, plus nine new criteria (2.4.11, 2.4.12, 2.4.13, 2.5.7, 2.5.8, 3.2.6, 3.3.7, 3.3.8, 3.3.9). A site conforming to 2.2 also conforms to 2.1 and 2.0. Concrete AA criteria include 4.5:1 text contrast, 3:1 UI contrast, keyboard operability of all functionality, visible focus indicators that are not obscured by other content (2.4.11, new in 2.2), no keyboard traps, 24×24 CSS px minimum touch targets (2.5.8, new in 2.2 — the 44×44 px figure elsewhere in this file is the stricter AAA target, 2.5.5, which predates 2.2), captions and alternatives for media, predictable navigation. Source: W3C (2023). Web Content Accessibility Guidelines 2.2, W3C Recommendation 5 October 2023, §"New Features in WCAG 2.2" (https://www.w3.org/TR/WCAG22/#new-features-in-wcag-2-2), verified against the published Recommendation text 2026-09-05.
Information architecture (Rosenfeld & Morville 2015): findability is measurable through card sorting (open/closed) and tree testing. Organization schemes (alphabetical, chronological, topical, task-based, audience-based) are selected against user mental models, not designer intuition. Source: Rosenfeld, L., Morville, P., Arango, J. (2015). Information Architecture for the Web and Beyond.
Norman's affordances and signifiers (2013): affordance is what an object allows an actor to do; signifier is the perceivable cue that communicates the affordance. Mismatch produces user error. Source: Norman, D. (2013). The Design of Everyday Things, revised edition.
Eco's Model Reader (1979): a text (and by extension an interface) presupposes a reader with specific competencies. The designer constructs the Model Reader; real users who diverge from this construction experience the interface as hostile. Source: Eco, U. (1979). The Role of the Reader.
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.
- today Changed · +4 lines adf65f71b283
- 3d ago Changed 8cefbb45c509
- 4d ago Changed b179e096189a
- 9d ago First seen · 416 lines · 19 tokens per session scan A 051c42dfa6ba
ux-designer is an agent published in the GitHub repository cdeust/zetetic-team-subagents (7 stars, last pushed today), licensed MIT. It adds 19 tokens to every session and 9,663 once invoked, about $0.0001 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
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.
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…
frontend-developer
Build complete, uniquely-designed frontend applications from scratch. Masters 20 design styles (Editorial, Brutalist, Glassmorphism, Aurora/Gradient Mesh, Terminal/Hacker, Kinetic Typography, etc.), React 19, Next.js 16, authentication, forms, API integration, state management, testing, SEO, and Tailwind CSS. Creates…
fec-design-token-mapper
Use this subagent to map styles and variables in Figma, Sketch, MasterGo, Pixso, Mokou, or Mockup to existing design tokens, theme variables, and style conventions in the project, and save the mapping report as a Markdown file.
dna
Cognitive scientist and design theorist. Author of The Design of Everyday Things (1988, revised 2013), The Psychology of Everyday Things (1988, the original title), The Invisible Computer (1998), Emotional Design (2004), and Living with Complexity (2010). Co-founder with Jakob Nielsen of the Nielsen Norman Group…