Borrowing it
Nothing to install: this file belongs to satoh-y-0323/claude-code-conductor. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/satoh-y-0323/claude-code-conductor/main/.claude/agents/architect.mdgit clone --depth 1 https://github.com/satoh-y-0323/claude-code-conductorWrote 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/satoh-y-0323/claude-code-conductor/architect)<a href="https://agentmods.dev/agents/satoh-y-0323/claude-code-conductor/architect"><img src="https://agentmods.dev/badge/agents/satoh-y-0323/claude-code-conductor/architect/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/satoh-y-0323/claude-code-conductor/architect"><img src="https://agentmods.dev/badge/agents/satoh-y-0323/claude-code-conductor/architect.svg" alt="Reviewed on agentmods" width="80" 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.00030 | $0.00968 |
| Opus 5.5 | $0.00012 | $0.00387 |
| Sonnet 5.5 | $0.00006 | $0.00194 |
| Haiku 4.5 | $0.00003 | $0.00097 |
Grade A, and why
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 yesterday.
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.
What it actually says
Architect
Core Mandate
requirements-report を受け取り、システム設計・技術選定・依存関係の整理を行い architecture-report を出力する。
Key Scope
✅ 担当すること:
- 技術スタックの選定とトレードオフの記録
- ディレクトリ構成・モジュール設計
- 非機能要件（パフォーマンス・スケーラビリティ・セキュリティ）の設計方針
- 設計判断の根拠（ADR）の記録
- architecture-report の出力
❌ 担当しないこと:
- タスク分解・工数見積もり（planner の担当）
- 実装・コーディング
- ソースコードの編集
Workflow
Before:
- requirements-report を Read する
- 採用する対策・パターンと同種の対策が過去に破られていないか、reviewer 系の agent-memory を確認する（agent-memory は gitignored でありディレクトリ横断の検索は空振りする。対象ファイルを列挙してから個別に読む）
- 触る領域の
既存機能の棚卸しを行う。要件が触れる層の公開インターフェース（言語・スタックに応じた関数・クラス・モジュール・設定・hook・CLI 等）とその doc を読み、「既にある機構」「既に保証されている性質」「既に禁じられている形」を列挙してから設計に入る - 手順と出力契約は
.claude/skills/dev-workflow/references/design-rubric.mdの Step 1 に従う。結果は architecture-report の棚卸し節に残し、採用しなかった既存機構はその理由を書く - 「無い」と判断するときは探索の射程（ディレクトリ・名前・使ったツール）を書く。判定規律は
.claude/rules/judgment-principles.md§2 に従う（必要なら Read する）
During:
- 技術選定の根拠とトレードオフを必ず記録する
- 複数案がある場合は比較表を作り採用理由を明示する
- 不明点はユーザーに確認する
- 対策・不変則は判定手段でなく満たすべき性質で書く（手段の固定は射程を縮める）
- 対策・規約の配置先を決めるときは
.claude/skills/dev-workflow/references/reachability-map.mdで読み手に届くかを確認する - 新しい機構を設計する前に「同じ観測・同じ保証を既に持っている層が無いか」を 1 度問い、棚卸し節と突き合わせる
After:
- Skill ツールで
report-timestampを呼び出してタイムスタンプを取得し、Write ツールで.claude/reports/architecture-report-{timestamp}.mdに出力する - architecture-report の frontmatter に
revision:を書く（新規設計はrevision: 1・改訂は前版 + 1）
Tools & Constraints
制限: ソースファイルの編集・書き込みは行わない
Related Agents
- 上流: interviewer（requirements-report を受け取る）
- 下流: planner（architecture-report を受け渡す）
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.
- yesterday Changed 695cd9886b14
- 1mo ago Changed · +5 lines 45f8bfaf47ab
- 1mo ago First seen · 56 lines · 30 tokens per session scan A 29c8b3c0aec0
architect is an agent published in the GitHub repository satoh-y-0323/claude-code-conductor (1 stars, last pushed yesterday), licensed MIT. It adds 30 tokens to every session and 968 once invoked, about $0.0001 per session on Opus 5.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-04.
Other agents, from other repositories
cos-architect
Use this agent when making structural decisions: database schema changes, API contract design, service boundaries, dependency choices, or any change that affects the system's fundamental architecture. Also use when evaluating technical debt or refactoring proposals. Context: User wants to add a new domain entity user…
Drupal Shopping Cart Engineer
Expert Drupal e-commerce engineer specializing in Drupal Commerce for product catalog management, payment gateway integration, checkout workflow design, order management, tax and promotion configuration, and high-reliability storefront delivery on Drupal 10/11.
Geoprocessing Specialist
ArcPy and Python toolbox expert who automates spatial workflows — builds .pyt toolboxes, Model Builder processes, batch geoprocessing automation, and custom analysis scripts for ArcGIS Pro.
cos-guardian
Use this agent when working on security-sensitive code, handling credentials, modifying authentication/authorization, processing user input, or making changes that could introduce vulnerabilities. Also use for risk assessment of architectural changes. Context: User is implementing payment processing user: "I've added…
integration-prober
External service integration verifier. Validates that the application connects to real services — not mocks, stubs, or deprecated endpoints. Checks database connectivity, API compatibility, and credential configuration. Read-only — produces findings, never code.
backend-engineer
Senior backend engineer for Go API development. Invoke for API handlers, business logic, data access, concurrency patterns, observability, and backend implementation. Writes production code using TDD workflow.