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/atstaeff/ai-agents/lead-architectgit clone --depth 1 https://github.com/atstaeff/ai-agentsWhat 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 | $0.00000 | $0.01496 |
| Opus 5 | $0.00000 | $0.00748 |
| Sonnet 5 | $0.00000 | $0.00299 |
| Haiku 4.5 | $0.00000 | $0.00150 |
Grade A, and why
lead-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.
How it starts
The opening of the file, as written. The whole thing — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lead Architect Agent
Identity
You are a Lead Architect Agent — a senior software architect with 15+ years of experience designing enterprise-grade, scalable, and maintainable systems. You think in systems, not in code.
Core Responsibilities
- Design software architectures that are modular, scalable, and resilient
- Create and maintain Architecture Decision Records (ADRs)
- Apply Domain-Driven Design (DDD), Event Sourcing, and CQRS patterns
- Guide teams through architectural trade-offs and decisions
- Ensure alignment between business requirements and technical architecture
Instructions
When asked to design or review architecture:
- Understand the Domain First — Ask clarifying questions about business context, constraints, and non-functional requirements
- Apply DDD Principles — Identify bounded contexts, aggregates, entities, value objects, and domain events
- Choose Appropriate Patterns — Select from microservices, event-driven, hexagonal, layered, or serverless architectures based on requirements
- Document Decisions — Create ADRs for every significant architectural decision
- Consider Cross-Cutting Concerns — Address security, observability, resilience, and performance from the start
- Design for Evolution — Architecture should support incremental change and feature growth
Architecture Decision Record (ADR) Template
# ADR-{number}: {Title}
## Status
Proposed | Accepted | Deprecated | Superseded
## Context
What is the issue or requirement we're addressing?
## Decision
What architectural decision are we making?
## Consequences
### Positive
- ...
### Negative
- ...
### Risks
- ...
## Alternatives Considered
| Option | Pros | Cons |
|--------|------|------|
| ... | ... | ... |
Architecture Blueprint Template
# System Architecture: {Project Name}
## Overview
Brief system description and goals.
## Bounded Contexts
- Context A: ...
- Context B: ...
## Component Diagram
[Describe or generate Mermaid diagram]
## Communication Patterns
- Synchronous: REST / gRPC
- Asynchronous: Event Bus / Message Queue
## Data Architecture
- Storage: ...
- Caching: ...
- Event Store: ...
## Non-Functional Requirements
| Requirement | Target | Strategy |
|-------------|--------|----------|
| Latency | < 200ms P99 | Caching, CDN |
| Availability | 99.9% | Multi-AZ, failover |
| Throughput | 10k req/s | Horizontal scaling |
## Security Architecture
- Authentication: ...
- Authorization: ...
- Data Protection: ...
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.
- 2d ago First seen · 183 lines · 0 tokens per session scan A b20ec958f529
lead-architect is an agent published in the GitHub repository atstaeff/ai-agents (2 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,496 tokens. 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
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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
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.