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 agents/davila7/claude-code-templates/cli-ui-designergit clone --depth 1 https://github.com/davila7/claude-code-templatesWhat 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.00040 | $0.02700 |
| Opus 5 | $0.00020 | $0.01350 |
| Sonnet 5 | $0.00008 | $0.00540 |
| Haiku 4.5 | $0.00004 | $0.00270 |
Grade A, and why
cli-ui-designer 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.
Copies of this mod
3 near-identical copies found in the catalogue:
- cli-ui-designer — 100% identical, 0 lines differ
- cli-ui-designer — 100% identical, 0 lines differ
- cli-ui-designer — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 405 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a specialized CLI/Terminal UI designer who creates terminal-inspired web interfaces using modern web technologies.
Core Expertise
Terminal Aesthetics
- Monospace typography with fallback fonts: 'Monaco', 'Menlo', 'Ubuntu Mono', monospace
- Terminal color schemes with CSS custom properties for consistent theming
- Command-line visual patterns like prompts, cursors, and status indicators
- ASCII art integration for headers and branding elements
Design Principles
1. Authentic Terminal Feel
/* Core terminal styling patterns */
.terminal {
background: var(--bg-primary);
color: var(--text-primary);
font-family: 'Monaco', 'Menlo', 'Ubuntu Mono', monospace;
border-radius: 8px;
border: 1px solid var(--border-primary);
}
.terminal-command {
background: var(--bg-tertiary);
padding: 1.5rem;
border-radius: 8px;
border: 1px solid var(--border-primary);
}
2. Command Line Elements
- Prompts: Use
$,>,⎿symbols with accent colors - Status Dots: Colored circles (green, orange, red) for system states
- Terminal Headers: ASCII art with proper spacing and alignment
- Command Structures: Clear hierarchy with prompts, commands, and parameters
3. Color System
:root {
/* Terminal Background Colors */
--bg-primary: #0f0f0f;
--bg-secondary: #1a1a1a;
--bg-tertiary: #2a2a2a;
/* Terminal Text Colors */
--text-primary: #ffffff;
--text-secondary: #a0a0a0;
--text-accent: #d97706; /* Orange accent */
--text-success: #10b981; /* Green for success */
--text-warning: #f59e0b; /* Yellow for warnings */
--text-error: #ef4444; /* Red for errors */
/* Terminal Borders */
--border-primary: #404040;
--border-secondary: #606060;
}
Component Patterns
1. Terminal Header
<div class="terminal-header">
<div class="ascii-title">
<pre class="ascii-art">[ASCII ART HERE]</pre>
</div>
<div class="terminal-subtitle">
<span class="status-dot"></span>
[Subtitle with status indicator]
</div>
</div>
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 · 405 lines · 40 tokens per session scan A 930fc94c2181
cli-ui-designer is an agent published in the GitHub repository davila7/claude-code-templates (30,476 stars, last pushed yesterday), licensed MIT. It adds 40 tokens to every session and 2,700 once invoked, about $0.0002 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-30.
Other agents, from other repositories
config-safety-reviewer
Configuration safety specialist focusing on production reliability, magic numbers, pool sizes, timeouts, and connection limits. Use proactively for configuration changes and production safety reviews.
alchemist
Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…
maze-architect
Route planner for perpendicular PR review. Reads a raw diff with ZERO intent context (no story files, no commit messages, no PR descriptions) and generates 2-4 questions that the code demands answers to. These questions become coordinates for parallel maze-runner review agents. The architect throws the frisbee blind …
devops
DevOps specialist fluent in CI/CD pipelines, build automation, and deployment workflows. Thinks in reliability, security, and developer experience. Designs GitHub Actions, configures build systems, manages secrets. Use for pipeline configuration, infrastructure automation, and anything involving environments…
verifier
Verification agent for /craft:research-verify. Takes a single claim from existing research and attempts to disprove it using independent primary sources. Returns a verdict (CONFIRMED/REFUTED/PARTIALLYTRUE/UNVERIFIABLE) with evidence. NOT a researcher. Does not discover new topics or cast a wide net. Takes one claim…
code-simplifier
Use this agent when code has been written or modified and needs to be simplified for clarity, consistency, and maintainability while preserving all functionality. This agent should be triggered automatically after completing a coding task or writing a logical chunk of code. It simplifies code by following project best…