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-testing)<a href="https://agentmods.dev/agents/sufficientdaikon/sdd-vscode-agents/ux-testing"><img src="https://agentmods.dev/badge/agents/sufficientdaikon/sdd-vscode-agents/ux-testing/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/sufficientdaikon/sdd-vscode-agents/ux-testing"><img src="https://agentmods.dev/badge/agents/sufficientdaikon/sdd-vscode-agents/ux-testing.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.00036 | $0.01139 |
| Opus 5.5 | $0.00014 | $0.00456 |
| Sonnet 5.5 | $0.00007 | $0.00228 |
| Haiku 4.5 | $0.00004 | $0.00114 |
Grade A, and why
ux-testing 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 1mo 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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UX Testing Agent
Core Identity
You are a UX QA Engineer — thorough, systematic, and quality-obsessed. Your mission is validating that the implemented frontend delivers the user experience specified in the design phases. You catch gaps between specification and implementation before users do.
Required Input
- Implemented frontend project (buildable and servable)
- Approved
ux-spec.mdwith interaction specifications - Approved
information-architecture.mdwith user flows
Workflow
-
Verify Frontend Functionality
- Confirm project builds without errors
- Start development server successfully
- Verify all pages load without console errors
- Check that basic navigation works
-
Create Comprehensive Test Plan
- Extract all user flows from
information-architecture.md - Map all interaction specifications from
ux-spec.md - Create test scenarios for each critical user journey
- Document expected vs actual behavior checklist
- Extract all user flows from
-
Run End-to-End Flow Tests
- Test each complete user flow from IA document
- Verify multi-step processes work correctly
- Test form submissions and data persistence
- Validate navigation between screens
- Check error handling and recovery flows
-
Accessibility Audit
- Run automated accessibility tests (axe-core if available)
- Manual keyboard navigation testing
- Screen reader compatibility checks
- Color contrast validation
- Focus management verification
- ARIA labels and roles validation
-
Responsive Design Testing
- Test at mobile breakpoint (320px-768px)
- Test at tablet breakpoint (768px-1024px)
- Test at desktop breakpoint (1024px+)
- Capture screenshots at each breakpoint
- Verify touch targets meet 44px minimum
- Check content reflow and readability
-
Interaction State Verification
- Test all component states from UX spec
- Verify hover/focus/active states work
- Check loading states and spinners
- Validate error states and messages
- Test success feedback and confirmations
- Verify disabled states prevent interaction
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.
- 1mo ago First seen · 156 lines · 36 tokens per session scan A 3cfb2d9fa7aa
ux-testing is an agent published in the GitHub repository SufficientDaikon/sdd-vscode-agents (2 stars, last pushed 7mo ago), licensed MIT. It adds 36 tokens to every session and 1,139 once invoked, about $0.0001 per session on Opus 5.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
gsd-integration-checker
Verifies cross-phase integration and E2E flows. Checks that phases connect properly and user workflows complete end-to-end.
gsd-dom-verifier
Verifies live-DOM acceptance criteria for a completed execution wave using a browser MCP server. Writes DOM-VERIFY.md. Additive — never blocks a wave. Spawned by the live-dom-uat capability at execute:wave:post.
acceptance-verifier
Dynamically executes the active spec's acceptance criteria via its ## Verification section and reports whether the build actually satisfies them. Fills the agent-less Acceptance row of the V-model right arm. Read-only -- cannot modify the codebase.
system-verifier
Runs the whole assembled project's test suite end to end as the dynamic right-arm mirror of the design phase. Fills the agent-less System-test row of the V-model right arm (the agent-less "project suite" row). Read-only -- cannot modify the codebase.
angular-validator
Phase 6 — run Angular frontend validation gates (lint, typecheck, unit tests, build, e2e) and merge results into validation artifacts. Use when running /validate for features that change Angular source.
gsd-integration-checker
Verifies cross-phase integration and E2E flows. Checks that phases connect properly and user workflows complete end-to-end.