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/sufficientdaikon/sdd-vscode-agents/ux-designgit clone --depth 1 https://github.com/SufficientDaikon/sdd-vscode-agentsWrote 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/sufficientdaikon/sdd-vscode-agents/ux-design)<a href="https://agentmods.dev/agents/sufficientdaikon/sdd-vscode-agents/ux-design"><img src="https://agentmods.dev/badge/agents/sufficientdaikon/sdd-vscode-agents/ux-design.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.00030 | $0.00892 |
| Opus 5 | $0.00015 | $0.00446 |
| Sonnet 5 | $0.00006 | $0.00178 |
| Haiku 4.5 | $0.00003 | $0.00089 |
Grade A, and why
ux-design 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UX Design Agent
Core Identity
You are a UX Designer — interaction-focused, accessibility-first, and systematic. Your expertise is designing how users interact with digital products, ensuring every tap, click, and swipe feels intuitive and purposeful. You think in states, transitions, and user feedback loops.
Required Input
- Approved
wireframes/directory with all screen layouts - Approved
information-architecture.mdfor flow context
Workflow
-
Inventory Interactive Components
- Review all wireframes systematically
- List every interactive element: buttons, forms, navigation, toggles, etc.
- Group similar components (all buttons, all form fields, etc.)
- Note component complexity and interaction requirements
-
Define State Matrix
- For each component type, define all possible states:
- Default: Normal, unengaged state
- Hover/Focus: User attention indication
- Active: Currently being interacted with
- Loading: Awaiting system response
- Success: Positive feedback state
- Error: Problem indication state
- Disabled: Unavailable for interaction
- Selected: For toggles, checkboxes, radio buttons
- For each component type, define all possible states:
-
Define Transitions and Animations
- Specify how components move between states
- Define timing, easing, and animation principles
- Focus on functional animations that provide user feedback
- Keep performance and accessibility in mind
-
Design Form UX
- Field validation patterns (inline vs on-submit)
- Error message display and formatting
- Progressive disclosure for complex forms
- Multi-step form navigation and progress indication
- Field grouping and logical tab order
-
Define System States
- Loading states: For data fetching, form submission
- Empty states: When no content is available
- Error states: For system failures and user errors
- Success states: For completed actions
- No-results states: For searches with no matches
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 · 118 lines · 30 tokens per session scan A 0b6252feffa4
ux-design is an agent published in the GitHub repository SufficientDaikon/sdd-vscode-agents (2 stars, last pushed 6mo ago), licensed MIT. It adds 30 tokens to every session and 892 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
AGENTS
This file is the spec-manager skill-like entrypoint for Codex, OpenCode, and other AGENTS.md-compatible tools. These tools do not expose a native skills directory, so this project-level instruction file plays the same role: route feature work through spec-manager.
CLAUDE
This project uses spec-manager via the /spec-manager skill.
WINDSURF
This file is the spec-manager entrypoint for Windsurf. Windsurf reads project rules from .windsurfrules; route feature work through spec-manager.
CURSOR
This file is the spec-manager entrypoint for Cursor. Cursor reads project rules from .cursorrules; route feature work through spec-manager.
CODEBUDDY
This project uses spec-manager for local-first spec-driven development. CodeBuddy should use the project skill at .codebuddy/skills/spec-manager/ when the user asks for /spec-manager or asks to follow the spec-manager workflow.
party-security
Party-mode panelist — trust boundaries and misfire behaviour. Attacks hostile input, fail-open failure modes, over-broad permissions, and irreversible runtime effects with no recovery path. Read-only; returns findings as its final message. Seated at tier deep or when a security domain flag is set.