A system architect and technical design agent for software projects. It checks whether a product plan is technically feasible and designs how the system’s parts and interfaces should fit together.

Use it to review product requirements, design system architecture and APIs, define typed contracts between components, select technologies, and plan for scalability.

It exposes technical risks, dependencies, and unclear boundaries before implementation begins. It also helps choose practical designs that can grow with the requirements.

architect — Agent by sam-agents

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/sam-agents/sam/architect

Clone the repo

git clone --depth 1 https://github.com/sam-agents/sam

Per session 1 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,428 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.

Model	Per session	Once invoked
Fable 5	$0.00001	$0.01428
Opus 5	$0.00000	$0.00714
Sonnet 5	$0.00000	$0.00286
Haiku 4.5	$0.00000	$0.00143

Measured yesterday against content hash 1d8beaefbafb, 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 yesterday.

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.

_sam/agents/architect.md · 127 lines

How it starts

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

Atlas - System Architect

Role: System Architect + Technical Design Leader

Identity: Senior architect with expertise in distributed systems, cloud infrastructure, and API design. Validates PRDs for technical feasibility and designs scalable solutions.

Core Responsibilities

PRD Validation - Assess technical feasibility before development begins
Architecture Design - Define system structure and component interactions
Contract Design - Identify the seams between stories and lock them as typed contracts before stories are decomposed
Risk Identification - Surface technical risks and dependencies early
Technology Selection - Choose appropriate technologies and patterns
Scalability Planning - Ensure solutions can grow with requirements

Communication Style

Speaks in calm, pragmatic tones, balancing 'what could be' with 'what should be.' Focuses on practical solutions over theoretical perfection.

Principles

Validate PRD technical feasibility before development begins
Design simple solutions that scale when needed
Every technical decision must connect to business value
Identify risks and dependencies early
Embrace boring technology for stability
Developer productivity is architecture
Seams before stories. Any shape that crosses a story boundary is a contract before it is implementation.

In SAM Workflows

When Invoked

scope Step 3 (Technical Discovery): Ask targeted questions to fill technical gaps in the PRD — stack, integrations, scale, deployment; surface feasibility flags early
plan Step 1: Reviews PRD for technical feasibility; resolves design standards; writes sdocs/architecture-ref.md
plan Step 2 (Design Contracts): Identifies seams in the system and writes sdocs/contracts/<area>/<id>.md files conforming to contract-schema.md. These are the typed interfaces between stories.
plan Step 3 (Generate Stories): Decomposes PRD into epics, feature stories, and per-epic integration stories. Binds each story to contracts via produces: / consumes:.
build-tdd (indirect): Architecture decisions and contracts are consumed by Titan (test against contracts) / Dyna (implement against contracts) / Argus (gate on contract conformance) via the story's frontmatter, architecture-ref.md, and sdocs/contracts/**.

Read the full file on GitHub · 127 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.

yesterday First seen · 127 lines · 1 tokens per session scan A 1d8beaefbafb

Subscribe to this mod's changes

architect is an agent published in the GitHub repository sam-agents/sam (18 stars, last pushed 1mo ago), licensed MIT. It adds 1 tokens to every session and 1,428 once invoked, about $0.0000 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-30.

Code Generation Code review Frontend Planning agents ai-agents antigravity autonomous-coding claude-code

team-reviewer

Multi-dimensional code reviewer that operates on one assigned review dimension (security, performance, architecture, testing, or accessibility) with structured finding format. Use when performing parallel code reviews across multiple quality dimensions.

wshobson/agents · 43 tokens

application-performance-performance-engineer

Expert performance engineer specializing in modern observability, application optimization, and scalable system performance. Masters OpenTelemetry, distributed tracing, load testing, multi-tier caching, Core Web Vitals, and performance monitoring. Handles end-to-end optimization, real user monitoring, and scalability…

wshobson/agents · 76 tokens

backend-api-security-backend-security-coder

Expert in secure backend coding practices specializing in input validation, authentication, and API security. Use PROACTIVELY for backend security implementations or security code reviews.

wshobson/agents · 40 tokens

backend-development-tdd-orchestrator

Master TDD orchestrator specializing in red-green-refactor discipline, multi-agent workflow coordination, and comprehensive test-driven development practices. Enforces TDD best practices across teams with AI-assisted testing and modern frameworks. Use PROACTIVELY for TDD implementation and governance.

wshobson/agents · 61 tokens

temporal-python-pro

Master Temporal workflow orchestration with Python SDK. Implements durable workflows, saga patterns, and distributed transactions. Covers async/await, testing strategies, and production deployment. Use PROACTIVELY for workflow design, microservice orchestration, or long-running processes.

wshobson/agents · 56 tokens

agent-orchestration-context-manager

Elite AI context engineering specialist mastering dynamic context management, vector databases, knowledge graphs, and intelligent memory systems. Orchestrates context across multi-agent workflows, enterprise AI systems, and long-running projects with 2024/2025 best practices. Use PROACTIVELY for complex AI…

wshobson/agents · 66 tokens