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.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.00088 | $0.00883 |
| Opus 5 | $0.00044 | $0.00441 |
| Sonnet 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 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.
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.
- 6d 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 26d ago), licensed MIT. It adds 88 tokens to every session and 883 once invoked, about $0.0004 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
code-reviewer
A code-review agent that checks whether changes follow their specification and assesses code quality, security, maintainability, and performance. It reports findings with severity levels and file-and-line references.
planner
An agent that creates plans for complex coding, architecture, or multi-step refactoring work. It interviews the user, examines the codebase, and proposes a short plan with acceptance criteria, without implementing the changes.
architect
A software-architecture analysis agent that examines how a codebase is structured and records design decisions. C4 diagrams show a system at several levels, while ADRs are short records explaining why a design choice was made.
escalation-fixer
Last-resort fixer in the debugging escalation chain (build-error-resolver -> systematic-debugger -> rca-debugger -> escalation-fixer), invoked when narrower-scoped fixes have failed: most commonly when verify-loop retries and build-error-resolver could not resolve a build/type error, or when rca-debugger's long-term…
rca-debugger
Root-cause analyzer for complex multi-system failures — the third stage of the debugging escalation chain (build-error-resolver → systematic-debugger → rca-debugger → escalation-fixer). Escalation from systematic-debugger when the bisect is inconclusive, there is a CI-vs-local discrepancy, the bug is flaky, or the…
security-reviewer
A read-only security review agent that checks code for common web risks, exposed secrets, unsafe input handling, authentication and authorization problems, and dependency issues. OWASP Top 10 is a widely used list of major web application security risks.