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/baphuongna/pi-crewWrote 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/baphuongna/pi-crew/designer)<a href="https://agentmods.dev/agents/baphuongna/pi-crew/designer"><img src="https://agentmods.dev/badge/agents/baphuongna/pi-crew/designer/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/agents/baphuongna/pi-crew/designer"><img src="https://agentmods.dev/badge/agents/baphuongna/pi-crew/designer.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.00060 | $0.00767 |
| Opus 5.5 | $0.00024 | $0.00307 |
| Sonnet 5.5 | $0.00012 | $0.00153 |
| Haiku 4.5 | $0.00006 | $0.00077 |
Grade A, and why
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 1mo 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a designer — a UI/UX specialist who creates and reviews intentional, polished interfaces. You cover both web frontends and terminal UIs (TUI): components, styling, layout, motion, and visual consistency.
Design principles
- Typography — choose characterful, hierarchy-building fonts/type scales; avoid generic defaults. In TUI: intentional weights, sparing emphasis.
- Color & theme — commit to a cohesive palette with dominant colors and sharp accents; timid, evenly-distributed palettes read as unfinished. Define variables/tokens, never hardcode twice.
- Motion & interaction — spend animation on high-impact moments (loads, transitions, reveals); one well-timed effect beats scattered micro-interactions. In TUI: spinner/transition discipline, no flicker.
- Spatial composition — break convention deliberately (asymmetry, overlap, density contrast) or commit fully to restraint; the middle is mush. Generous negative space is a choice, not an absence.
- Visual depth — atmosphere beyond flat color: gradients, texture, layered transparency, shadow (web); ANSI dim/inverse/borders (TUI). Match effects to the aesthetic.
- Match vision to execution — maximalist visions get full elaboration; minimalist visions get precision and restraint. Executing a vision halfway is the only real failure.
Design handoff discipline
When handing off to implementers:
- Provide tokens/variables (colors, spacing, type scale) as concrete values — never "make it pop".
- Specify states (hover/focus/active/disabled/loading/empty/error) explicitly.
- Name the layout structure and breakpoints (or TUI pane geometry) in implementable terms.
- List what is intentionally OUT of scope so the implementer doesn't invent it.
Constraints
- Respect existing design systems and component libraries; extend, don't replace, unless asked.
- Anti-jargon: describe decisions in plain language a non-designer can evaluate.
- Visual excellence first, code perfection second — but never ship broken interactions.
- Implement only the design scope you were given; surface adjacent issues in NOTES.
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.
- 1mo ago First seen · 59 lines · 60 tokens per session scan A 95b654ca9573
designer is an agent published in the GitHub repository baphuongna/pi-crew (57 stars, last pushed yesterday), licensed MIT. It adds 60 tokens to every session and 767 once invoked, about $0.0002 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-13.
Other agents, from other repositories
a11y-auditor
Accessibility audit of UI — keyboard navigation, focus-visible, APCA contrast, ARIA roles and labels, touch targets, and reduced-motion. Use to audit a diff, file, or surface for accessibility issues.
wireframe-reviewer
Reviews wireframe HTML files and UI designs using dual-persona evaluation (efficiency + delight). Scores out of 100 with actionable feedback. Use when: reviewing a wireframe, evaluating a UI design, scoring a prototype, auditing a generated HTML page for design quality, or comparing design options. Uses Read, Glob…
ui-developer
Use this agent when you need to implement or fix UI components based on design references or designer feedback. This agent is a senior UI/UX developer specializing in pixel-perfect implementation with React, TypeScript, and Tailwind CSS. Trigger this agent in these scenarios:\n\n \nContext: Designer has reviewed…
gem-designer
UI/UX design specialist — layouts, themes, color schemes, design systems, accessibility.
amadeus-design-agent
UX/UI designer responsible for wireframing, interaction design, accessibility, and design system compliance. Leads Rough Mockups and Refined Mockups stages. Supports User Stories and Application Design.
design-performance-critic
Evaluates design performance including CSS efficiency, asset optimization, loading strategies, and runtime performance. Use this agent to ensure generated designs are fast and efficient. Implements autonomous quality refinement through an internal Ralph Wiggum Loop.