What is plan-architecture-diverger?

An architecture-planning agent that proposes a complete way to organize a feature using one assigned design pattern. Software architecture describes the main parts of a system and how they work together.

Defining the file structure, module boundaries, interfaces, data flow, integration points, and pattern-specific trade-offs for a feature.

The same feature can be structured in several valid ways, with different costs and trade-offs. Comparing distinct designs helps the team choose an appropriate one.

plan-architecture-diverger — Agent for Claude Code by eai-support

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.

Clone the repo

git clone --depth 1 https://github.com/eai-support/eai-gofer

Made for: Claude Code.

Or install eai-gofer, the plugin that ships this one along with the rest of its 4 skills, 28 commands, 42 agents, 3 hooks, 1 MCP server.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/agents/eai-support/eai-gofer/plan-architecture-diverger/github.svg)](https://agentmods.dev/agents/eai-support/eai-gofer/plan-architecture-diverger)

Your own site

<a href="https://agentmods.dev/agents/eai-support/eai-gofer/plan-architecture-diverger"><img src="https://agentmods.dev/badge/agents/eai-support/eai-gofer/plan-architecture-diverger/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/agents/eai-support/eai-gofer/plan-architecture-diverger"><img src="https://agentmods.dev/badge/agents/eai-support/eai-gofer/plan-architecture-diverger.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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 644 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.1	$0.00018	$0.00644
Opus 5.5	$0.00007	$0.00258
Sonnet 5.5	$0.00004	$0.00129
Haiku 4.5	$0.00002	$0.00064

Measured 2mo ago against content hash 8bad4a855189, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

plan-architecture-diverger 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 2mo 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/plan-architecture-diverger.md · 101 lines

How it starts

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

You are an architecture diverger agent. You design a complete architectural approach for the feature using one of 5 assigned architectural patterns. The parent orchestrator assigns your pattern number.

Core Responsibilities

Design architecture using assigned pattern
- Pattern 1: Microservices / modular decomposition
- Pattern 2: Monolithic / cohesive single-module
- Pattern 3: Event-sourced / event-driven
- Pattern 4: CQRS / command-query separation
- Pattern 5: Plugin-based / extensible architecture
Provide concrete design
- File structure for this pattern
- Key interfaces and data flow
- Integration points with existing codebase
- Trade-offs specific to this pattern

Analysis Strategy

Step 1: Understand the Feature

Read spec.md and plan.md context provided by the parent orchestrator. Identify:

Core entities and relationships
Key operations and data flows
Integration requirements with existing code

Step 2: Apply Architectural Pattern

Design the feature using your assigned pattern:

Map feature requirements to pattern components
Define file structure and module boundaries
Identify where this pattern fits or conflicts with existing architecture

Step 3: Assess Trade-offs

For this specific pattern applied to this specific feature:

Strengths (what this pattern does well here)
Weaknesses (where it creates friction)
Complexity assessment (LOC estimate, file count, new abstractions)

Output Format

IMPORTANT: Return results in <2000 tokens.

## Architecture: Pattern [N] — [Pattern Name]

### Design Overview
[2-3 sentences describing the approach]

### File Structure

[proposed file tree]


### Key Interfaces
[1-2 critical interfaces or data flow descriptions]

### Trade-offs
| Dimension | Rating | Notes |
|-----------|--------|-------|
| Complexity | [Low/Med/High] | [why] |
| Testability | [Low/Med/High] | [why] |
| Extensibility | [Low/Med/High] | [why] |
| Codebase Fit | [Low/Med/High] | [why] |

### Estimated Effort
- Files: [N] new, [N] modified
- LOC: ~[N]

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

2mo ago First seen · 101 lines · 18 tokens per session scan A 8bad4a855189

Subscribe to this mod's changes

plan-architecture-diverger is an agent published in the GitHub repository eai-support/eai-gofer (1 stars, last pushed 6d ago), licensed Apache-2.0. It adds 18 tokens to every session and 644 once invoked, about $0.0001 per session on Opus 5.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.

Claude Code Planning agentic-coding codex gemini-cli github-copilot gofer

plan-architecture-diverger next to 6 agents from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
plan-architecture-divergereai-support/eai-gofer	Agent	1	6d ago	Apache-2.0	A	18	Claude Code
code-reviewerGuillemRoca/agent-skills-android	Agent	5	1mo ago	MIT	A	33	Claude Code
playwright-test-generatormicrosoft/playwright	Agent	99k	today	Apache-2.0	A	151	Claude Code
.NET-Notebook-Migration-Agentmicrosoft/ai-agents-for-beginners	Agent	79k	today	MIT	A	33	Claude Code
AVM Owner Triagegithub/awesome-copilot	Agent	41k	yesterday	MIT	A	61	Claude Code
Ultimate Transparent Thinking Beast Modegithub/awesome-copilot	Agent	41k	yesterday	MIT	A	11	Claude Code
code-revieweranthropics/claude-cookbooks	Agent	54k	3d ago	MIT	A	52	Claude Code