architecture-explainer Claude Code subagentA
architecture-explainer from alexisbalayre/claude-code-config is a Claude Code subagent: a helper Claude Code hands a task to, with its own instructions.
mdr add alexisbalayre/claude-code-config/.claude/agents/architecture-explainer.md@git:20260917.a589e3fPins git:20260917.a589e3f in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- Claude Code subagent
- Repository
- alexisbalayre/claude-code-config
- Path
.claude/agents/architecture-explainer.md- Versions recorded
- 3
- Latest version
- git:20260917.a589e3f, committed Sep 17, 2026
- First version recorded
- May 23, 2026
- Size
- 4,196 bytes
- Repository stars
- 3
- License
- MIT
Use PROACTIVELY when the user asks why or how about the system architecture — component boundaries, data flow, request or job lifecycle, external dependencies, scaling, data-model decisions, auth model, or cross-component interactions. MUST BE USED before answering architecture questions instead of re-reading docs in the main context. Grounds answers in `docs/reference/architecture.md`, `docs/explanation/` (rationale), `docs/adr/` (decisions), `docs/glossary.md`, and the code.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Architecture Explainer Answer architecture questions about this project grounded in its documentation. Do NOT invent architecture. Every claim must trace to a file in `docs/reference/`, `docs/explanation/`, `docs/adr/`, `docs/conventions/`, `docs/glossary.md`, 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/architecture.md` for the topology, then drill down. | Question pattern | Primary doc | Cross-reference | | :---------------------------------------------------------------- | :------------------------------------------- | :--------------------------------------- | | Component split, layout, topology | `docs/reference/architecture.md` | `docs/explanation/` | | "Why X over Y?" / a past technical choice | `docs/adr/` (accepted ADRs) | `docs/explanation/` | …
Read the whole file at its exact version.
How to install
mdr add alexisbalayre/claude-code-config/.claude/agents/architecture-explainer.md@sha256:97570388f24a44baThe line at the top of this page pins the label git:20260917.a589e3f, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_5p6tkqarn7zvf4bm)
1 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in alexisbalayre/claude-code-config/.claude/agents/architecture-explainer.md since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of architecture-explainer.md from somewhere else? Ask it: where did my architecture-explainer.md come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 3 versions of this file, between May 23, 2026 and Sep 17, 2026, about one every 59 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260917.a589e3f latest | 2026-09-17 | a589e3f | 4,196 B | A | view · diff |
| git:20260811.6af4418 | 2026-08-11 | 6af4418 | 4,148 B | A | view · diff |
| git:20260523.36e5a7e | 2026-05-23 | 36e5a7e | 4,144 B | A | view |
Installed this file, say at architecture-explainer.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (4196 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
alexisbalayre/claude-code-config · 3 stars · license MIT · pushed 2026-11-17 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_5p6tkqarn7zvf4bm GET https://markdownregistry.com/api/v1/resolve?ref=alexisbalayre/claude-code-config/.claude/agents/architecture-explainer.md GET https://markdownregistry.com/api/v1/blob/97570388f24a44ba38d44f6b91b4e9d59d616e8a8b858e2c065d2f93101777b8
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: which agent file does what.