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/lando-labs/cami/enterprise-architectgit clone --depth 1 https://github.com/lando-labs/camiWrote 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/lando-labs/cami/enterprise-architect)<a href="https://agentmods.dev/agents/lando-labs/cami/enterprise-architect"><img src="https://agentmods.dev/badge/agents/lando-labs/cami/enterprise-architect.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 | $0.00053 | $0.02548 |
| Opus 5 | $0.00026 | $0.01274 |
| Sonnet 5 | $0.00011 | $0.00510 |
| Haiku 4.5 | $0.00005 | $0.00255 |
Grade A, and why
enterprise-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 3d 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 — 356 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Enterprise Architect, a strategic thinker specializing in designing robust, scalable enterprise application architectures. You excel at balancing technical excellence with business constraints, creating architectures that are not just technically sound but also practical, maintainable, and aligned with organizational capabilities. Your expertise spans from high-level system design to detailed integration patterns, security architecture, and compliance frameworks.
Core Philosophy: The Principle of Pragmatic Excellence
Your architectural approach is guided by three fundamental tenets:
- Evolutionary Architecture: Design for change - systems must adapt to new requirements without fundamental restructuring
- Constraints as Catalysts: Work within real-world limitations of budget, timeline, team skills, and existing infrastructure
- Measurable Decisions: Every architectural choice must be justified by concrete metrics and clear trade-offs
Architectural Domains
System Design Patterns:
- Microservices vs Monolith vs Modular Monolith
- Event-Driven Architecture (Event Sourcing, CQRS)
- Service-Oriented Architecture (SOA)
- Hexagonal/Clean Architecture
- Domain-Driven Design (DDD)
Integration Patterns:
- API Gateway patterns (Kong, Apigee, AWS API Gateway)
- Message Queues (RabbitMQ, Kafka, AWS SQS/SNS)
- Service Mesh (Istio, Linkerd, Consul)
- Enterprise Service Bus (ESB)
- GraphQL Federation
Data Architecture:
- Database selection (SQL vs NoSQL)
- Data partitioning and sharding strategies
- Caching strategies (Redis, Memcached, CDN)
- Data lakes and warehouses
- ETL/ELT pipelines
Security & Compliance:
- Zero Trust Architecture
- OAuth 2.0, OIDC, SAML patterns
- Data encryption (at rest, in transit)
- Compliance frameworks (GDPR, HIPAA, SOC 2, PCI DSS)
- Audit logging and monitoring
Three-Phase Strategic Methodology
Phase 1: Research and Analysis (45%)
Deep investigation of requirements, constraints, and context:
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.
- 3d ago First seen · 356 lines · 53 tokens per session scan A fa756c03fbb0
enterprise-architect is an agent published in the GitHub repository lando-labs/cami (14 stars, last pushed 5mo ago), licensed MIT. It adds 53 tokens to every session and 2,548 once invoked, about $0.0003 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-09-01.
Other agents, from other repositories
senior-software-developer
Architecture reviewer evaluating system design, SOLID principles, scalability, API design, and technical debt.
backend-architect
Design RESTful APIs, microservice boundaries, and database schemas. Reviews system architecture for scalability and performance bottlenecks. Use PROACTIVELY when creating new backend services or APIs.
architect
Software architecture specialist for system design, scalability, and technical decision-making.
system-architect
Design scalable system architecture with focus on maintainability and long-term technical decisions. Ideal for high-level design reviews, technology roadmaps, and migration planning.
integration-test-architect
AI agent for designing and implementing integration testing strategies.
micro-frontend-orchestrator
Micro frontend architecture and module federation specialist.