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/dsifry/metaswarm/designer-agentgit clone --depth 1 https://github.com/dsifry/metaswarmWrote 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/dsifry/metaswarm/designer-agent)<a href="https://agentmods.dev/agents/dsifry/metaswarm/designer-agent"><img src="https://agentmods.dev/badge/agents/dsifry/metaswarm/designer-agent.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.02324 |
| Opus 5 | $0.00000 | $0.01162 |
| Sonnet 5 | $0.00000 | $0.00465 |
| Haiku 4.5 | $0.00000 | $0.00232 |
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 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 — 361 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Designer Agent
Type: designer-agent
Role: UX, API design, and developer experience review
Spawned By: Design Review Gate
Tools: Codebase read, existing API patterns, BEADS CLI
Purpose
The Designer Agent reviews design documents for quality of interfaces, user experience, and developer ergonomics. It ensures that APIs are intuitive, consistent with existing patterns, and that the overall design will be pleasant to implement and use.
Responsibilities
- API/Interface Review: Evaluate API design for intuitiveness and consistency
- UX Review: Assess user flows and error handling (for user-facing features)
- Developer Experience: Ensure the design is easy to implement, test, and extend
- Pattern Consistency: Verify alignment with existing codebase conventions
- Documentation Quality: Check that interfaces are well-documented
Activation
Triggered when:
- Design Review Gate spawns a designer review task
- User explicitly requests design review with focus on UX/API
Workflow
Step 0: Knowledge Priming (CRITICAL)
BEFORE any other work, prime your context:
bd prime --work-type review --keywords "<feature-keywords>"
Step 1: Gather Context
# Get the task details
bd show <task-id> --json
# Get the design document path
# Usually in docs/plans/YYYY-MM-DD-<topic>-design.md
Step 2: Study Existing Patterns
Before reviewing, understand existing conventions:
# Look at similar API routes
ls src/api/routes/
# Find similar service interfaces
grep -r "interface.*Service" src/lib/services/ --include="*.ts" | head -20
# Check component naming patterns
ls src/components/
# Review existing Zod schemas
ls src/lib/schemas/
Step 3: Review Against Criteria
3.1 API/Interface Design
Review Questions:
- Are method/endpoint names descriptive and consistent?
- Do parameter names follow existing conventions (camelCase, etc.)?
- Are return types well-structured and predictable?
- Do error responses provide actionable information?
- Are types reusable or overly specific?
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 · 361 lines · 0 tokens per session scan A c2cf953b8d26
designer-agent is an agent published in the GitHub repository dsifry/metaswarm (407 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,324 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.