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/amadeus-dlc/amadeus/architect-agent.jagit 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/architect-agent.ja)<a href="https://agentmods.dev/agents/amadeus-dlc/amadeus/architect-agent.ja"><img src="https://agentmods.dev/badge/agents/amadeus-dlc/amadeus/architect-agent.ja.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.00000 | $0.01189 |
| Opus 5 | $0.00000 | $0.00594 |
| Sonnet 5 | $0.00000 | $0.00238 |
| Haiku 4.5 | $0.00000 | $0.00119 |
Grade A, and why
architect-agent.ja 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 5d 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architect Agent
言語: English | 日本語
エージェント詳細解説 · ユーザーガイド › エージェント › 詳細解説 · 技術リファレンス: architect-agent
amadeus-architect-agent はソリューションアーキテクトです。要件を堅牢なシステムアーキテクチャへ翻訳し、Architecture Decision Records(ADR)を作成し、ドメインモデルを設計し、プロジェクトを実装可能な作業単位へ分解します。パターンとトレードオフの観点で思考し、開発者が直接実装できる設計を生み出します。
amadeus-architect-agent は、ライフサイクル内で単一エージェントとして最も多くのステージ — 合計 6 つ — をリードし、Ideation、Inception、Construction にまたがります。主たる設計権限であり、他の 7 つの高い判断力を要するエージェントとともに Opus モデルで動作します。delivery、pipeline-deploy、operations の 3 つだけが Sonnet で動作しますが、それはこれらの出力が主にテンプレートベースだからです。
リードするステージ
| ステージ | フェーズ | 説明 |
|---|---|---|
| 1.3 Feasibility & Constraints | Ideation | 技術的実現可能性の評価と制約分析 |
| 2.6 Application Design | Inception | コンポーネント設計、API 契約、ADR |
| 2.7 Units Generation | Inception | 設計を実装可能な作業単位へ分解 |
| 3.1 Functional Design | Construction | 詳細なドメインモデルとビジネスロジック(ユニット単位) |
| 3.2 NFR Requirements | Construction | 測定可能な目標値を伴う非機能要件(ユニット単位) |
| 3.3 NFR Design | Construction | キャッシング、レジリエンス、セキュリティの技術的アプローチ(ユニット単位) |
さらに、ステージ 2.1(Reverse Engineering)の統合ステップもリードします。ここでは amadeus-developer-agent からコードスキャン結果を受け取り、9 つのアーキテクチャ成果物を生成します。
サポートするステージ
| ステージ | フェーズ | 貢献 |
|---|---|---|
| 1.1 Intent Capture | Ideation | 技術的コンテキストの提供 |
| 2.1 Reverse Engineering(統合ステップ) | Inception | コードスキャン結果を一貫したアーキテクチャモデルへ統合 |
| 2.8 Delivery Planning | Inception | アーキテクチャの依存関係に照らしてビルド順序を検証 |
期待できること
amadeus-architect-agent がアクティブなとき、境界、パターン、トレードオフに焦点を当てます。既存システムの制約、技術の選好、スケーラビリティ要件、運用上の懸念について問いかけます。明示的な意思決定の根拠を伴う構造化された設計ドキュメント、markdown で記述されたコンポーネント図、そして重要な選択ごとの ADR を生成します。
協働の仕方
amadeus-architect-agent は amadeus-product-agent から要件を、amadeus-developer-agent からコードスキャン結果を受け取ります。AWS サービスマッピングでは amadeus-aws-platform-agent と、セキュア設計では amadeus-devsecops-agent と、規制上の制約では amadeus-compliance-agent と協働します。その出力(ユニット仕様、API 契約、NFR 目標値)は amadeus-developer-agent、amadeus-quality-agent、amadeus-aws-platform-agent によって消費されます。
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.
- 5d ago First seen · 48 lines · 0 tokens per session scan A f38534cb37d0
architect-agent.ja is an agent published in the GitHub repository amadeus-dlc/amadeus (8 stars, last pushed 14d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,189 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
requirements-analyst
Use this agent when decomposing, analyzing, and validating requirements across the SDD workflow. Specializes in requirements engineering, traceability analysis, coverage mapping, and quality validation - focuses on requirements methodology rather than code implementation.
traceability-auditor
Use this agent to verify cross-layer traceability and project-wide document integrity across the SDD flow. A READ-ONLY mechanical gate: it runs the traceability/validation tooling and reports gaps, broken links, ID/naming violations, and orphaned artifacts. It reports only — it does not fix. A downstream-heavy role…
OWL-IMPLEMENTATION
Status: ✅ Implemented Script: scripts/owl.py Wrapper: scripts/owl.
owl-of-athena
Archive management agent for Athena. Handles athena-index.md maintenance, archived feature retrieval, search, and progress pruning. Dispatch when user asks about archived features, wants to search history, or a feature completes.
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.