design

design is a command for coding agents from ruslan-korneev/claude-plugins. It costs 13 tokens per session (1,703 once invoked), scanned A, original, MIT.

An interactive command for planning the architecture of a new project or a major module. It gathers requirements and compares approaches such as a modular monolith, microservices, event-driven design, and layered design.

In plain words
What is it for?
Use it to discuss system purpose, user workflows, expected scale, external services, technology constraints, and a suitable way to divide the code.
Why use it?
It connects technical structure to the project’s size, workload, integrations, and constraints. This helps avoid choosing an architecture without understanding what the system needs.

Command

Part of the tech-lead plugin — 14 commands, 9 agents shipped together

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.

agentmods
npx agentmods add commands/ruslan-korneev/claude-plugins/design
Clone the repo
git clone --depth 1 https://github.com/ruslan-korneev/claude-plugins

Or install tech-lead, the plugin that ships this one along with the rest of its 14 commands, 9 agents.

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

README.md
[![agentmods](https://agentmods.dev/badge/commands/ruslan-korneev/claude-plugins/design.svg)](https://agentmods.dev/commands/ruslan-korneev/claude-plugins/design)
Your own site
<a href="https://agentmods.dev/commands/ruslan-korneev/claude-plugins/design"><img src="https://agentmods.dev/badge/commands/ruslan-korneev/claude-plugins/design.svg" alt="Measured on agentmods" height="20"></a>
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,703 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00013 $0.01703
Opus 5 $0.00006 $0.00851
Sonnet 5 $0.00003 $0.00341
Haiku 4.5 $0.00001 $0.00170

Measured 3d ago against content hash 29732845010b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

design 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 3d 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.

plugins/tech-lead/commands/design.md · 314 lines

How it starts

The opening of the file, as written. The whole thing — 314 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Command /architect:design

Interactive architecture design workflow for new projects or major features.

Instructions

Step 1: Gather Requirements

Use AskUserQuestion to understand the project scope:

Questions to ask:

  1. What is the primary purpose of this system?
  2. What are the main use cases / user stories?
  3. Expected scale (users, requests/sec, data volume)?
  4. What external systems need integration (databases, APIs, queues)?
  5. Any specific constraints (tech stack, compliance, team expertise)?

Step 2: Analyze Existing Codebase (if applicable)

If this is a new module in existing project:

  • Check existing structure with Glob
  • Identify patterns already in use
  • Ensure consistency with existing modules

Step 3: Choose Architecture Style

Based on requirements, recommend one of:

Style When to Use
Modular Monolith Small team (<10), uncertain requirements, MVP
Microservices Large team, independent scaling needs, different tech stacks
Event-Driven Real-time processing, loose coupling between modules
Layered (Clean/Hexagonal) Complex business logic, long-term maintainability

Step 4: Design Module Structure

For FastAPI + SQLAlchemy projects, propose structure:

src/
├── core/
│   ├── __init__.py
│   ├── config.py           # Settings with pydantic-settings
│   ├── database.py         # AsyncSession setup
│   ├── container.py        # DI container
│   ├── dependencies.py     # FastAPI dependencies
│   ├── exceptions.py       # Base exceptions
│   └── repositories.py     # BaseRepository
│
├── modules/
│   └── {{ name }}/
│       ├── __init__.py     # Public API exports
│       ├── models.py       # SQLAlchemy models
│       ├── dto.py          # Pydantic DTOs
│       ├── repositories.py # Data access layer
│       ├── services.py     # Business logic
│       ├── routers.py      # HTTP endpoints
│       └── events.py       # Domain events (if needed)
│
├── shared/
│   ├── protocols.py        # Shared interfaces
│   └── events.py           # Event bus
│
└── main.py                  # FastAPI app entry point

Read the full file on GitHub · 314 lines

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. 3d ago First seen · 314 lines · 13 tokens per session scan A 29732845010b

Subscribe to this mod's changes

design is a command published in the GitHub repository ruslan-korneev/claude-plugins (4 stars, last pushed 6mo ago), licensed MIT. It adds 13 tokens to every session and 1,703 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-08-31.