design-architecture

design-architecture is a command for Claude Code from kumaran-is/claude-code-onboarding. It costs 18 tokens per session (199 once invoked), scanned A, original, MIT.

An architecture-planning command for turning a feature or system's requirements into diagrams, API definitions, local setup, and a written technology decision.

In plain words
What is it for?
Use it to document system structure, define OpenAPI contracts, map important request flows, prepare Docker Compose development setup, and save architecture records.
Why use it?
It gives a team a shared technical plan before implementation begins, including how parts connect and what trade-offs matter.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Good fit Use it to document system structure, define OpenAPI contracts, map important request flows, prepare Docker Compose development setup, and save architecture records.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/kumaran-is/claude-code-onboarding/design-architecture
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/kumaran-is/claude-code-onboarding

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

README.md
[![agentmods](https://agentmods.dev/badge/commands/kumaran-is/claude-code-onboarding/design-architecture.svg)](https://agentmods.dev/commands/kumaran-is/claude-code-onboarding/design-architecture)
Your own site
<a href="https://agentmods.dev/commands/kumaran-is/claude-code-onboarding/design-architecture"><img src="https://agentmods.dev/badge/commands/kumaran-is/claude-code-onboarding/design-architecture.svg" alt="Measured on agentmods" height="20"></a>
Per session 18 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 199 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.00018 $0.00199
Opus 5 $0.00009 $0.00100
Sonnet 5 $0.00004 $0.00040
Haiku 4.5 $0.00002 $0.00020

Measured 4d ago against content hash a445d92a5266, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

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 4d 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/design-architecture.md · 26 lines

What it actually says

Design System Architecture

Design the architecture for the following system or feature:

Requirements: $ARGUMENTS

Steps

  1. Clarify and summarize the requirements and NFRs
  2. Create a C4 System Context diagram (Mermaid)
  3. Create a component-level architecture diagram (Mermaid)
  4. Define key API contracts (OpenAPI YAML snippets)
  5. Draw sequence diagrams for critical flows (Mermaid)
  6. Provide a Docker Compose setup for local development
  7. Write an ADR (Architecture Decision Record) for the key technology choice
  8. Summarize trade-offs and next steps

Use the architecture-design skill for templates. Save output files to a docs/architecture/ directory.

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. 4d ago First seen · 26 lines · 18 tokens per session scan A a445d92a5266

Subscribe to this mod's changes

design-architecture is a command published in the GitHub repository kumaran-is/claude-code-onboarding (35 stars, last pushed 2mo ago), licensed MIT. It adds 18 tokens to every session and 199 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-09-03.