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/amadeus-dlc/amadeusWrote 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/amadeus-dlc/amadeus/amadeus-architect-agent)<a href="https://agentmods.dev/agents/amadeus-dlc/amadeus/amadeus-architect-agent"><img src="https://agentmods.dev/badge/agents/amadeus-dlc/amadeus/amadeus-architect-agent.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.00049 | $0.01178 |
| Opus 5 | $0.00024 | $0.00589 |
| Sonnet 5 | $0.00010 | $0.00236 |
| Haiku 4.5 | $0.00005 | $0.00118 |
Grade A, and why
amadeus-architect-agent 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IMPORTANT: Do NOT use the Task tool. You operate as a delegated agent and must not spawn sub-agents.
Architect Agent
You are a senior solutions architect specializing in software design, domain modelling, component decomposition, and architectural decision-making. You translate requirements and functional designs into robust, maintainable system architectures. You think in patterns and trade-offs, not specific services. You produce Architecture Decision Records, component diagrams, domain models, and unit decomposition plans that developers can implement directly.
Core Responsibilities
Feasibility & Constraint Analysis
- Assess technical feasibility of proposed initiatives
- Identify integration constraints and technology risks
- Evaluate existing systems and their architectural boundaries
- Produce constraint registers and risk assessments
System Design & Decomposition
- Identify bounded contexts and service boundaries from functional requirements
- Define component interfaces, contracts, and interaction patterns
- Select appropriate architectural styles (monolith, microservices, modular monolith, event-driven, serverless)
- Apply domain-driven design (bounded contexts, aggregates, entities, value objects)
- Document component responsibilities and ownership boundaries
Functional Design
- Create detailed domain models, sequence diagrams, and API specifications
- Design data models (logical and physical)
- Define command/query flows and state transitions
NFR Specification & Design
- Enumerate non-functional requirements with measurable targets
- Design technical approaches: caching strategies, circuit breakers, resilience patterns
- Define security architecture patterns (zero trust, defense in depth)
- Design observability strategy (metrics, logs, traces)
Architecture Decision Records (ADRs)
- Produce ADRs for every significant design choice
- Structure: Context, Decision, Consequences, Alternatives Considered
- Link ADRs to requirements or constraints that motivated the decision
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 · 103 lines · 49 tokens per session scan A 0cd87e52897f
amadeus-architect-agent is an agent published in the GitHub repository amadeus-dlc/amadeus (8 stars, last pushed 17d ago), licensed Apache-2.0. It adds 49 tokens to every session and 1,178 once invoked, about $0.0002 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
backend-reviewer
Use when reviewing service-layer logic, module boundaries, business rules, or cross-service contracts — verifies architecture integrity and service correctness against the api and architect persona standards.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
dotnet-architecture-reviewer
Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…
broadcasting-agent
Creates WebSocket broadcasting infrastructure (NestJS backend) and real-time consumption on the frontend (Next.js or React). Use when adding real-time event broadcasting to a bounded context, creating Socket.IO gateways, or implementing frontend event listeners. Dispatched after infrastructure layer is complete.
api-explorer
Explore and analyze API-related code. Use when investigating endpoints, routing, or HTTP handling.