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.
npx agentmods add skills/langerrr/distributed-architect/dist-designnpx skills add Langerrr/distributed-architect --skill dist-designgit 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/skills/langerrr/distributed-architect/dist-design)<a href="https://agentmods.dev/skills/langerrr/distributed-architect/dist-design"><img src="https://agentmods.dev/badge/skills/langerrr/distributed-architect/dist-design.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 | $0.00095 | $0.00623 |
| Opus 5 | $0.00048 | $0.00311 |
| Sonnet 5 | $0.00019 | $0.00125 |
| Haiku 4.5 | $0.00010 | $0.00062 |
Grade A, and why
dist-design 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 today.
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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/dist-design — Design-Time Architecture Analysis
Evaluate architectural options and their trade-offs for distributed system decisions.
Arguments
$ARGUMENTSmay contain a description of what's being designed
Step 1: Gather Requirements
Understand from $ARGUMENTS or by asking the user:
- What problem does this solve?
- What are the constraints (latency, throughput, consistency, fault tolerance)?
- What components already exist? (load topology file if available)
Step 2: Load Project Topology
Look for a topology file. If it exists, understand the current system shape. If it doesn't, work with whatever architecture context is available.
Step 3: Identify the Design Decision
Categorize what's being decided:
| Decision type | Examples |
|---|---|
| Communication pattern | Stream vs queue vs RPC, push vs pull, sync vs async |
| Component boundary | Where to split responsibilities, same process vs separate |
| State management | Where state lives, who owns it, consistency model |
| Failure strategy | Retry policy, circuit breakers, fallback behavior, DLQ design |
| Scaling approach | Horizontal vs vertical, partitioning, sharding, replication |
Step 4: Enumerate Options
For each viable option, analyze:
a. Topology impact — What cardinality does it introduce? New convergence points? b. Failure analysis — What fails, blast radius, recovery mechanism? c. Concurrency implications — New concurrent access to shared resources? d. Operational cost — Complexity to operate, monitor, debug?
Step 5: Compare and Recommend
Present options side by side:
## Design Analysis: [decision description]
### Option A: [name]
- Topology: [impact]
- Failure modes: [key risks]
- Concurrency: [concerns]
- Operational cost: [assessment]
- Best when: [conditions where this option excels]
### Option B: [name]
- [same structure]
### Recommendation
[Which option and why, given the stated constraints]
### Topology Changes
[How the topology file should be updated if adopted]
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.
- today Changed · +2 lines · +68 tokens per session 8bfd64a8e8d5
- 4d ago First seen · 76 lines · 27 tokens per session scan A 0e28d6daf1b4
dist-design is a skill published in the GitHub repository Langerrr/distributed-architect (1 stars, last pushed 2d ago), licensed MIT. It adds 95 tokens to every session and 623 once invoked, about $0.0005 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 skills, from other repositories
feature-execution
This skill should be used when the user asks to "orchestrate the feature", "run the phases", "resume implementation", "continue the plan", "the phase agent died", "the agent stopped on its usage limit", "accept this phase", "can these phases run in parallel", "is this phase done", "does this shortfall matter", or…
acceptance-agent
Use this agent when a zforge phase has reported DONE and its evidence must be independently verified before the planner accepts it. Typical triggers include $zforge:feature-orchestrate accepting a REPORTED phase during a long chain, and any run where the planner's context is the constrained resource. It reconciles the…
phase-agent
Use this agent when a phase of a zforge feature plan is ready to implement and its work should run in its own context. Typical triggers include $zforge:feature-orchestrate spawning a READY phase, resuming a phase whose agent was interrupted mid-run, and re-running a phase after a decision was rejected in review. See…
retro
This skill should be used when the user asks to "retro", "evaluate zforge", "review plugin performance", "score this session", or wants to assess how well zforge's workflow served a feature. Evaluates zforge's workflow scaffolding, not the project's technical decisions or LLM reasoning quality.
template-conventions
This skill should be used when the user asks to "plan a feature", "what goes in the phase file", "which file owns this", "what evidence class is this", "how do I verify a claim no test can settle", "where should this doc go", or when writing, reading or updating any zforge feature document under docs/{feature}/.…
async-reasoning
This skill should be used when implementing or designing code with async data flows — "state management design", "async data flow", "stale data", "cache invalidation", "optimistic update", "init order", "race condition", "write then read", "data not updating", "cache not refreshing", "UI shows old data after save"…