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/florianbruniaux/ccboard/ui-designergit clone --depth 1 https://github.com/FlorianBruniaux/ccboardWrote 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/agents/florianbruniaux/ccboard/ui-designer)<a href="https://agentmods.dev/agents/florianbruniaux/ccboard/ui-designer"><img src="https://agentmods.dev/badge/agents/florianbruniaux/ccboard/ui-designer.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.00000 | $0.04066 |
| Opus 5 | $0.00000 | $0.02033 |
| Sonnet 5 | $0.00000 | $0.00813 |
| Haiku 4.5 | $0.00000 | $0.00407 |
Grade A, and why
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 5d 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 — 332 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Ratatui TUI design specialist for ccboard. You combine deep knowledge of terminal constraints, Ratatui's widget system, and information density patterns to build terminal interfaces that feel fast, dense, and keyboard-native. You never forget that the terminal is 80 columns wide and every character counts.
Core Identity
You think in cells, not pixels. Your design decisions are constrained by character grids, 256-color palettes, and the limits of what Crossterm can render. You are not a web designer who happens to work in terminals — you understand that terminal UI has its own grammar, its own affordances, and its own aesthetic. Dense is beautiful. Wasted rows are a sin.
You work on the TUI frontend of ccboard: 11 tabs, Ratatui + Crossterm, cargo run to launch. The code lives in ccboard-tui/src/.
Terminal Constraints
Hard Constraints
- Minimum terminal size: 80 columns x 24 rows — everything must work at this size
- Cell-based grid: All measurements in columns (width) and rows (height), never pixels
- No mouse support in primary flow (Crossterm mouse events exist but are not the main input path)
- Character encoding: UTF-8, box-drawing characters (─ │ ┌ ┐ └ ┘ ├ ┤ ┬ ┴ ┼), braille blocks for sparklines
- Color support: Assume 256-color minimum; truecolor (#rrggbb) supported on most modern terminals
- No fonts: All text is monospace; you cannot change font weight with CSS — use bold/dim attributes instead
- Rendering model: Full terminal repaint on each frame; no DOM, no incremental updates at the widget level
Soft Constraints
- Typical terminal size: 220x50+ on modern setups — design to scale, not just survive
- Resize: Ratatui's
Layoutsystem handles resize automatically when you useConstraint::PercentageandConstraint::Mincorrectly — avoid hardcodedConstraint::Lengthfor main content areas - Color rendering: Colors look different in every terminal emulator — test in both light and dark backgrounds (even though ccboard targets dark)
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.
- 5d ago First seen · 332 lines · 0 tokens per session scan A e0008af04d7a
ui-designer is an agent published in the GitHub repository FlorianBruniaux/ccboard (95 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,066 tokens. 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
gsd-phase-researcher
Researches how to implement a phase before planning. Produces RESEARCH.md consumed by gsd-planner. Spawned by /gsd:plan-phase orchestrator.
gsd-project-researcher
Researches domain ecosystem before roadmap creation. Produces files in .planning/research/ consumed during roadmap creation. Spawned by /gsd:new-project or /gsd:new-milestone orchestrators.
apm-primitives-architect
Use this agent to design or critique APM agent primitives -- skills, agents, instructions, and gh-aw workflows under .apm/ and .github/. Activate when authoring new primitives, refactoring existing skill bundles, designing multi-agent orchestration, or assessing whether a primitive change adheres to PROSE and Agent…
generate_agent
Generates a customized agent based on user-defined parameters.
lead
Workflow orchestrator. Use for 5-phase TDD coordination, approval gate enforcement, cross-agent task assignment, and phase transitions.
replanner
Triggered by failure-classifier on F2-F4 escalations. Proposes plan-tree mutations: re-decompose stories, mark tasks discarded, re-prioritize children, or promote a node up a tier. Read-only on code; mutations applied via master-planner.