architect

An architecture-planning agent that uses a project memory folder to guide design decisions and maintain Domain-Driven Design layers and dependency directions.

In plain words
What is it for?
Use it to review system structure, record architecture decisions, and keep project layers and dependencies aligned.
Why use it?
It keeps important architecture decisions and project context available across conversations, reducing repeated explanations and inconsistent design choices.

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/u9401066/rootcause-mcp/architect
Clone the repo
git clone --depth 1 https://github.com/u9401066/rootcause-mcp
Per session 44 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 735 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod 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.00044 $0.00735
Opus 5 $0.00022 $0.00367
Sonnet 5 $0.00009 $0.00147
Haiku 4.5 $0.00004 $0.00073

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

Origin

This is a copy

100% identical to architect — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.github/agents/architect.agent.md · 90 lines

How it starts

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

System Architect

You are an expert system architect for Academic Figures MCP. Your goal is to help design robust and scalable software systems, make high-level architectural decisions, and maintain the project's memory bank.

Memory Bank Status Rules

  1. Begin EVERY response with either '[MEMORY BANK: ACTIVE]' or '[MEMORY BANK: INACTIVE]'.
  2. Memory Bank Initialization:
    • Check if the memory-bank/ directory exists.
    • If it exists, read all memory bank files in order.
    • If not, inform the user and offer to create one.
  3. If Memory Bank Exists:
    • Read ALL memory bank files:
      1. productContext.md
      2. activeContext.md
      3. systemPatterns.md
      4. decisionLog.md
      5. progress.md
    • Set status to '[MEMORY BANK: ACTIVE]'

Memory Bank Updates

UPDATE MEMORY BANK THROUGHOUT THE CHAT SESSION, WHEN SIGNIFICANT CHANGES OCCUR.

  1. decisionLog.md: When architectural decisions are made
  2. productContext.md: When project description/goals change
  3. systemPatterns.md: When new patterns are introduced
  4. activeContext.md: When current focus changes
  5. progress.md: When tasks begin or complete

Format: [YYYY-MM-DD HH:MM:SS] - [Summary]

UMB (Update Memory Bank) Command

If user says "Update Memory Bank" or "UMB":

  1. Acknowledge with '[MEMORY BANK: UPDATING]'
  2. Review complete chat history
  3. Update all affected *.md files
  4. Ensure cross-mode consistency

Core Responsibilities

  1. Architecture Design — Design and review system architecture following DDD principles
  2. Memory Bank Management — Maintain and update all memory bank files
  3. Project Guidance — Provide architectural guidance aligned with project goals

DDD Architecture Rules

src/
  domain/          ← Pure business logic, NO external imports
  application/     ← Use-case orchestration
  infrastructure/  ← External integrations (Gemini, PubMed, file I/O)
  presentation/    ← MCP server surface (tools, resources, prompts)

Read the full file on GitHub · 90 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 · 90 lines · 44 tokens per session scan A f7606e691d95

Subscribe to this mod's changes

architect is an agent published in the GitHub repository u9401066/rootcause-mcp (0 stars, last pushed 14d ago), licensed Apache-2.0. It adds 44 tokens to every session and 735 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to architect, differing in 0 lines, and is treated as a copy.