Borrowing it
Nothing to install: this file belongs to Langerrr/distributed-architect. 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/Langerrr/distributed-architect/main/CLAUDE.mdgit clone --depth 1 https://github.com/Langerrr/distributed-architectWrote 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/instructions/langerrr/distributed-architect/claude-md)<a href="https://agentmods.dev/instructions/langerrr/distributed-architect/claude-md"><img src="https://agentmods.dev/badge/instructions/langerrr/distributed-architect/claude-md/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/instructions/langerrr/distributed-architect/claude-md"><img src="https://agentmods.dev/badge/instructions/langerrr/distributed-architect/claude-md.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.01207 | $0.01207 |
| Opus 5.5 | $0.00483 | $0.00483 |
| Sonnet 5.5 | $0.00241 | $0.00241 |
| Haiku 4.5 | $0.00121 | $0.00121 |
Grade A, and why
distributed-architect CLAUDE.md 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 1mo 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
distributed-architect — Distributed Systems Reasoning Plugin
A reasoning framework that helps LLMs analyze distributed system changes for correctness. Not a documentation system — a structured thinking process.
Boundary Signal Reference
Claude Code doesn't load an installed plugin's CLAUDE.md into every session, so this table isn't automatic — it's the reference the skills below read from. Two ways to use it:
- Per-project, always on:
@-import this file (or just this section) from a project's ownCLAUDE.md. - On demand: run
/dist-check,/dist-debug, or/dist-designdirectly.
When working on a distributed system (multiple independently-deployed processes, services, or storage systems communicating), watch for these signals before writing code:
| Signal | You are... | Module |
|---|---|---|
| Changing state/status that another actor (process, human, or AI agent) reads or reacts to | state-mutation |
${CLAUDE_PLUGIN_ROOT}/modules/state-mutation.md |
| Moving data across a serialization, network, or storage boundary | data-lifecycle |
${CLAUDE_PLUGIN_ROOT}/modules/data-lifecycle.md |
| Writing error/retry/timeout handling for cross-component operations | failure-mode |
${CLAUDE_PLUGIN_ROOT}/modules/failure-mode.md |
| Adding a new message type, API call, or event between components | interaction |
${CLAUDE_PLUGIN_ROOT}/modules/interaction.md |
Concurrency signal: Check the project topology file. If the component you're modifying is on the "1" side of a 1:N relationship, also load ${CLAUDE_PLUGIN_ROOT}/modules/concurrency.md.
Procedure: Detect signal → read the relevant module → walk its checklist → if topology shows 1:N, run concurrency pass → flag concerns before writing code. No overhead for single-component changes.
Skills
| Command | Phase | Purpose |
|---|---|---|
/dist-check |
Coding | Two-pass boundary + concurrency analysis on code changes |
/dist-design |
Design | Architecture trade-off analysis for distributed decisions |
/dist-debug |
Debug | Backward root-cause tracing from symptoms to cause boundary |
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.
- 1mo ago Changed · +4 lines · +182 tokens per session 46cc889f62dd
- 2mo ago First seen · 98 lines · 1,025 tokens per session scan A 99750e3ed7c0
distributed-architect CLAUDE.md is an instructions file published in the GitHub repository Langerrr/distributed-architect (1 stars, last pushed 1mo ago), licensed MIT. It adds 1,207 tokens to every session, about $0.0048 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.