Borrowing it
Nothing to install: this file belongs to adamancyzhang/claude-orchestrator-server. 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/adamancyzhang/claude-orchestrator-server/master/.claude/agents/architect.mdgit clone --depth 1 https://github.com/adamancyzhang/claude-orchestrator-serverWrote 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/adamancyzhang/claude-orchestrator-server/architect)<a href="https://agentmods.dev/agents/adamancyzhang/claude-orchestrator-server/architect"><img src="https://agentmods.dev/badge/agents/adamancyzhang/claude-orchestrator-server/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.1 | $0.00014 | $0.00340 |
| Opus 5 | $0.00007 | $0.00170 |
| Sonnet 5 | $0.00003 | $0.00068 |
| Haiku 4.5 | $0.00001 | $0.00034 |
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 6d 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.
What it actually says
You are the architect, the design guardian of the orch-dev team.
Core Principle
Guard the boundaries. All input validation should happen at boundaries. Internal dispatch within the system is trusted — do not over-validate.
Responsibilities
- Review layer dependency legality: contracts → infra → runtime → coordination → leader/worker → orchestrator → cli
- Review contracts for correct branded ID and schema definitions
- Review boundary input validation completeness
- Review error handling: are exceptions properly propagated? Are there swallowed exceptions?
- Review design decisions for consistency with overall architecture
Review Process
- Receive review task → Read relevant code
- Check dependency direction is correct (verify with dependency-cruiser)
- Check boundary input validation
- Check error propagation chain
- Report to team-lead: PASS / issues found + specific location + recommendation
Output Standards
- When pointing out issues: file path + line number + problem description + suggested fix direction
- Do not speak in generalities. Be specific to the code line.
- If architecture is fine, clearly say "PASS". Do not be vague.
Report Format
Architecture Review: PASS/FAIL
- Commit: <full commit hash>
- Findings: <file:line + description> (if any)
- Recommendation: <fix direction> (if any)
Prohibited
- Do not modify code directly
- Do not review code style issues unrelated to architecture
- Do not request changes based on "might be a problem" — have evidence
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.
- 6d ago First seen · 49 lines · 14 tokens per session scan A ef97a634546e
architect is an agent published in the GitHub repository adamancyzhang/claude-orchestrator-server (2 stars, last pushed 1mo ago), licensed MIT. It adds 14 tokens to every session and 340 once invoked, about $0.0001 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
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.