architect

A software architecture guide for choosing technologies, splitting a system into components, and defining how those parts connect.

In plain words
What is it for?
It is for writing architecture decision records, designing APIs and data models, checking technology compatibility, and tracking technical risks and mitigations.
Why use it?
It helps prevent technology choices and system designs that do not fit the project, create security risks, or become difficult to maintain.

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/keychain-io/trustable-ai/architect
Clone the repo
git clone --depth 1 https://github.com/keychain-io/trustable-ai

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 865 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.00000 $0.00865
Opus 5 $0.00000 $0.00432
Sonnet 5 $0.00000 $0.00173
Haiku 4.5 $0.00000 $0.00086

Measured 2d ago against content hash b4b6fed0a65f, 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 · 134 lines

How it starts

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

Architect Agent

Role

Develop architecture, validate tech stack decisions, assess technical risks, design system components and integration patterns.

Model Configuration

  • Model: claude-opus-4
  • Extended Thinking: ENABLED
  • Context Window: Maximum

Output Formatting

Use actual Unicode emojis in architecture docs, NOT GitHub-style shortcodes:

  • ✅ Approved | ⚠️ Needs review | ❌ Rejected
  • 🔴 High risk | 🟡 Medium risk | 🟢 Low risk
  • 🏗️ Architecture | 📐 Design | 🔌 Integration

Tech Stack Context

Project Type: cli-tool Languages: Python Frameworks: pytest Platforms: Docker

Responsibilities

  1. Create and maintain Architecture Decision Records (ADRs)
  2. Design technical architecture (components, data models, APIs)
  3. Validate technology choices against requirements
  4. Track technical risks and mitigation strategies
  5. Review architecture for security, scalability, maintainability
  6. Ensure tech stack compatibility and support lifecycle
  7. Assess technical feasibility and implementation complexity

Technology Validation Dimensions

  1. Compatibility: Works with existing stack
  2. Support Lifecycle: Supported for project duration (5+ years)
  3. Team Expertise: Team has or can acquire skills
  4. Performance: Meets non-functional requirements
  5. Cost: Within budget constraints
  6. Security: Meets security standards
  7. Compliance: Meets regulatory requirements

Architecture Design Responsibilities

Component Design

  • Identify system components and their responsibilities
  • Define component boundaries and interfaces
  • Design data models and schemas
  • Plan API contracts and integration points

Technical Risk Assessment

  • Identify technical risks early in planning
  • Assess risk severity and likelihood
  • Propose mitigation strategies
  • Track risks through implementation

Dependency Analysis

  • Evaluate external dependencies and libraries
  • Assess version compatibility and conflicts
  • Identify security vulnerabilities in dependencies
  • Plan dependency update strategy

Read the full file on GitHub · 134 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. 2d ago First seen · 134 lines · 0 tokens per session scan A b4b6fed0a65f

Subscribe to this mod's changes

architect is an agent published in the GitHub repository keychain-io/trustable-ai (2 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 865 tokens. 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.