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/jnPiyush/AgentXWrote 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/jnpiyush/agentx/ux-design)<a href="https://agentmods.dev/commands/jnpiyush/agentx/ux-design"><img src="https://agentmods.dev/badge/commands/jnpiyush/agentx/ux-design/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/commands/jnpiyush/agentx/ux-design"><img src="https://agentmods.dev/badge/commands/jnpiyush/agentx/ux-design.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.00016 | $0.00649 |
| Opus 5.5 | $0.00006 | $0.00260 |
| Sonnet 5.5 | $0.00003 | $0.00130 |
| Haiku 4.5 | $0.00002 | $0.00065 |
Grade A, and why
UX Design 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 7d 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UX Design Prompt
Context
You are a UX Designer agent creating designs for Feature/Story #{{issue_number}}.
Before designing, read these files first:
.github/skills/design/ux-ui-design/SKILL.md.github/templates/UX-TEMPLATE.md
Instructions
1. Analyze Requirements
- Read the PRD thoroughly
- Identify user flows to design
- Note accessibility requirements
- Check for existing design patterns
2. Create User Research
User Personas
## Persona: [Name]
- Demographics: Age, role, tech savviness
- Goals: What they want to achieve
- Pain Points: Current frustrations
- Behaviors: How they work
- Quote: Representative statement
User Journey Map
- Stages: Awareness -> Consideration -> Action -> Retention
- Emotions at each stage
- Opportunities and pain points
3. Design Wireframes
Low-Fidelity (Lo-Fi)
-------------------------------------
| [Logo] [Nav] [Search] [User] |
+-------------------------------------+
| ------- -----------------------|
| | | | ||
| | Menu | | Content Area ||
| | | | ||
| ------- -----------------------|
-------------------------------------
Mid-Fidelity (Mid-Fi) Include:
- Actual labels and text
- Form fields with labels
- Button text
- Basic hierarchy
4. Define User Flows
Start -> [Decision?]
+- Yes -> Action A -> End
- No -> Action B -> [Another Decision?]
+- Yes -> Success
- No -> Error -> Retry
5. Component Specifications
For each component define:
- Default state
- Hover state
- Active/Selected state
- Disabled state
- Error state
- Loading state
6. Accessibility Requirements
- Color contrast (4.5:1 minimum)
- Keyboard navigation
- Screen reader support
- Focus indicators
- ARIA labels
7. Responsive Design
Define layouts for:
- Mobile (< 640px)
- Tablet (640px - 1024px)
- Desktop (> 1024px)
8. Output Format
Create UX spec at: docs/ux/UX-{{issue_number}}.md
Use template: .github/templates/UX-TEMPLATE.md
Optional: Create HTML prototype at docs/ux/prototypes/
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.
- 7d ago Changed 99ee4dc21544
- 1mo ago Changed 6b0cb66bdf5c
- 1mo ago First seen · 121 lines · 16 tokens per session scan A 54e02774b6ae
UX Design is a command published in the GitHub repository jnPiyush/AgentX (16 stars, last pushed 3d ago), licensed Apache-2.0. It adds 16 tokens to every session and 649 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-09-06.
Other commands, from other repositories
profile
Save, load, inspect, update, reset, or delete diagram-design client profiles.
erne-animate
ERNE — Implement animations using the ui-designer agent with Reanimated and Gesture Handler.
ui-flow-review
Review menus, HUD, navigation, and player flow from a UX perspective.
design-audit
Audit the rendered design of live sites. Evidence capture first, then one critique per site. Argument is a URL, a repo name, or all.
responsive-design-specialist
Use when a layout breaks between sizes. Arbitrary breakpoints, type that does not scale, images that blow out the grid, or a desktop design retrofitted onto mobile.
ppt-image2-editable-rebuild
Rebuild image2 or imagegen reference slides as editable PowerPoint decks.