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 GalaxyRuler/Galactic-skills --skill test-uxgit clone --depth 1 https://github.com/GalaxyRuler/Galactic-skillsWrote 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/galaxyruler/galactic-skills/test-ux)<a href="https://agentmods.dev/skills/galaxyruler/galactic-skills/test-ux"><img src="https://agentmods.dev/badge/skills/galaxyruler/galactic-skills/test-ux/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/galaxyruler/galactic-skills/test-ux"><img src="https://agentmods.dev/badge/skills/galaxyruler/galactic-skills/test-ux.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.00113 | $0.00831 |
| Opus 5 | $0.00056 | $0.00415 |
| Sonnet 5 | $0.00023 | $0.00166 |
| Haiku 4.5 | $0.00011 | $0.00083 |
Grade A, and why
test-ux 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 2d 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 — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/test-ux — portable UX testing runner
Execute the UX Testing Playbook (playbook.md, same folder) against the current product and emit a findings report (and a real-user test plan). Read it first — it's the method; this is the runbook. Works for any web/app product; a project-level test-ux overrides this when present.
Scope: an argument narrows to a flow/screen (/test-ux "signup flow"). No argument = the top tasks from Phase 0.
Phase 0 — Detect & scope
- Find how to launch the app (project
README/TESTING.md, dev script inpackage.json, or ask). Identify supported locales + text direction. - Read a project
TESTING.md/docs/testing/*/ the Project appendix inplaybook.mdand prefer its goals/tasks/personas. - Define the top 3–5 tasks as user goals (not features) + a one-line success criterion each; pick ≥1 novice persona.
Runbook (see playbook.md for the why)
- Scope & journeys — goals, personas (≥1 novice), top tasks, environments (every locale + text direction, mobile + desktop).
- Heuristic evaluation — Nielsen's 10 per key screen; screenshot evidence;
heuristic# · screen · issue · severity 0–4 · fix. - Task walkthroughs — drive each task step-by-step; at each step apply the 4 learnability questions; log steps-vs-optimal, dead-ends, hesitation; verdict completed/friction/failed.
- Journey & states — empty/loading/low-data/error/first-run/returning; error recovery; trust & provenance.
- Content & i18n comprehension — plain language, no jargon, no raw technical identifiers shown to users, honest tone; per locale verify meaning parity + correct direction + no untranslated source text on the rendered page (not just resource files).
- Real-user test-plan generator — moderated + unmoderated scripts, screener, metrics sheet (task success, time, SEQ, SUS). Save alongside the report.
- Report — severity-sorted findings + top-3 blockers, top-3 quick wins, and the explicit "validate with real users" list.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago Changed 45849d9f9976
- 9d ago First seen · 36 lines · 113 tokens per session scan A 360b9e1daee6
test-ux is a skill published in the GitHub repository GalaxyRuler/Galactic-skills (5 stars, last pushed 3d ago), licensed MIT. It adds 113 tokens to every session and 831 once invoked, about $0.0006 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 skills, from other repositories
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.
design-qa
Internal prototype QA helper. Use only after a Product Design prototype, URL-to-code build, or image-to-code build has a source visual target and a rendered implementation to compare before handoff. Do not use for broad UX critique, design critique, product audits, or flow reviews; route those user-facing requests to…
health
Runs a budget-aware agent-assisted engineering health audit for instruction/config drift, hooks/MCP, verifier surfaces, and AI maintainability. Use when users ask in any language to audit Claude, Codex, Pi, agent instructions, MCP or hooks, verifier coverage, or AI-maintainability drift. Not for debugging application…
hunt
Finds root cause before applying fixes for errors, crashes, regressions, failing tests, broken behavior, and screenshot-reported defects. Use when users report in any language errors, crashes, broken behavior, regressions, failing tests, screenshot evidence, or something that used to work and now fails. Not for code…
chrome-cdp
Drive a headless Chrome over the Chrome DevTools Protocol (CDP) for browser QA — navigate, click, fill forms, read the DOM/accessibility tree, screenshot, and assert. Use whenever a task requires loading a web page and interacting with it like a user. Chrome is launched by a bash step (recipe below); this skill…
ui-craft-checks
Use this comprehensive gate for formal review, QA, launch handoff, exact-fidelity inspection, high-risk complex UI, or when the fast gate exposes a deeper craft problem. Ordinary single-screen work uses ui-design-executor and its bundled validator without loading this full matrix. Pair standalone artifacts with…