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/realmpastai-web/claude-design-suiteWrote 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/realmpastai-web/claude-design-suite/setup-workflow)<a href="https://agentmods.dev/commands/realmpastai-web/claude-design-suite/setup-workflow"><img src="https://agentmods.dev/badge/commands/realmpastai-web/claude-design-suite/setup-workflow.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.1 | $0.00009 | $0.00228 |
| Opus 5 | $0.00005 | $0.00114 |
| Sonnet 5 | $0.00002 | $0.00046 |
| Haiku 4.5 | $0.00001 | $0.00023 |
Grade A, and why
setup-workflow 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 6d 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.
This is a copy
88% identical to setup-workflow — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
/setup-workflow
Set up a design team workflow.
Steps
- Team structure — Define roles and responsibilities using
team-workflowskill. - Rituals — Establish collaboration cadence using
team-workflowskill. - Critique process — Set up design critique format using
design-critiqueskill. - Review gates — Define quality checkpoints using
design-review-processskill. - Versioning — Establish file and library versioning using
version-control-strategyskill. - QA process — Set up design QA workflow using
design-qa-checklistskill.
Output
Team workflow document with rituals calendar, critique format, review process, versioning strategy, QA checklist, and tooling recommendations.
Consider following up with /plan-sprint to kick off your first project with the new workflow.
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.
- 6d ago First seen · 17 lines · 9 tokens per session scan A be9030cbc01b
setup-workflow is a command published in the GitHub repository realmpastai-web/claude-design-suite (2 stars, last pushed 4mo ago), licensed MIT. It adds 9 tokens to every session and 228 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to setup-workflow, differing in 2 lines, and is treated as a copy.
Other commands, from other repositories
extract-screens
Analyze user stories in the current project and extract screens + reusable UI components into project-management/screens/ and project-management/components/. Requires user stories in project-management/user-stories/.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
m-task-planner
Target: $ARGUMENTS (Default: requirement document(s) discovered in the project).
gofer:check-workspace
Check whether this repo is initialized for Gofer and explain any missing or stale scaffold.