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 skills add stunt-double/stuntdouble-mcp --skill run-ux-validationgit clone --depth 1 https://github.com/stunt-double/stuntdouble-mcpWrote 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/skills/stunt-double/stuntdouble-mcp/run-ux-validation)<a href="https://agentmods.dev/skills/stunt-double/stuntdouble-mcp/run-ux-validation"><img src="https://agentmods.dev/badge/skills/stunt-double/stuntdouble-mcp/run-ux-validation/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/skills/stunt-double/stuntdouble-mcp/run-ux-validation"><img src="https://agentmods.dev/badge/skills/stunt-double/stuntdouble-mcp/run-ux-validation.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.00031 | $0.00224 |
| Opus 5.5 | $0.00012 | $0.00090 |
| Sonnet 5.5 | $0.00006 | $0.00045 |
| Haiku 4.5 | $0.00003 | $0.00022 |
Grade A, and why
run-ux-validation 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 11d 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.
What it actually says
Run UX validation
- Find validations:
list_workspaces(),list_workflows(workspace_id)(end-to-end journeys),list_checklists(workspace_id)(quality gates). Run both for a full pre-release pass. - Trigger in parallel:
run_workflow(workflow_id),run_checklist(checklist_id); both are async. - Poll:
get_workflow_run(run_id),get_checklist_run(run_id)until terminal. - Report: pass or fail for each; for failures the failing step or check, what happened, and which actor hit it.
- Follow up:
list_feedback(project_id)andget_feedback(feedback_id)for related issues,update_feedback_status(feedback_id, status: "reviewed")for triaged items, then suggest fixes or flag for the team.
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.
- 11d ago Changed · -52 lines · +8 tokens per session e234b39ba5d7
- 1mo ago First seen · 65 lines · 23 tokens per session scan A 3382b1de25b0
run-ux-validation is a skill published in the GitHub repository stunt-double/stuntdouble-mcp (1 stars, last pushed 2d ago), licensed MIT. It adds 31 tokens to every session and 224 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 skills, from other repositories
visual-testing
Visual testing, UI verification, and design comparison using screenshots and Figma integration. Use when the user wants to verify UI appearance, compare with Figma designs, test responsive layouts, check for visual regressions, or validate design implementation.
screen-reader-testing
Test web applications with screen readers including VoiceOver, NVDA, and JAWS. Use when validating screen reader compatibility, debugging accessibility issues, or ensuring assistive technology support.
qa-test-planner
Generate comprehensive test plans, manual test cases, regression test suites, and bug reports for QA engineers. Includes Figma MCP integration for design validation.
e2e-testing-patterns
Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.
critique
Adversarial design critique of the current work. Render it, look at it, and argue for rejection. Run after the gates are green, never instead of them.
test-runner
For a code change, pick the right test tier by change surface, run apc test with baseline diff, and report only NEW reds vs baseline back to the task's acceptance criterion. Separates envblocked from SUT red so a broken machine never fails the code.