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 Eliyce/paqad-ai --skill ux-state-machinegit clone --depth 1 https://github.com/Eliyce/paqad-aiWrote 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/eliyce/paqad-ai/ux-state-machine)<a href="https://agentmods.dev/skills/eliyce/paqad-ai/ux-state-machine"><img src="https://agentmods.dev/badge/skills/eliyce/paqad-ai/ux-state-machine/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/eliyce/paqad-ai/ux-state-machine"><img src="https://agentmods.dev/badge/skills/eliyce/paqad-ai/ux-state-machine.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.00014 | $0.00541 |
| Opus 5 | $0.00007 | $0.00270 |
| Sonnet 5 | $0.00003 | $0.00108 |
| Haiku 4.5 | $0.00001 | $0.00054 |
Grade A, and why
ux-state-machine 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 8d 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
What It Does
Defines the user-visible states, transitions, and triggers for a changed interface so design, implementation, and documentation all operate from the same state model.
Use This When
Use this when a UI change introduces new async behavior, branching flows, or recovery paths that are hard to reason about from the happy path alone.
Inputs
- Read the affected screen or component docs and any existing state inventory first.
- Read
references/state-inventory-template.mdbefore enumerating states. - Read
runtime/capabilities/coding/checklists/edge-cases-coding.mdto avoid missing loading, stale, and error paths.
Procedure
- Walk
assets/canonical-states.txt(idle, loading, success, empty, error, disabled, stale, permission, retry); include every state the UI actually exposes. - For each transition, name the trigger explicitly (user event, async resolve, timeout, permission denied) — never imply it.
- Build the table per
assets/output.template.md(From / Trigger / To / Notes). - Surface any contradictory or undocumented state under
## Gaps. - Validate with
scripts/lint-output.sh.
Output Contract
- Return sections named
State Inventory,Transitions, andGaps. - Each state entry must name the visible UI condition and the user or system trigger.
- If no gaps remain, write
Gaps: none.
Escalate / Stop Conditions
- Ask when the request does not define the source of async updates, permissions, or recovery behavior.
- Warn when two states imply conflicting outcomes for the same trigger.
- Do not collapse materially different visible states into one generic label.
Resources
references/state-inventory-template.mdscripts/lint-output.shassets/output.template.mdassets/canonical-states.txtruntime/capabilities/coding/checklists/edge-cases-coding.mdagents/openai.yaml
What ships with it
5 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.
- 8d ago First seen · 68 lines · 14 tokens per session scan A e119cadee621
ux-state-machine is a skill published in the GitHub repository Eliyce/paqad-ai (8 stars, last pushed today), licensed MIT. It adds 14 tokens to every session and 541 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
make-interfaces-feel-better
Use when building or reviewing UI polish: typography, hit areas, nested radius, optical alignment, shadows, media outlines, micro-interactions, and animation performance.
frontend-skill
Use when the task asks for a visually strong landing page, website, app, prototype, demo, or game UI. This skill enforces restrained composition, image-led hierarchy, cohesive content structure, and tasteful motion while avoiding generic cards, weak branding, and UI clutter.
frontend-skill
Use when the task asks for a visually strong landing page, website, app, prototype, demo, or game UI. This skill enforces restrained composition, image-led hierarchy, cohesive content structure, and tasteful motion while avoiding generic cards, weak branding, and UI clutter.
frontend-design
Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Use whenever the task produces or modifies anything a user will see rendered — websites, landing pages, web apps, dashboards, React/HTML/Vue components, artifacts with visual output, style overhauls, or "make this…
frontend-design
Produce intentional, responsive, accessible UI work and perform visual QA instead of generic component assembly.
image-to-code
Implement a selected image, screenshot, mockup, generated concept, or design frame as a faithful, responsive, interactive frontend in the target codebase.