Borrowing it
Nothing to install: this file belongs to alwkala/tidyfactor-design. 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/alwkala/tidyfactor-design/main/.agents/skills/tidyfactor-design/references/commands/states.mdgit clone --depth 1 https://github.com/alwkala/tidyfactor-designWrote 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/commands/alwkala/tidyfactor-design/states)<a href="https://agentmods.dev/commands/alwkala/tidyfactor-design/states"><img src="https://agentmods.dev/badge/commands/alwkala/tidyfactor-design/states.svg" alt="Measured on agentmods" 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.00000 | $0.00497 |
| Opus 5 | $0.00000 | $0.00249 |
| Sonnet 5 | $0.00000 | $0.00099 |
| Haiku 4.5 | $0.00000 | $0.00050 |
Grade A, and why
states 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 6d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command: states — Interactive States, Not a Static Mockup
Purpose
This is what separates an "interactive prototype" from a picture of a website — the difference the whole positioning of this skill depends on. Kept as its own command because states are easy to skip under time pressure and easy to audit for once isolated.
When to run it
- After a component/page/screen has its default look — always follow with a states pass before calling it done.
- User phrasing: "add hover states", "what does this look like empty/
loading",
states.
What it does
- For every interactive component in scope, confirm the full matrix applies where relevant: default, hover, focus-visible, active/pressed, disabled, loading, empty, error, success.
- Implement via
interactions.js(shared) for stateful JS behavior (dropdown open/close, tab switching, modal show/hide, toast dismiss) and CSS pseudo-classes for the rest — never a per-page<script>for one page's interactive widget. - Empty states are a design decision, not a placeholder: what caused
it, what the user should do next — same principle as
frontend-design's "an empty screen is an invitation to act", applied consistently across the whole prototype rather than per page. - Loading states: skeleton shapes matching the eventual content's layout, not a generic spinner-only blank — this is what makes a dashboard prototype credible.
- Keyboard/focus-visible states are not optional — every interactive element needs a visible focus ring using a token color, not the browser default.
Output convention
design-system/
components.css ← :hover, :focus-visible, [disabled], .is-loading, .is-empty, .is-error
interactions.js ← shared stateful behavior (toggle/modal/dropdown/tab)
Checklist
- Hover, focus-visible, active, and disabled states present on every interactive component
- Empty and loading states designed deliberately, not left as placeholders
- Stateful behavior lives in shared
interactions.js, never a per-page script - Focus ring visible and token-colored on every focusable element
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.
- 6d ago First seen · 49 lines · 0 tokens per session scan A 53fe715c1177
states is a command published in the GitHub repository alwkala/tidyfactor-design (5 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 497 tokens. 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 commands, from other repositories
critique-screen
Run all seven visual critiques on a screen and output a prioritised fix list.
critique-ux
Run a focused UX critique on a screen — affordances, information density, and hierarchy — and output a prioritised fix list.
design-onboarding
Design a first-run experience end to end — activation path, progressive disclosure, and time to first value.
frame-problem
Structure an ambiguous design challenge into a clear problem definition with constraints and criteria.
pull-repos
Pull all repos (parent + marketplace clones + configured project repos).
update-counts
Update all hardcoded counts (skills, agents, marketplace repos/skills) across documentation from filesystem.