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/practicalswan/agent-skills/cloud-design-patternsnpx skills add PracticalSwan/agent-skills --skill cloud-design-patternsgit clone --depth 1 https://github.com/PracticalSwan/agent-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/skills/practicalswan/agent-skills/cloud-design-patterns)<a href="https://agentmods.dev/skills/practicalswan/agent-skills/cloud-design-patterns"><img src="https://agentmods.dev/badge/skills/practicalswan/agent-skills/cloud-design-patterns.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.00042 | $0.01384 |
| Opus 5 | $0.00021 | $0.00692 |
| Sonnet 5 | $0.00008 | $0.00277 |
| Haiku 4.5 | $0.00004 | $0.00138 |
Grade A, and why
cloud-design-patterns 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cloud Design Patterns
Use proven distributed-systems patterns to choose safer architectures and surface trade-offs early.
- Leverage native parallel subagent dispatch and 200k+ context windows where available.
When to Use
Use symptom -> action triggers: when one matches, apply this skill and verify with the protocol below.
- You are designing or reviewing a cloud or distributed-system architecture.
- A workload has reliability, latency, scaling, messaging, migration, or security concerns.
- You need to shortlist patterns before writing an ADR, design doc, or implementation plan.
- You want a technology-agnostic pattern discussion before choosing platform services.
Pattern Selection Workflow
- State the main workload goal and the main constraint.
- Identify the top concerns: reliability, performance, messaging, migration, deployment, security, or eventing.
- Use the concern-to-pattern map below to shortlist candidates.
- Compare trade-offs instead of looking for a single perfect pattern.
- Document why the chosen pattern fits the workload better than the obvious alternatives.
Concern-To-Pattern Map
| Concern | Common patterns | Reference |
|---|---|---|
| reliability and fault tolerance | Bulkhead, Circuit Breaker, Retry, Health Endpoint Monitoring, Saga | Reliability And Resilience |
| performance and scale | Cache-Aside, CQRS, Queue-Based Load Leveling, Rate Limiting, Sharding | Performance |
| messaging and workflow coordination | Publisher-Subscriber, Pipes and Filters, Competing Consumers, Choreography | Messaging And Integration |
| architecture boundaries and API shape | Anti-Corruption Layer, Backends for Frontends, Gateway patterns, Sidecar, Strangler Fig | Architecture And Design |
| deployment and operations | Deployment Stamps, External Configuration Store, Geode, Static Content Hosting | Deployment And Operational |
| security and controlled access | Federated Identity, Quarantine, Valet Key | Security |
| event sourcing and auditability | Event Sourcing | Event-Driven |
What ships with it
11 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- CHANGELOG.md 4.7 KB
- references/architecture-design.md 4.6 KB
- references/azure-service-mappings.md 606 B
- references/best-practices.md 1.6 KB
- references/deployment-operational.md 3.2 KB
- references/event-driven.md 715 B
- references/messaging-integration.md 4.5 KB
- references/performance.md 6.6 KB
- references/reliability-resilience.md 6.2 KB
- references/security.md 1.8 KB
- scripts/pattern-shortlist.py 3.2 KB runs code
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 240aea733076
- 4d ago First seen · 121 lines · 42 tokens per session scan A 88b320bb9ab1
cloud-design-patterns is a skill published in the GitHub repository PracticalSwan/agent-skills (13 stars, last pushed 3d ago), licensed MIT. It adds 42 tokens to every session and 1,384 once invoked, about $0.0002 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 skills, from other repositories
azure-diagrams
Comprehensive technical diagramming toolkit for solutions architects, presales, and developers. Creates Azure architecture diagrams (800+ Azure service icons), business process flows (swimlanes, workflows), ERD diagrams (database schemas), project timelines, UI wireframes, and network topology diagrams. Perfect for…
design-expert
Expert-level system design, architecture patterns, scalability, and distributed systems.
architecture-diagrams
Turn a natural-language cloud architecture description into an editable diagram whose nodes are official vendor service icons (Azure, AWS, GCP, Kubernetes), exported as PDF, draw.io, or VSDX (Lucid-importable). Use when the user asks to draw, diagram, or visualize a cloud/system architecture, or to produce a…
design-patterns-expert
Comprehensive knowledge of all 23 Gang of Four design patterns with progressive disclosure (Quick/Practical/Deep), pattern recognition for problem-solving, and philosophy-aligned guidance to prevent over-engineering.
oci-drawio-icon-native
Build and validate OCI draw.io diagrams in icon-native mode so they never depend on mxgraph.oci. runtime libraries. Use when authoring or fixing Oracle Cloud architecture diagrams in draw.io that must render portably.
software-patterns
Decision framework for architectural patterns including DI, SOA, Repository, Domain Events, Circuit Breaker, and Anti-Corruption Layer. Use when designing systems, choosing patterns, or reviewing architecture.