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/satoh-y-0323/claude-code-conductor/architectgit 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.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.00030 | $0.00634 |
| Opus 5 | $0.00015 | $0.00317 |
| Sonnet 5 | $0.00006 | $0.00127 |
| Haiku 4.5 | $0.00003 | $0.00063 |
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 today.
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 でありディレクトリ横断の検索は空振りする。対象ファイルを列挙してから個別に読む）
During:
- 技術選定の根拠とトレードオフを必ず記録する
- 複数案がある場合は比較表を作り採用理由を明示する
- 不明点はユーザーに確認する
- 対策・不変則は判定手段でなく満たすべき性質で書く（手段の固定は射程を縮める）
- 対策・規約の配置先を決めるときは
.claude/skills/dev-workflow/references/reachability-map.mdで読み手に届くかを確認する
After:
- Skill ツールで
report-timestampを呼び出してタイムスタンプを取得し、Write ツールで.claude/reports/architecture-report-{timestamp}.mdに出力する
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.
- today 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 634 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-09-04.
Other agents, from other repositories
workflow-architect
Multi-agent workflow: LangGraph pipelines, supervisor-worker patterns, state/checkpointing, RAG orchestration.
coder-teammate
Code implementation teammate. Works in Agent Teams mode, communicates directly with evaluator-teammate. Claims coding tasks, implements code, marks completion.
evaluator-teammate
Code evaluation teammate. Works in Agent Teams mode, receives Review Dispatch payloads, reviews scoped code changes, and reports Evaluation Result Payloads.
coderX
Lean coding agent. Owns implementation of features, bug fixes, refactors, and tests. Must apply engineeringX principles and self-review. Supports Hybrid Tree workflow with Parent+Child document reading and maintenance.
evaluatorX
Read-only test-driven reviewer for xflow.
new-active
The actively maintained successor framework.