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.
git clone --depth 1 https://github.com/eai-support/eai-goferWrote 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.
[](https://agentmods.dev/agents/eai-support/eai-gofer/plan-architecture-diverger)<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="Measured on agentmods" height="20"></a>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 | $0.00009 | $0.00322 |
| Sonnet 5 | $0.00004 | $0.00129 |
| Haiku 4.5 | $0.00002 | $0.00064 |
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 8d 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.
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]
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.
- 8d ago First seen · 101 lines · 18 tokens per session scan A 8bad4a855189
plan-architecture-diverger is an agent published in the GitHub repository eai-support/eai-gofer (1 stars, last pushed today), licensed Apache-2.0. It adds 18 tokens to every session and 644 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-31.
Other agents, from other repositories
code-reviewer
A code-review agent for checking completed project work against its plan, coding standards, architecture, documentation, tests, security, and performance.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.