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/claude-code/uigit clone --depth 1 https://github.com/MadAppGang/claude-codeWrote 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/claude-code/ui)<a href="https://agentmods.dev/commands/madappgang/claude-code/ui"><img src="https://agentmods.dev/badge/commands/madappgang/claude-code/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.00014 | $0.08839 |
| Opus 5 | $0.00007 | $0.04419 |
| Sonnet 5 | $0.00003 | $0.01768 |
| Haiku 4.5 | $0.00001 | $0.00884 |
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 yesterday.
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 — 1,022 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. dev:ui uses Gemini multimodal analysis for visual review — other agents cannot do this. dev:ui-engineer applies Anti-AI design patterns that dev:developer does not have.
AGENT RULES FOR THIS COMMAND:
- Design analysis/review → dev:ui agent (subagent_type: "dev:ui")
- Implementation of design improvements → dev:ui-engineer agent (subagent_type: "dev:ui-engineer")
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 Task tool to delegate ALL design reviews to 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 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 neither GEMINI_API_KEY nor OPENROUTER_API_KEY available:
- Explain the situation clearly
- Provide setup instructions
- Offer to describe the design verbally for basic feedback
- Exit gracefully if user chooses not to configure
</graceful_degradation>
</critical_constraints>
<intent_detection> Analyze $ARGUMENTS to determine user intent.
**Note**: All trigger word matching should be case-insensitive (e.g., "IMPROVE", "Fix", "REVIEW" all work).
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.
- yesterday First seen · 1,022 lines · 14 tokens per session scan A b5dc88096a33
ui is a command published in the GitHub repository MadAppGang/claude-code (279 stars, last pushed 5mo ago), licensed MIT. It adds 14 tokens to every session and 8,839 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.