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 rainmanjam/poka-yoke --skill uxgit clone --depth 1 https://github.com/rainmanjam/poka-yokeWrote 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/rainmanjam/poka-yoke/ux)<a href="https://agentmods.dev/skills/rainmanjam/poka-yoke/ux"><img src="https://agentmods.dev/badge/skills/rainmanjam/poka-yoke/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/rainmanjam/poka-yoke/ux"><img src="https://agentmods.dev/badge/skills/rainmanjam/poka-yoke/ux.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00915 |
| Opus 5.5 | $0.00014 | $0.00366 |
| Sonnet 5.5 | $0.00007 | $0.00183 |
| Haiku 4.5 | $0.00004 | $0.00092 |
Grade A, and why
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 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UX: Structuring Interaction Code
Interface code accumulates faster than any other kind, because every requirement arrives as "and also, when the user does X". Without structure a screen becomes one component holding fetching, validation, formatting, submission and error display, and every change risks all of them.
The discipline is ordinary: single responsibility, explicit state ownership, and names that survive being read alone. What is different is that the pressure to skip it is higher, because interface code is visible and the deadline is usually visual.
Decide where state lives, once
Most interface bugs are state-ownership bugs wearing other clothes.
One owner per piece of state. If two components can both change a value, they will disagree, and the disagreement will be intermittent. Lift the state to the nearest common parent and pass it down, or move it out of the tree entirely.
Derive rather than duplicate. A total stored alongside the items it sums is two facts
that must agree. Compute it. If computing it is expensive, memoise the computation rather than
storing a second copy.
Keep server state and form state distinct. What the server last said and what the user has typed are different things with different lifetimes. Conflating them is why "the form reset itself" bugs are so hard to reproduce.
Name state for what it is, not what it shows. isSubmitting is a fact. showSpinner is a
consequence, and it will eventually need to be true for a second reason.
Split components along seams that will move
By responsibility, not by size. A 400-line component that renders one coherent thing is easier to work with than four components passing state between them.
Separate what fetches from what displays. A component that both loads and renders cannot be previewed, tested, or reused with different data. Take data as props; let a parent decide where it came from.
Keep the rules out of the markup. Whether a discount applies is a business question with a right answer that does not depend on React. It should be a function you can test without rendering.
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 · 90 lines · 36 tokens per session scan A ec49226228dd
ux is a skill published in the GitHub repository rainmanjam/poka-yoke (24 stars, last pushed 3d ago), licensed MIT. It adds 36 tokens to every session and 915 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-30.
Other skills, from other repositories
review-all
Multi-agent code review for diffs (project-agnostic). Covers standards, bugs, security, DRY, smells, perf, tests, API contracts, a11y/i18n. Verifies each finding to eliminate false positives. Use for /review-all, pre-PR/pre-commit review, or auditing uncommitted/staged changes.
aesthetic-instrument
A committed aesthetic in the sense of skills/committed-aesthetic/SKILL.md: every rule below is checkable, and every value was read out of the source — packages/board/public/index.html and greatcto-site/styles.css — rather than chosen to write this document.
committed-aesthetic
How to write — and how to use — a skill that IS one aesthetic rather than a catalogue of them. A catalogue lets an agent pick, and it picks the modal option; a committed aesthetic makes it execute one thing precisely, against rules you can check. Use when a design keeps coming out competent and forgettable, when…
design-reviewer
Use after AC and before RED for any wave that ships UI or changes existing behaviour. Audits component APIs against installed dist files, writes a per-route mockup and visual ACs to .wave/dr.md.
a11y-audit
Dedicated WCAG 2.2 AA/AAA accessibility audit across 10 dimensions (A1-A10) covering semantic HTML, keyboard navigation, ARIA patterns, color contrast, forms, images/media, responsive/zoom, motion/animation, reading/content, and legal compliance. Goes far beyond surface-level design-review checks with deep…
design-review
UI/UX design consistency audit. Code-based DX1-DX20 checklist covering states, consistency, accessibility, responsive behavior, and interaction patterns. Optional visual audit via chrome-devtools screenshots and automated WCAG accessibility via axe-core. DAP1-DAP12 anti-pattern detection. Modes: [path], visual…