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.
git clone --depth 1 https://github.com/kensaurus/cursor-kenjiWrote 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/kensaurus/cursor-kenji/uiux-plan)<a href="https://agentmods.dev/commands/kensaurus/cursor-kenji/uiux-plan"><img src="https://agentmods.dev/badge/commands/kensaurus/cursor-kenji/uiux-plan.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.00018 | $0.00160 |
| Opus 5 | $0.00009 | $0.00080 |
| Sonnet 5 | $0.00004 | $0.00032 |
| Haiku 4.5 | $0.00002 | $0.00016 |
Grade A, and why
uiux-plan 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
UI/UX Unification Plan
Run the plan-uiux-unification skill: exhaustively audit UI/UX and
design-system consistency and produce a phased unification plan. Audit and
plan only — change no code until the plan is reviewed and approved.
Emit the plan ranked by severity with concrete file:line findings and a
phase-by-phase remediation checklist. After approval, execute with
enhance-web-ui, enhance-web-ux, and audit-uiux-design-system.
The full playbook lives in the plan-uiux-unification skill.
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 · 17 lines · 18 tokens per session scan A 2da0c8a3cdc0
uiux-plan is a command published in the GitHub repository kensaurus/cursor-kenji (9 stars, last pushed 9d ago), licensed MIT. It adds 18 tokens to every session and 160 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 commands, from other repositories
audit-accessibility
Audit a product against real assistive technology use, prioritised by who is blocked.
build-website
Build a small site with the simplest stack that fits, fast by default and editable afterwards.
onboarding-flow
Design an onboarding flow that gets a user to first value quickly, cutting everything that delays it.
review-accessibility
Review an interface for accessibility barriers, prioritised by who is blocked rather than by rule count.
summary
Generate a consolidated project brief from design artifacts. For the full spec package with YAML specs and validation, use /compile instead.
checklist
Generate a custom checklist for the current feature based on user requirements.