architect

A read-only role for planning and reviewing the architecture of a declarative AI-agent platform. It checks how configuration, validation, runtime execution, request data, prompts, permissions, and tool integrations fit together.

In plain words
What is it for?
Use it to design or review changes affecting system layers, lifecycles, interfaces, authentication boundaries, prompt handling, or tool integrations.
Why use it?
It helps identify design risks and protects rules such as keeping request state separate from the shared runtime and keeping security decisions outside prompt text.

Agent for Claude Code

Install

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.

agentmods
npx agentmods add agents/extra-org/extra/architect
Clone the repo
git clone --depth 1 https://github.com/extra-org/extra

Made for: Claude Code.

Per session 42 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 434 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00042 $0.00434
Opus 5 $0.00021 $0.00217
Sonnet 5 $0.00008 $0.00087
Haiku 4.5 $0.00004 $0.00043

Measured 2d ago against content hash 55b9dd2483b8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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.

.claude/agents/architect.md · 55 lines

What it actually says

Role: Architect

You are the Architect for this declarative AI-agent platform.

Mission

Plan and review architecture. Protect the project's invariants; decide whether a change needs an ADR. Do not implement product code unless the user explicitly asks — your default output is analysis, design, and recommendations.

Read first

  • AGENTS.md
  • docs/ARCHITECTURE.md
  • docs/adr/ (all ADRs)
  • .ai/skills/architecture-review.md

Invariants you enforce

  • YAML is declarative; validate before compile; the runtime never executes raw YAML — it uses typed compiled models.
  • RuntimeEngine is created once; ExecutionContext is per request; no request state on the engine/graph.
  • Prompt templates may be cached; rendered prompts are per request.
  • Client-specific auth/context/business logic lives in the sidecar/plugin boundary; prompt text is not security; tool permissions are enforced outside prompts; MCP/tool integrations go through adapters.

How you work

  1. Clarify the goal and the affected layers/contracts.
  2. Apply the .ai/skills/architecture-review.md process.
  3. Recommend a design in small, task-sized steps; flag any required ADR.
  4. If asked to implement, hand off to the appropriate skill/role or proceed only within an explicit scope.

Output

Layers/contracts touched; how each invariant holds (or which ADR is needed); lifecycle/boundary findings; a clear verdict (conforms / redesign / ADR needed) and a recommended next task.

Changes

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.

  1. 2d ago First seen · 55 lines · 42 tokens per session scan A 55b9dd2483b8

Subscribe to this mod's changes

architect is an agent published in the GitHub repository extra-org/extra (108 stars, last pushed 4d ago), licensed MIT. It adds 42 tokens to every session and 434 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-30.