Borrowing it
Nothing to install: this file belongs to c9r-io/orchestrator. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/c9r-io/orchestrator/main/.claude/skills/uiux-test-doc-gen/SKILL.mdgit clone --depth 1 https://github.com/c9r-io/orchestratorWrote 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/c9r-io/orchestrator/uiux-test-doc-gen)<a href="https://agentmods.dev/skills/c9r-io/orchestrator/uiux-test-doc-gen"><img src="https://agentmods.dev/badge/skills/c9r-io/orchestrator/uiux-test-doc-gen/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/c9r-io/orchestrator/uiux-test-doc-gen"><img src="https://agentmods.dev/badge/skills/c9r-io/orchestrator/uiux-test-doc-gen.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.00071 | $0.01080 |
| Opus 5.5 | $0.00028 | $0.00432 |
| Sonnet 5.5 | $0.00014 | $0.00216 |
| Haiku 4.5 | $0.00007 | $0.00108 |
Grade A, and why
uiux-test-doc-gen 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 2mo 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UI/UX Test Doc Gen
Generate/complete docs/uiux/** so it evolves from a generic checklist into a set of project-aligned, reproducible, executable UI/UX test scenarios.
Source Of Truth (Mutable)
docs/design-system.md is a developer-maintained and evolving source of design language and constraints. When using this skill:
- Always use the current repo's
docs/design-system.md(do not rely on memory). - Avoid hardcoding token numeric values into test expectations. Prefer verifying "tokens/rules are used" and reference the latest values in
docs/design-system.mdonly when numeric thresholds are necessary.
Inputs
- Project design system:
docs/design-system.md - Frontend code:
gui/in this repository; discover the actual frontend root in other targets. - If available: a confirmed plan or the current diff (new routes, forms, components)
Outputs
- Update/add
docs/uiux/**docs (only what applies to the current project) - Generate/update
docs/uiux/_surface/(inputs like UI routes) - Update
docs/uiux/README.mdindex (keep it lightweight; do not hardcode totals)
Workflow
-
Define scope
feature-only: align only UI/UX constraints related to the current feature (default)system-baseline: baseline regression across the whole UI (pre-release)
-
Discover UI surface (from code/config)
- Prefer running the UI route extraction script:
.claude/skills/uiux-test-doc-gen/scripts/extract_surface.sh- Output defaults to
docs/uiux/_surface/ - Optional override:
PORTAL_DIRS=portal,frontend,web(comma-separated)
- If output is empty: the project likely has no frontend directory yet. Maintain only generic docs and constraint notes, and clearly state "no UI integrated" in doc headers.
- Prefer running the UI route extraction script:
-
Update scenarios against the design system
- Any expectation involving visuals/interactions must align with
docs/design-system.md:- tokens (light/dark)
- glass/fallback behavior
- spacing/radius
- focus ring/a11y
- animation duration and reduced motion
- Any expectation involving visuals/interactions must align with
What ships with it
2 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.
- 2mo ago First seen · 92 lines · 71 tokens per session scan A c837f627b987
uiux-test-doc-gen is a skill published in the GitHub repository c9r-io/orchestrator (21 stars, last pushed 1mo ago), licensed MIT. It adds 71 tokens to every session and 1,080 once invoked, about $0.0003 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-30.
Other skills, from other repositories
site-preship-review
Use before publishing or relaunching any website — six parallel single-dimension reviewers (design, mobile, states, user flows, launch prep, security & infra) that render and look at every page, then one or two fix passes. Includes launch-readiness and rendered-page checks.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
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…
cw-dogfood
Use when a Codewhale change needs proving in the real product, or when asked to build/install/dogfood the local binaries: stamped release build, atomic install, fresh-shell verification, and the manual QA that gates cannot cover.
cw-gates
Use before claiming any Codewhale change is done, green, or ready to land: the focused-to-broad verification ladder, the budget checks CI enforces, and the rules for what counts as a passing test.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code.