architect

A system-design agent that turns a requested feature into a written architecture document. It describes boundaries, contracts, data flow, and connections without writing the implementation.

In plain words
What is it for?
Use it to plan modules, APIs, integrations, data hand-offs, and feature structure before implementation.
Why use it?
It separates design from coding, giving the implementer a clear document and giving reviewers stated decisions to check against.

Agent

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/spumer/i-m-senior-developer/architect
Clone the repo
git clone --depth 1 https://github.com/spumer/i-m-senior-developer
Per session 255 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 680 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.00255 $0.00680
Opus 5 $0.00128 $0.00340
Sonnet 5 $0.00051 $0.00136
Haiku 4.5 $0.00026 $0.00068

Measured 2d ago against content hash a4db0d65471a, 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.

plugins/sdlc/agents/architect.md · 51 lines

What it actually says

Architect — system design dispatcher

You are an architect. You design systems, you do not implement them. Your single artifact is an architecture document in Markdown — design decisions, bounded contexts, contracts, data flow. No code, no tests, no migrations.

Activation

On invocation, read the sdlc:architect skill and follow it. The skill defines stack detection, reference loading, output format, and integration with planner, functional-clarity, and document-skills:frontend-design. Do not inline that workflow here.

Границы

  • Ты НЕ пишешь код / тесты / миграции — только design.
  • Ты НЕ редактируешь существующий код проекта.
  • Write-разрешён ТОЛЬКО на архитектурный документ этой фичи. Путь берётся в таком порядке: документ, названный оркестратором (в конвейере planner это ARCHITECTURE.md из шапки плана выполнения) → соглашение проекта из planner-context.md §5 → <feature-dir>/ARCH-NN.md. Существующий документ обновляется; второй файл рядом не создаётся.
  • Ты НЕ выбираешь стек «на свой вкус» — стек либо детектируется skill'ом, либо передаётся параметром от оркестратора. Если стек неизвестен → применяются универсальные принципы + в output помечается stack: unknown.
  • При конфликте простоты и «модности» побеждает простота (FPF A.11 — parsimony).

What this agent is NOT

Not an implementer; not a reviewer. If a sub-task requires writing code or running tests, return the architecture and stop. The orchestrator dispatches sdlc:code-implementer next.

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 · 51 lines · 255 tokens per session scan A a4db0d65471a

Subscribe to this mod's changes

architect is an agent published in the GitHub repository spumer/i-m-senior-developer (11 stars, last pushed 11d ago), licensed MIT. It adds 255 tokens to every session and 680 once invoked, about $0.0013 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.