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/catlog22/Claude-Code-WorkflowWrote 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/commands/catlog22/claude-code-workflow/design-sync)<a href="https://agentmods.dev/commands/catlog22/claude-code-workflow/design-sync"><img src="https://agentmods.dev/badge/commands/catlog22/claude-code-workflow/design-sync/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.
<a href="https://agentmods.dev/commands/catlog22/claude-code-workflow/design-sync"><img src="https://agentmods.dev/badge/commands/catlog22/claude-code-workflow/design-sync.svg" alt="Reviewed on agentmods" width="80" 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.00020 | $0.04147 |
| Opus 5.5 | $0.00008 | $0.01659 |
| Sonnet 5.5 | $0.00004 | $0.00829 |
| Haiku 4.5 | $0.00002 | $0.00415 |
Grade A, and why
design-sync 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 1mo 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 — 455 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Sync Command
Overview
Synchronize finalized design system references to brainstorming artifacts, preparing them for workflow-plan skill consumption. This command updates references only (via @ notation), not content duplication.
Core Philosophy
- Reference-Only Updates: Use @ references, no content duplication
- Main Claude Execution: Direct updates by main Claude (no Agent handoff)
- Synthesis Alignment: Update role analysis documents UI/UX Guidelines section
- Plan-Ready Output: Ensure design artifacts discoverable by task-generate
- Minimal Reading: Verify file existence, don't read design content
Execution Process
Input Parsing:
├─ Parse flags: --session, --selected-prototypes
└─ Validation: session_id REQUIRED
Phase 1: Session & Artifact Validation
├─ Step 1: Validate session exists
├─ Step 2: Find latest design run
├─ Step 3: Detect design system structure
└─ Step 4: Select prototypes (--selected-prototypes OR all)
Phase 1.1: Memory Check (Conditional)
└─ Decision (current design run in synthesis):
├─ Already updated → Skip Phase 2-5, EXIT
└─ Not found → Continue to Phase 2
Phase 2: Load Target Artifacts
├─ Read role analysis documents (files to update)
├─ Read ui-designer/analysis.md (if exists)
└─ Read prototype notes (minimal context)
Phase 3: Update Synthesis Specification
└─ Edit role analysis documents with UI/UX Guidelines section
Phase 4A: Update Relevant Role Analysis Documents
├─ ui-designer/analysis.md (always)
├─ ux-expert/analysis.md (if animations exist)
├─ system-architect/analysis.md (if layouts exist)
└─ product-manager/analysis.md (if prototypes)
Phase 4B: Create UI Designer Design System Reference
└─ Write ui-designer/design-system-reference.md
Phase 5: Update Context Package
└─ Update context-package.json with design system references
Phase 6: Completion
└─ Report updated artifacts
Execution Protocol
Phase 1: Session & Artifact Validation
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.
- 1mo ago First seen · 455 lines · 20 tokens per session scan A a82ed34ebb14
design-sync is a command published in the GitHub repository catlog22/Claude-Code-Workflow (2,125 stars, last pushed 4mo ago), licensed MIT. It adds 20 tokens to every session and 4,147 once invoked, about $0.0001 per session on Opus 5.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 commands, from other repositories
multi-frontend
Run a frontend-focused multi-model workflow for components, layouts, animation, and UI polish.
create-excalidraw-diagram
description: "Create system architecture or technical diagram (Excalidraw) (Use any time you need a diagram)".
verify-claim
Walk a claim through the SIFT method (Stop, Investigate, Find better coverage, Trace).
my_brand
Interactive brand identity creation with archetypes, colors, typography, and voice guidelines. Use when user mentions "brand", "colors", "typography", "brand.md", "design system", or "visual identity".
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.