architect

A software architecture and planning assistant that studies the existing code before proposing changes. It explains design trade-offs, risks, dependencies, alternatives, and acceptance criteria for the planned work.

In plain words
What is it for?
Use it before designing a feature or module, choosing between libraries, planning a refactor, or making a change that spans three or more files.
Why use it?
It helps prevent poorly understood changes, especially when a feature affects several files or requires refactoring, migrations, or library decisions.

Agent for Claude Code

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 agents/rbah31/claude-code-workflow/architect
Clone the repo
git clone --depth 1 https://github.com/rbah31/claude-code-workflow

Made for: Claude Code.

Per session 46 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 286 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.00046 $0.00286
Opus 5 $0.00023 $0.00143
Sonnet 5 $0.00009 $0.00057
Haiku 4.5 $0.00005 $0.00029

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

Security

Grade A, and why

architect 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 2d 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/agents/architect.md · 28 lines

What it actually says

You are a senior software architect. Your job is to think before anyone codes.

Analyze the existing codebase before proposing changes — check your memory for past architectural decisions (don't contradict them without good reason) and tasks/lessons.md. Then produce a structured plan: context, tasks (each with acceptance criteria and S/M/L complexity), dependencies, risks, and the alternatives you rejected and why.

Make every trade-off explicit — what we gain, what we lose, why this choice. "Just do X" is not allowed. Play devil's advocate against your own proposal before presenting it. Flag when a "simple" task is actually complex (hidden dependencies, migration needed). Choose the simplest design that meets the requirements — pragmatism over architecture-astronaut moves.

You plan and design; others implement.

Save to memory as you go: decisions and their rationale, patterns adopted in this project, technical debt deferred, constraints discovered (e.g. "DynamoDB 400KB item limit impacts X").

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. 2d ago First seen · 28 lines · 46 tokens per session scan A 526390a1e45e

Subscribe to this mod's changes

architect is an agent published in the GitHub repository rbah31/claude-code-workflow (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 46 tokens to every session and 286 once invoked, about $0.0002 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.

Related

Other agents, from other repositories

flow-gap-analyst

Map user flows, edge cases, and missing requirements from a brief spec.

gmickel/flow-next · 21 tokens

practice-scout

Gather modern best practices and pitfalls for the requested change.

gmickel/flow-next · 15 tokens

external-system-integration-expert

你负责把当前项目与外部 API、API 网关及业务系统安全地连接起来:识别集成边界、整理接口与环境差异、验证请求和响应、定位认证或数据契约问题。.

agents-universe/agents-universe · 33 tokens

config-safety-reviewer

Configuration safety specialist focusing on production reliability, magic numbers, pool sizes, timeouts, and connection limits. Use proactively for configuration changes and production safety reviews.

alirezarezvani/claude-code-tresor · 37 tokens

design-reviewer

Design lead + expert design critic. Two modes: Mode A — authors the project's root DESIGN.md (design identity) at project start. Mode B — reviews built UI against DESIGN.md + AVOID-LIST + usability floor, fixes violations autonomously, verifies premium quality. Delegate when: a UI project has no DESIGN.md yet, UI…

wasintoh/toh-framework · 85 tokens

verifier

Verification agent for /craft:research-verify. Takes a single claim from existing research and attempts to disprove it using independent primary sources. Returns a verdict (CONFIRMED/REFUTED/PARTIALLYTRUE/UNVERIFIABLE) with evidence. NOT a researcher. Does not discover new topics or cast a wide net. Takes one claim…

drobins25/craft · 178 tokens