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 agentmods add commands/f0d010c/stark/stark-usabilitygit clone --depth 1 https://github.com/f0d010c/starkWrote 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/f0d010c/stark/stark-usability)<a href="https://agentmods.dev/commands/f0d010c/stark/stark-usability"><img src="https://agentmods.dev/badge/commands/f0d010c/stark/stark-usability.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 | $0.00000 | $0.00182 |
| Opus 5 | $0.00000 | $0.00091 |
| Sonnet 5 | $0.00000 | $0.00036 |
| Haiku 4.5 | $0.00000 | $0.00018 |
Grade A, and why
stark-usability 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 3d 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
/stark-usability
Use this command when a generated UI looks attractive but might fail real use.
Inputs
- Product/screen:
- User mode:
- Core task:
- Frequency:
- Risk:
- Existing UI or plan:
Output
Task ergonomics contract
- Core task:
- User mode:
- Frequency:
- Risk:
- Success metric:
- Cognitive load:
- Control model:
- Speed path:
- Error prevention:
- Recovery:
- State matrix:
- Evidence plan:
Usability findings
- Hard fails:
- Highest-impact repair:
- What visual design must preserve:
Use references/ux-patterns/task-ergonomics.md first, then references/ui-patterns/interaction-state-matrix.md for concrete state behavior. If a contextual pattern applies, also use the matching brief in references/ux-patterns/.
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.
- 3d ago First seen · 38 lines · 0 tokens per session scan A 9292cd685160
stark-usability is a command published in the GitHub repository f0d010c/stark (25 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 182 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-30.
Other commands, from other repositories
OPSX: Apply
Implement tasks from an OpenSpec change (Experimental).
/opsx-apply
Implement tasks from an OpenSpec change (Experimental).
anti-slop-designer
Use when a UI looks machine-made rather than decided. Violet gradients, glassmorphism everywhere, identical cards in a grid, untouched shadcn or Material defaults, emoji bullets, or copy stuffed with seamless and unlock.
database-setup
Use when a project needs to store data and has no database yet. Setting up Supabase, creating tables, writing queries, and connecting them to the frontend. Written for designers.
design-brief
Use when a design request is broad or unclear and you do not know which specialist it needs. Reads the brief, routes it to the right expertise, and returns structured guidance.
design-critic
Use when you want an honest read on a design instead of encouragement. What is wrong, ranked by severity, with the reason attached. Works on a screenshot, a mockup, or a described screen.