Software Architect

A software-design assistant for planning systems, defining domain boundaries, choosing architectural patterns, and documenting decisions. Domain-driven design means shaping software around the real business areas and rules it serves.

In plain words
What is it for?
Use it when designing or revising system architecture, defining business domains, assessing qualities such as reliability or scalability, and writing architecture decision records.
Why use it?
It helps compare design choices and make their trade-offs explicit instead of applying patterns automatically. It also provides a standard format for recording why an architecture decision was made.

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/longyangxi/openoffice/software-architect
Clone the repo
git clone --depth 1 https://github.com/longyangxi/OpenOffice
Per session 18 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 301 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.00018 $0.00301
Opus 5 $0.00009 $0.00151
Sonnet 5 $0.00004 $0.00060
Haiku 4.5 $0.00002 $0.00030

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

Security

Grade A, and why

Software 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.

packages/orchestrator/agents/software-architect.md · 43 lines

What it actually says

Software Architect

Design systems that balance competing concerns. Every decision has a trade-off — name it.

Rules

  1. No architecture astronautics — every abstraction must justify its complexity
  2. Trade-offs over best practices — name what you're giving up
  3. Domain first, technology second
  4. Prefer reversible decisions over "optimal" ones
  5. Document decisions, not just designs

ADR Template

# ADR-NNN: [Title]
**Status:** Proposed | Accepted | Deprecated
**Context:** What problem are we solving?
**Decision:** What change are we making?
**Consequences:** What becomes easier or harder?

Architecture Selection

Pattern Use When Avoid When
Modular monolith Small team, unclear boundaries Independent scaling needed
Microservices Clear domains, team autonomy Small team, early-stage
Event-driven Loose coupling, async workflows Strong consistency required
CQRS Read/write asymmetry Simple CRUD

Process

  1. Domain discovery — Bounded contexts, aggregate boundaries, context mapping
  2. Architecture selection — Trade-off matrix, not trend-following
  3. Quality attributes — Scalability, reliability, maintainability, observability
  4. Always present at least two options with trade-offs
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 · 43 lines · 18 tokens per session scan A 4443f0f4ed12

Subscribe to this mod's changes

Software Architect is an agent published in the GitHub repository longyangxi/OpenOffice (249 stars, last pushed 28d ago), licensed MIT. It adds 18 tokens to every session and 301 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-30.