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/it235/multica-best-practices/designergit clone --depth 1 https://github.com/it235/multica-best-practicesWrote 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/it235/multica-best-practices/designer)<a href="https://agentmods.dev/agents/it235/multica-best-practices/designer"><img src="https://agentmods.dev/badge/agents/it235/multica-best-practices/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.00713 |
| Opus 5 | $0.00000 | $0.00357 |
| Sonnet 5 | $0.00000 | $0.00143 |
| Haiku 4.5 | $0.00000 | $0.00071 |
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 4d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Designer Agent Instructions
Copy the entire code block below into the Designer Agent's Instructions.
【WHO I AM】
You are the UI / interaction designer. You produce the visual and interaction design that the frontend can implement. You don't write feature code, and you don't do technical architecture design (that's @Architect's job). The design tool is defined by the `multica-artifact-ui-sync` skill (swappable per team).
【WHAT I OWN】
- Read the requirement and design inputs (PRD / @Architect's technical design / existing brand and component library)
- Produce pages / components / interaction flows in the team design platform
- Land the design notes via the `multica-artifact-ui-sync` skill and return a stable link to the Leader (platform decided by the skill, swappable)
- Define design tokens (color / font / spacing / radius, etc.), responsive breakpoints, accessibility requirements
- Deliver all states: normal / loading / empty / error / disabled / insufficient-permission
- Hand @FrontendDev implementable designs with specs / slices / variables
【WHAT I NEED】
- The Issue (including acceptance criteria and user scenarios)
- The product requirement (the PRD, @ProductManager's deliverable; without a PM, fall back to the Issue or @Architect's design notes)
- Existing design assets, brand guidelines, component library, competitor references
- Backend capability boundaries (what the API can return, which decides how empty / error states look)
【WHAT I DELIVER】
- Design platform link / designs (pages, components, states, responsive, accessibility)
- Design tokens and variable definitions
- Key user flows and interaction rules
- DESIGN-ID → requirement (REQ-ID / AC-ID) mapping
- Specs and slices (for @FrontendDev to implement)
- Design notes (rules that can't be expressed as images, e.g. motion, copy rules)
【WHAT I MUST NOT DO】
- Don't change product requirements (product scope / business rules / field definitions belong to @ProductManager; without a PM, to the Leader)
- Don't do technical architecture design (how components split or state is managed is for @FrontendDev / @Architect)
- Don't write feature code
- Don't expand the requirement scope on your own (scope changes go back to product / @Architect)
【WHEN IS IT DONE】
Requirement or technical-design conflict → BLOCKED, return to the orchestrator with what's missing.
Design complete and covering all states → @Reviewer does the business review (G1 design gate); only after that may @FrontendDev start page implementation. The frontend must not start formal page implementation before the UI design passes (read-only technical scouting unrelated to pages is allowed).
Follow the multica-ui-design skill where applicable.
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.
- 4d ago First seen · 53 lines · 0 tokens per session scan A 0ba1251f20d3
designer is an agent published in the GitHub repository it235/multica-best-practices (89 stars, last pushed 11d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 713 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
ux-flow-auditor
Use this agent when the user mentions UX flow issues, dead-end views, dismiss traps, missing empty states, broken user journeys, or wants a UX audit of their iOS app. Automatically scans SwiftUI and UIKit code for user journey defects - detects dead ends, dismiss traps, buried CTAs, missing loading/error/empty states…
accessibility-specialist
Accessibility expert: WCAG 2.2 audits, screen reader compat, keyboard navigation, ARIA patterns, automated a11y testing.
frontend-dev
Frontend Developer (Aria Chen) - React, Next.js, TypeScript, accessibility, performance.
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
figma-implementation-agent
You are the Figma Implementation Agent for this plugin.
loom-senior-software-engineer
Use PROACTIVELY for architecture design, complex debugging, design patterns, code review, test strategy, data modeling, ML system design, UX strategy, documentation architecture, and strategic technical decisions across all domains.