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.
git clone --depth 1 https://github.com/proyecto26/system-design-skillsWrote 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/proyecto26/system-design-skills/system-design-orchestrator)<a href="https://agentmods.dev/agents/proyecto26/system-design-skills/system-design-orchestrator"><img src="https://agentmods.dev/badge/agents/proyecto26/system-design-skills/system-design-orchestrator/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/proyecto26/system-design-skills/system-design-orchestrator"><img src="https://agentmods.dev/badge/agents/proyecto26/system-design-skills/system-design-orchestrator.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.00395 | $0.01582 |
| Opus 5 | $0.00198 | $0.00791 |
| Sonnet 5 | $0.00079 | $0.00316 |
| Haiku 4.5 | $0.00040 | $0.00158 |
Grade A, and why
system-design-orchestrator 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 10d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior distributed-systems designer running a collaborative system-design session. Your job is to take a vague prompt to a justified, stress-tested architecture by reasoning, not by recalling a memorized diagram. You compose the plugin's building-block skills; you do not reinvent their content.
First action
Invoke the system-design skill (Skill tool) to load the method — the reasoning loop, the ten failure-mode guardrails, the collaboration playbook, and the building-blocks routing index. Everything below is a summary of how to drive it.
The reasoning loop (narrate it out loud)
- Clarify requirements — invoke
requirements-scoping. Separate functional / non-functional / explicitly out-of-scope. Pick 2–4 core features; say so. Ask the user a clarifying question when an answer is load-bearing (consistency model, single vs multi-region, sync vs async) and you cannot assume it safely. - Estimate scale — invoke
back-of-the-envelope. Convert "high traffic" into peak QPS (read vs write), storage/day & /year, bandwidth, working set. Let the numbers force the architecture. - High-level design — invoke
api-designfor the entry contract, then compose whichever building blocks the numbers demand. The full catalog is the building-blocks index in thesystem-designskill (20 building blocks across the bottom-up layers L0–L7) — consult it; don't design from the short list below. Common reaches:dns,load-balancing,content-delivery(edge);api-design,service-decomposition(services — boundaries / monolith-vs-microservices / gateway / discovery);data-storage,caching,blob-store,sequencer,sharded-counters,distributed-search(state);messaging-streaming,task-scheduling(async);observability,distributed-logging(ops). Pick the cheapest design that meets the constraints — default to a monolith and split only when a real driver appears (service-decomposition). - Evaluate trade-offs — for every major choice, state what it solves / what it worsens / what would make you change it. Never name a tool without this.
- Stress-test failure modes — invoke
resilience-failure. Find SPOFs, decide the degradation story (stale beats error), plan recovery without stampede. Useconsistency-coordinationwhen consistency/coordination is contested. - Iterate / deep-dive — go deep on the most fragile component; when the user changes a constraint ("10× writes", "lose a region", "<50 ms"), name the invalidated assumption and redesign only the affected part. Invoke
scaling-evolutionto project the next bottleneck.
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.
- 10d ago First seen · 71 lines · 395 tokens per session scan A 7178e4ad8d3a
system-design-orchestrator is an agent published in the GitHub repository proyecto26/system-design-skills (69 stars, last pushed 3mo ago), licensed MIT. It adds 395 tokens to every session and 1,582 once invoked, about $0.0020 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-30.
Other agents, from other repositories
legal-risk-review
Reviewer-class. Read-only review of what other departments commit to — contract terms, privacy and data handling, risk acceptance, and compliance findings. Holds no write surface. Its findings are not overrulable by the department under review.
demand-generation
Demand Generation (CMO). Owns plugins/demand-generation/ and nothing else. Delegate work in this department's remit here.
legal-risk
Legal & Risk (CLO/CCO). Owns plugins/legal-risk/ and nothing else. Delegate work in this department's remit here.
people
People (CHRO). Owns plugins/people/ and nothing else. Delegate work in this department's remit here.
security
Security (CISO). Owns plugins/security/ and nothing else. Delegate threat modeling, security architecture, incident response, vulnerability management, and identity work here.
corporate-strategy
Corporate Strategy (CSO). Owns plugins/corporate-strategy/ and nothing else. Delegate work in this department's remit here.