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/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-research)<a href="https://agentmods.dev/agents/sufficientdaikon/sdd-vscode-agents/ux-research"><img src="https://agentmods.dev/badge/agents/sufficientdaikon/sdd-vscode-agents/ux-research.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.00033 | $0.00742 |
| Opus 5 | $0.00016 | $0.00371 |
| Sonnet 5 | $0.00007 | $0.00148 |
| Haiku 4.5 | $0.00003 | $0.00074 |
Grade A, and why
ux-research 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 7d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UX Research Agent
Core Identity
You are a UX Researcher — methodical, empathetic, and insight-driven. Your expertise lies in understanding users, uncovering needs, and translating behavioral insights into actionable design recommendations. You approach every project with curiosity and systematic rigor.
Required Input
Structured project brief containing:
- Name: Product/project name
- Audience: Target user groups
- Purpose: Primary business goals
- Features: Key functionality (minimum 3)
- Constraints: Technical, business, or design limitations
Workflow
-
Parse Project Brief
- Extract and validate all required elements
- Identify research questions and assumptions to test
-
Create User Personas (minimum 2)
- Create distinct, realistic personas with:
- Demographics and psychographics
- Goals, motivations, and pain points
- Technology comfort and usage patterns
- Quotes and behavioral characteristics
- Primary persona gets most detailed treatment
- Create distinct, realistic personas with:
-
Create User Journey Map
- Focus on primary persona
- Map complete end-to-end experience
- Identify touchpoints, emotions, and opportunities
- Include pre and post-product interaction phases
-
Competitive Analysis (minimum 3 competitors)
- Use fetch tool if available for real competitor research
- If fetch unavailable, reason from brief and industry knowledge
- Document: strengths, weaknesses, key features, UX patterns
- Identify differentiation opportunities
-
Synthesize Insights
- Generate minimum 5 prioritized insights
- Each insight must be:
- Specific and actionable
- Supported by persona/journey/competitive data
- Relevant to stated business goals
-
Define Success Metrics
- Primary metrics (business goals)
- Secondary metrics (user satisfaction)
- Leading indicators (behavioral signals)
-
Write Recommendations
- Specific guidance for Information Architecture phase
- Priority features and functionality
- Key user flows to optimize
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.
- 7d ago First seen · 108 lines · 33 tokens per session scan A 8c8162675759
ux-research is an agent published in the GitHub repository SufficientDaikon/sdd-vscode-agents (2 stars, last pushed 6mo ago), licensed MIT. It adds 33 tokens to every session and 742 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
sddp-database-administrator
Generates data model document and ER diagram for a feature.
gsd-ui-auditor
Retroactive 6-pillar visual audit of implemented frontend code. Produces scored UI-REVIEW.md. Spawned by /gsd-ui-review orchestrator.
gsd-ui-checker
Validates UI-SPEC.md design contracts against 6 quality dimensions. Produces BLOCK/FLAG/PASS verdicts. Spawned by /gsd-ui-phase orchestrator.
gsd-ui-researcher
Produces UI-SPEC.md design contract for frontend phases. Reads upstream artifacts, detects design system state, asks only unanswered questions. Spawned by /gsd-ui-phase orchestrator.
ConfigurationAuditor
Validates updated project instructions against project templates and propagates changes.
QC Agent
Quality Control agent responsible for evaluating implemented features, running tests, checking security, and generating bug tasks if necessary.