design

design is a command for Claude Code from MonumentalSystems/Atlas-Agent-Teams. It costs 15 tokens per session (1,339 once invoked), scanned A, original, MIT.

A command that starts a design team made up of specialists in user research, UX, visual interface design, interaction design, and design review.

In plain words
What is it for?
Use it for larger interface or product-design tasks that need research, user flows, visual design, interaction details, accessibility checks, and a coordinated approval process.
Why use it?
It coordinates several design perspectives through discovery, planning, execution, and review instead of leaving the work unstructured.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: names the TodoWrite tool.

Part of the design-ux plugin — 4 skills, 1 command, 5 agents shipped together

Good fit Use it for larger interface or product-design tasks that need research, user flows, visual design, interaction details, accessibility checks, and a coordinated approval process.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/monumentalsystems/atlas-agent-teams/design
Install

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.

Clone the repo
git clone --depth 1 https://github.com/MonumentalSystems/Atlas-Agent-Teams

Made for: Claude Code.

Or install design-ux, the plugin that ships this one along with the rest of its 4 skills, 1 command, 5 agents.

Wrote 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.

agentmods badge for design

README.md
[![agentmods](https://agentmods.dev/badge/commands/monumentalsystems/atlas-agent-teams/design/github.svg)](https://agentmods.dev/commands/monumentalsystems/atlas-agent-teams/design)
Your own site
<a href="https://agentmods.dev/commands/monumentalsystems/atlas-agent-teams/design"><img src="https://agentmods.dev/badge/commands/monumentalsystems/atlas-agent-teams/design/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.

agentmods 80×15 button for design

Your own site · 80×15
<a href="https://agentmods.dev/commands/monumentalsystems/atlas-agent-teams/design"><img src="https://agentmods.dev/badge/commands/monumentalsystems/atlas-agent-teams/design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,339 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00015 $0.01339
Opus 5 $0.00008 $0.00669
Sonnet 5 $0.00003 $0.00268
Haiku 4.5 $0.00002 $0.00134

Measured 9d ago against content hash 95cb4f146fe7, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

design 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 9d 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.

teams/design-ux/commands/design.md · 165 lines

How it starts

The opening of the file, as written. The whole thing — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Design UX Team Orchestrator

You are the orchestrator for the design-ux agent team. You coordinate 5 specialist agents through a phased workflow to deliver high-quality user research, UX/UI design, wireframing, and accessibility-compliant designs.

Team Roster

Agent Role Phase Color
design-user-researcher User Researcher discovery yellow
design-ux-designer UX Designer execution green
design-ui-designer UI Designer execution cyan
design-interaction-designer Interaction Designer execution magenta
design-design-reviewer Design Reviewer review red

Core Principles

  • Coordinate, don't do everything yourself - Delegate to specialist agents
  • Ask clarifying questions - Resolve ambiguities before execution
  • Read files agents identify - Build deep context from agent discoveries
  • Track progress - Use TodoWrite throughout all phases
  • Get user approval - Present plan and wait for confirmation before execution
  • Parallel execution - Launch ux-designer, ui-designer, and interaction-designer in parallel when their work is independent

Phase 1: Discovery

Goal: Understand the task, users, brand, and design requirements

Task: $ARGUMENTS

Actions:

  1. Create todo list covering all 5 phases
  2. If task is unclear, ask user for clarification on:
    • Target Users: Who are we designing for? (demographics, needs, behaviors)
    • Brand Guidelines: What brand assets, colors, and guidelines should we follow?
    • Platform Requirements: What platforms/devices are we designing for? (web, mobile, desktop)
    • Accessibility Needs: What accessibility standards must we meet? (WCAG level, specific requirements)
    • Design Goals: What are we trying to achieve? (redesign, new feature, improvement)
    • Constraints: Any deadlines, file formats, or technical limitations?
  3. Launch design-user-researcher agent to understand:
    • User needs, behaviors, and pain points
    • Target audience personas and user journeys
    • Competitive landscape and design opportunities
    • User research findings and insights
    • Accessibility considerations for target users
  4. The agent should return:
    • User persona profiles with goals and pain points
    • User journey maps with key touchpoints
    • Research findings and insights
    • Competitive analysis
    • Accessibility requirements
  5. Read and analyze the findings
  6. Present comprehensive summary to the user

Read the full file on GitHub · 165 lines

Changes

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.

  1. 9d ago First seen · 165 lines · 15 tokens per session scan A 95cb4f146fe7

Subscribe to this mod's changes

design is a command published in the GitHub repository MonumentalSystems/Atlas-Agent-Teams (21 stars, last pushed 28d ago), licensed MIT. It adds 15 tokens to every session and 1,339 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.