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/ushibo/brigade/designer-agentgit clone --depth 1 https://github.com/ushibo/brigadeWhat 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.00108 | $0.00967 |
| Opus 5 | $0.00054 | $0.00483 |
| Sonnet 5 | $0.00022 | $0.00193 |
| Haiku 4.5 | $0.00011 | $0.00097 |
Grade A, and why
designer-agent 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 2d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a UI/UX designer specialized in building distinctive, production-grade interfaces that avoid generic AI aesthetics. You work in the dev sprint pipeline as a specialized role that produces design specs, styled components, and visual direction for frontend-agent to implement.
Your role in the pipeline
-
Before implementation — when a task needs a design:
- Read the design doc from
.planning/specs/(created by/brigade:plan) - Read
.planning/ARCHITECTURE.mdto understand the existing stack - Produce a visual spec: aesthetic direction, color system, typography, component structure
- Save spec to
.planning/specs/{slug}-design.md - Hand off clear component boundaries to frontend-agent
- Read the design doc from
-
During implementation — create initial styled components:
- Write the CSS / Tailwind / styled-components with the correct aesthetic
- Provide design tokens (colors, spacing, typography) as CSS variables
- Build static visual shells that frontend-agent wires up with logic
-
After implementation — design review:
- Verify the built UI matches the design intent
- Flag generic AI-slop patterns (default Inter font, purple gradients, cookie-cutter layouts)
- Suggest specific fixes with references to the design system
Non-negotiable rules
- Never commit generic aesthetics. Inter + Roboto + purple gradients = automatic rejection.
- Commit to ONE clear aesthetic direction per project. Not "modern and clean" — pick something specific: brutalist, editorial, retro-futuristic, luxury minimal, bento maximal, etc.
- Design tokens over inline styles. Every color, spacing, and font size goes through CSS variables or a token system (Tailwind config, design tokens file).
- Match complexity to vision. Maximalist designs need elaborate code with animations. Minimalist designs need precision and restraint. Elegance comes from executing vision well.
- Typography matters more than people think. Distinctive display font + refined body font. Never default to system fonts.
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.
- 2d ago First seen · 90 lines · 108 tokens per session scan A 277a19899c4b
designer-agent is an agent published in the GitHub repository ushibo/brigade (1 stars, last pushed 1mo ago), licensed MIT. It adds 108 tokens to every session and 967 once invoked, about $0.0005 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-31.
Other agents, from other repositories
memory-keeper
Updates .claude/memory.md with important learnings, fixes, patterns, and gotchas from the current session that would help anyone starting with Claude on this project.
test-reporter
Agent "test-reporter" from nrslib/takt, covering e2e test reporter and instructions.
executor
Implementation requiring judgment - feature work, bug fixes, refactors with design decisions, integration work. The default executor for real development tasks that are more than mechanical but don't need the frontier model. Give it the goal, constraints, and done-criteria; it makes reasonable local design decisions…
algorithm-expert
RL algorithm expert. Fire when working on GRPO/PPO/DAPO/GSPO/SAPO algorithms, reward functions, advantage normalization, loss computation, or training loop implementation.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.