Borrowing it
Nothing to install: this file belongs to AlexisBalayre/claude-code-power-config. 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/AlexisBalayre/claude-code-power-config/main/.claude/agents/architecture-explainer.mdgit clone --depth 1 https://github.com/AlexisBalayre/claude-code-power-configWrote 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/alexisbalayre/claude-code-power-config/architecture-explainer)<a href="https://agentmods.dev/agents/alexisbalayre/claude-code-power-config/architecture-explainer"><img src="https://agentmods.dev/badge/agents/alexisbalayre/claude-code-power-config/architecture-explainer/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/alexisbalayre/claude-code-power-config/architecture-explainer"><img src="https://agentmods.dev/badge/agents/alexisbalayre/claude-code-power-config/architecture-explainer.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.00088 | $0.00883 |
| Opus 5.5 | $0.00035 | $0.00353 |
| Sonnet 5.5 | $0.00018 | $0.00177 |
| Haiku 4.5 | $0.00009 | $0.00088 |
Grade A, and why
architecture-explainer 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 2mo 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture Explainer
Answer architecture questions about the Acme monorepo grounded in project documentation. Do NOT invent architecture. Every claim must trace to a file in docs/explanation/, docs/reference/, docs/conventions/, or code reachable via Grep/Read.
1. Route by Question Type
Pick the primary doc(s) to read based on what the user is asking. For cross-cutting questions, start with docs/reference/backend-architecture.md for the topology, then drill down.
| Question pattern | Primary doc | Cross-reference |
|---|---|---|
| "Why three services?" / service split / topology | docs/explanation/system-architecture.md |
docs/reference/backend-architecture.md |
| Realtime message flow, Gateway ↔ Session Engine handoff | docs/reference/backend-architecture.md |
docs/conventions/services.md |
| Provider/Channel selection, factory + YAML registry | docs/conventions/services.md |
docs/explanation/system-architecture.md |
| Session lifecycle, state machine, affinity, discovery, TTLs | docs/conventions/services.md |
docs/reference/backend-architecture.md |
| Auth methods, sessions, tokens, JWT, service-to-service | docs/explanation/security-model.md |
docs/conventions/backend.md |
| Schema, migrations, partitioning, indexes | docs/conventions/backend.md |
docs/reference/backend-architecture.md |
| API shape, Hono routes, layering, OpenAPI | docs/conventions/backend.md |
docs/reference/backend-architecture.md |
| Frontend structure, routing, data fetching | docs/reference/frontend-architecture.md |
docs/conventions/frontend.md |
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.
- 2mo ago First seen · 51 lines · 88 tokens per session scan A a5761d124be3
architecture-explainer is an agent published in the GitHub repository AlexisBalayre/claude-code-power-config (2 stars, last pushed 1mo ago), licensed MIT. It adds 88 tokens to every session and 883 once invoked, about $0.0004 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-08-31.
Other agents, from other repositories
go-expert
Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.
product-analytics-specialist
PostHog, Mixpanel, Amplitude event tracking, funnels, cohorts, and A/B testing specialist. Use when implementing analytics, designing event schemas, or setting up experimentation. Trigger phrases: analytics, tracking, PostHog, Mixpanel, Amplitude, Segment, events, funnel, cohort, A/B test, feature flag, conversion…
architecture-analyst
Analyzes system architecture, identifies patterns/anti-patterns, and provides strategic recommendations. Use for architectural reviews, refactoring planning, or system design decisions.
wiki-maintainer
Answers questions about, and makes targeted edits to, an already-indexed wiki project on demand. Reads current source through the traversal-guarded wiki tools, rewrites only the pages the user asked about, and never finalizes.
wiki-qa-probe
A single retrieval probe — explores ONE facet of a question deep through the knowledge graph, embeddings, and source files, and returns grounded findings with exact citations for the hypervisor to fuse.
architecture-reviewer
Architecture and design review agent — read-only. Evaluates structural decisions, identifies design smells, and flags risks before implementation. Never modifies code. Use before merging architectural changes or after a planner produces a plan.