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/madappgang/magus/uigit clone --depth 1 https://github.com/MadAppGang/magusWrote 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/madappgang/magus/ui)<a href="https://agentmods.dev/commands/madappgang/magus/ui"><img src="https://agentmods.dev/badge/commands/madappgang/magus/ui.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.00017 | $0.08589 |
| Opus 5 | $0.00009 | $0.04294 |
| Sonnet 5 | $0.00003 | $0.01718 |
| Haiku 4.5 | $0.00002 | $0.00859 |
Grade A, and why
ui 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.
How it starts
The opening of the file, as written. The whole thing — 969 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<user_request> $ARGUMENTS </user_request>
<critical_override> THIS COMMAND OVERRIDES THE CLAUDE.md TASK ROUTING TABLE FOR AGENT SELECTION.
WHY: This command uses specialized visual analysis agents. designer:ui carries the usability, WCAG and design-system checklists that turn a screenshot into a severity-ranked review — other agents cannot do this. dev:frontend applies Anti-AI design patterns that dev:developer does not have.
AGENT RULES FOR THIS COMMAND:
- Design analysis/review → designer:ui agent (subagent_type: "designer:ui")
- Implementation of design improvements → dev:frontend agent (subagent_type: "dev:frontend")
Note: Implementation delegation requires the dev plugin (dev@magus). If dev plugin is not installed, provide implementation recommendations only without delegating to dev:frontend.
DO NOT use dev:developer for design implementation (lacks Anti-AI design rules and visual verification). DO NOT use dev:architect for design review (cannot perform multimodal visual analysis). DO NOT use code-analysis:detective (READ-ONLY, cannot implement design changes). </critical_override>
**You MUST:**
- Use Agent tool to delegate ALL design reviews to designer:ui agent
- Use Bash to check API keys and run Claudish
- Use Read/Glob to find design references
- Use Tasks to track workflow progress
- Use AskUserQuestion for user input gates
**You MUST NOT:**
- Write or edit ANY files directly
- Perform design reviews yourself
- Write review files yourself (delegate to designer:ui)
</orchestrator_role>
<todowrite_requirement>
You MUST use Tasks to track orchestration workflow.
Initialize Tasks AFTER Phase 0.5 (Intent Detection) determines INTENT_MODE.
**If INTENT_MODE === "REVIEW_AND_IMPLEMENT":**
1. Session Initialization
2. Intent Detection
3. Design Reference Input
4. API Configuration
5. Review Configuration
6. Execute Analysis
7. Present Results
8. Implementation Approval
9. Execute Implementation
**If INTENT_MODE === "REVIEW_ONLY":**
1. Session Initialization
2. Intent Detection
3. Design Reference Input
4. API Configuration
5. Review Configuration
6. Execute Analysis
7. Present Results
</todowrite_requirement>
<graceful_degradation>
If no image can be read and no Figma access is configured:
- Say which input was missing
- Ask for a screenshot path, or Figma MCP setup
- Exit gracefully. Do not produce a review of a screen nobody looked at.
</graceful_degradation>
</critical_constraints>
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 · 969 lines · 17 tokens per session scan A a2fe5465ae8d
ui is a command published in the GitHub repository MadAppGang/magus (9 stars, last pushed 5d ago), licensed MIT. It adds 17 tokens to every session and 8,589 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-08-31.
Other commands, from other repositories
ui-flow-review
Review menus, HUD, navigation, and player flow from a UX perspective.
template-ui
Design a Sent template-builder interface.
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.
study
Runtime entry point for extracting design DNA from a live URL, screenshot, or reference site. Part of the Discovery lifecycle phase.
4-generate
Run Stage 4 of the design system skill generation pipeline: parallel skill file generation.
audit-ux
Whole-repo adversarial UX audit of the shipped user surfaces -> docs/audits/ux-audit- .md.