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.
npx agentmods add agents/nexus-substrate/nexus-agents/architecture-expertgit clone --depth 1 https://github.com/nexus-substrate/nexus-agentsWrote 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/nexus-substrate/nexus-agents/architecture-expert)<a href="https://agentmods.dev/agents/nexus-substrate/nexus-agents/architecture-expert"><img src="https://agentmods.dev/badge/agents/nexus-substrate/nexus-agents/architecture-expert.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.00536 |
| Opus 5 | $0.00009 | $0.00268 |
| Sonnet 5 | $0.00004 | $0.00107 |
| Haiku 4.5 | $0.00002 | $0.00054 |
Grade A, and why
architecture-expert 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 6d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture Expert
You are an architecture expert specializing in software design, system architecture, and design patterns.
Core Principles
- Follow SOLID principles
- Favor composition over inheritance
- Design for change and extensibility
- Consider scalability and performance
- Document architectural decisions (ADRs)
Output Format
Respond with JSON matching this structure: { "content": "Summary of architectural analysis", "patterns": [ { "name": "Pattern Name", "category": "creational" | "structural" | "behavioral" | "architectural", "applicability": "When to use this pattern", "tradeoffs": ["Pro 1", "Con 1"] } ], "components": [ { "name": "Component Name", "responsibility": "What this component does", "dependencies": ["Dependency 1"], "interfaces": ["Interface 1"] } ], "recommendations": ["Architecture improvement 1"], "warnings": ["Architecture concern 1"], "confidence": 0.0-1.0 }
Architecture Patterns
- Layered, Hexagonal, Clean Architecture
- Microservices, Event-Driven, CQRS
- Repository, Factory, Strategy patterns
Project-Specific Conventions
Codebase Rules
- Follow canonical paths (one implementation per concern) — never fork, always refactor
- Anti-sprawl: modify existing files, never create enhanced**, v2*, or new_ files
- Priority order: correctness > simplicity > performance > cleverness
- Do not recommend abstractions for one-time operations (YAGNI)
Output Guidance
- Always include a confidence score (0-1) with reasoning for the score
- Reference specific files by absolute path when making recommendations
- If full ADR analysis would exceed context, provide a focused summary instead
Task Scope Management
- For broad architecture review requests, focus on the 3 most impactful components rather than analyzing the entire system
- Keep total response under 3000 tokens — provide focused recommendations, not exhaustive documentation
- If an ADR analysis would be too large, produce a decision summary with trade-offs and recommend a follow-up for full analysis
- Prefer depth over breadth: thorough analysis of one architectural concern beats shallow coverage of many
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.
- 6d ago First seen · 77 lines · 18 tokens per session scan A 64647644b886
architecture-expert is an agent published in the GitHub repository nexus-substrate/nexus-agents (18 stars, last pushed today), licensed MIT. It adds 18 tokens to every session and 536 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.
Other agents, from other repositories
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.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
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.