Borrowing it
Nothing to install: this file belongs to rcdelacruz/claude-code-agents. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/rcdelacruz/claude-code-agents/main/.claude/commands/workflow-design-architecture.mdgit clone --depth 1 https://github.com/rcdelacruz/claude-code-agentsWrote 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/rcdelacruz/claude-code-agents/workflow-design-architecture)<a href="https://agentmods.dev/commands/rcdelacruz/claude-code-agents/workflow-design-architecture"><img src="https://agentmods.dev/badge/commands/rcdelacruz/claude-code-agents/workflow-design-architecture.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.00380 |
| Opus 5 | $0.00005 | $0.00190 |
| Sonnet 5 | $0.00002 | $0.00076 |
| Haiku 4.5 | $0.00001 | $0.00038 |
Grade A, and why
workflow-design-architecture 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 7d 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.
What it actually says
You are in ARCHITECTURE DESIGN MODE.
Use the architect agent to:
-
Analyze Requirements
- Understand functional and non-functional requirements
- Identify constraints (budget, timeline, team size, existing systems)
- Clarify scale expectations (users, data volume, geographic distribution)
-
Design System Architecture
- Choose architectural pattern (monolith, microservices, serverless)
- Design system components and their interactions
- Create architecture diagrams (component, deployment, sequence)
- Define data flow and integration points
-
Make Technology Decisions
- Select appropriate tech stack based on requirements
- Choose database strategy (SQL vs NoSQL, single vs multiple DBs)
- Define API architecture (REST, GraphQL, tRPC, gRPC)
- Plan authentication and authorization strategy
- Choose deployment platform (Vercel, AWS, GCP, Azure, on-prem)
-
Plan for Scalability
- Identify scaling bottlenecks
- Design caching strategy (client, CDN, server, database)
- Plan for horizontal and vertical scaling
- Design for resilience (circuit breakers, retries, fallbacks)
-
Document Decisions
- Create Architecture Decision Records (ADRs)
- Document trade-offs and rationale
- Define success metrics
- Plan migration path if applicable
Output: Comprehensive architecture design document with diagrams, technology stack, and clear rationale for decisions.
Next Steps After Design:
- Use
/mcp-design-nextjsor/mcp-design-springfor technology-specific design - Use
/mcp-implement-fullstackto start implementation - Use
/mcp-review-codeto review architecture decisions in code
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.
- 7d ago First seen · 45 lines · 9 tokens per session scan A 9680dee00bbd
workflow-design-architecture is a command published in the GitHub repository rcdelacruz/claude-code-agents (2 stars, last pushed 10mo ago), licensed MIT. It adds 9 tokens to every session and 380 once invoked, about $0.0000 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-31.
Other commands, from other repositories
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.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.