agentmods.dev

claude-code-agents: Command for Claude Code

.claude/commands/workflow-design-architecture.md

workflow-design-architecture is a command for Claude Code from rcdelacruz/claude-code-agents. It costs 9 tokens per session (380 once invoked), scanned A, original, MIT.

A command for designing a software system’s overall structure and making high-level technical decisions.

In plain words
What is it for?
Use it to choose an architecture, database, API style, authentication approach, cloud platform, scaling strategy, and documented architecture decisions.
Why use it?
It helps turn requirements and constraints such as budget, scale, and team size into a consistent technical plan.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is rcdelacruz/claude-code-agents's own configuration. It tells Claude Code how to work on claude-code-agents itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything claude-code-agents configures →

not rated 2repo 1y ago A scan 9 tokens original MIT
View source ↗ rcdelacruz/claude-code-agents claude-code-agents-docs.stratpoint.io
Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/rcdelacruz/claude-code-agents/main/.claude/commands/workflow-design-architecture.md
Clone the repo
git clone --depth 1 https://github.com/rcdelacruz/claude-code-agents

Made for: Claude Code.

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 workflow-design-architecture

README.md
[![agentmods](https://agentmods.dev/badge/commands/rcdelacruz/claude-code-agents/workflow-design-architecture/github.svg)](https://agentmods.dev/commands/rcdelacruz/claude-code-agents/workflow-design-architecture)
Your own site
<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/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 workflow-design-architecture

Your own site · 80×15
<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="Reviewed on agentmods" width="80" height="20"></a>
Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 380 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.00009 $0.00380
Opus 5.5 $0.00004 $0.00152
Sonnet 5.5 $0.00002 $0.00076
Haiku 4.5 $0.00001 $0.00038

Measured 2mo ago against content hash 9680dee00bbd, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

.claude/commands/workflow-design-architecture.md · 45 lines

What it actually says

You are in ARCHITECTURE DESIGN MODE.

Use the architect agent to:

  1. Analyze Requirements

    • Understand functional and non-functional requirements
    • Identify constraints (budget, timeline, team size, existing systems)
    • Clarify scale expectations (users, data volume, geographic distribution)

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

  3. 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)

  4. 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)

  5. 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-nextjs or /mcp-design-spring for technology-specific design
  • Use /mcp-implement-fullstack to start implementation
  • Use /mcp-review-code to review architecture decisions in code
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. 2mo ago First seen · 45 lines · 9 tokens per session scan A 9680dee00bbd

Subscribe to this mod's changes

workflow-design-architecture is a command published in the GitHub repository rcdelacruz/claude-code-agents (2 stars, last pushed 1y ago), licensed MIT. It adds 9 tokens to every session and 380 once invoked, about $0.0000 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-31.

Planning
Related

workflow-design-architecture compared with commands from other repositories

workflow-design-architecture next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
workflow-design-architecturercdelacruz/claude-code-agentsCommand21y agoMITA9Claude Code
checklistgithub/spec-kitCommand148kyesterdayMITA13Claude Code
clarifygithub/spec-kitCommand148kyesterdayMITA27Claude Code
specifygithub/spec-kitCommand148kyesterdayMITA13Claude Code
analyzegithub/spec-kitCommand148kyesterdayMITA26Claude Code
convergegithub/spec-kitCommand148kyesterdayMITA35Claude Code
implementgithub/spec-kitCommand148kyesterdayMITA14Claude Code