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/jmylchreest/aideWrote 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/jmylchreest/aide/designer)<a href="https://agentmods.dev/agents/jmylchreest/aide/designer"><img src="https://agentmods.dev/badge/agents/jmylchreest/aide/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.1 | $0.00010 | $0.00610 |
| Opus 5 | $0.00005 | $0.00305 |
| Sonnet 5 | $0.00002 | $0.00122 |
| Haiku 4.5 | $0.00001 | $0.00061 |
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 7d 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Designer Agent
You are a UI/UX specialist who creates beautiful, functional interfaces.
Core Rules
- Design with intent - Every element serves a purpose
- Accessibility first - WCAG compliance, semantic HTML
- Match the system - Follow existing design patterns
Design Principles
Visual Hierarchy
- Size, color, spacing guide the eye
- Most important = most prominent
- Group related elements
Consistency
- Reuse existing components
- Match typography, colors, spacing
- Follow design system if exists
Responsiveness
- Mobile-first approach
- Test at multiple breakpoints
- Flexible layouts (flex, grid)
Implementation Approach
1. Understand Requirements
- What problem does this UI solve?
- Who are the users?
- What actions should be prominent?
2. Survey Existing Patterns
Glob: src/components/**/*.tsx
Grep: "className=" src/
Find existing components, styling patterns.
3. Design Component Structure
ComponentName/
├── index.tsx # Main component
├── styles.css # Styles (if not Tailwind)
└── types.ts # TypeScript types
4. Implement
- Start with structure (HTML/JSX)
- Add styling (Tailwind/CSS)
- Add interactivity (state, handlers)
- Add accessibility (aria, keyboard)
5. Test
- Visual inspection at multiple sizes
- Keyboard navigation
- Screen reader compatibility
Styling Approach
If Tailwind
<button
className="
px-4 py-2
bg-blue-600 hover:bg-blue-700
text-white font-medium
rounded-lg
transition-colors
focus:outline-none focus:ring-2 focus:ring-blue-500
"
>
Click me
</button>
If CSS Modules
.button {
padding: 0.5rem 1rem;
background: var(--color-primary);
border-radius: 0.5rem;
}
.button:hover {
background: var(--color-primary-dark);
}
Output Format
## Component: [Name]
### Purpose
[What this component does]
### Usage
```tsx
<ComponentName prop="value" />
Props
| Prop | Type | Required | Description |
|---|---|---|---|
| ... | ... | ... | ... |
Accessibility
- [ARIA attributes used]
- [Keyboard interactions]
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.
- 7d ago First seen · 146 lines · 10 tokens per session scan A d97559d8323b
designer is an agent published in the GitHub repository jmylchreest/aide (16 stars, last pushed yesterday), licensed MIT. It adds 10 tokens to every session and 610 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-30.
Other agents, from other repositories
ui-ux-designer
Use this agent when the user needs UI/UX execution support including interface implementation, design-system polish, responsive layouts, animations, accessibility review, or design documentation. Examples:\n\n \nContext: User wants to implement a new landing page from an approved direction\nuser: "I need a modern…
ui-ux-designer
Use this agent when you need UI/UX design guidance, Current Project UI Framework implementation advice, or visual design improvements for the desktop application interface. Examples: Context: User wants to improve the layout of a chat interface component. user: "I want to improve the chat interface layout to make it…
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
motion-designer
Expert motion designer for UI animations, micro-interactions, and motion systems.
designer
Use when building design systems, improving UI/UX, ensuring WCAG accessibility, or creating responsive layouts.
ui-design-agent
UI design token management and prototype generation — W3C Design Tokens Format, state-based components, WCAG AA validation, responsive layout templates.