architecture-patterns-catalog

architecture-patterns-catalog is a skill for Claude Code from sethdford/claude-skills. It costs 33 tokens per session (825 once invoked), scanned A, original, MIT.

A reference catalogue of established software-architecture patterns, including ways to structure components, services, data flows, and messages. Examples include Adapter, Observer, microservices, event-driven systems, and Saga.

In plain words
What is it for?
Use it while designing systems to find suitable communication, data, messaging, structural, behavioral, or architectural patterns.
Why use it?
It helps developers choose a known design approach and understand its trade-offs instead of designing every solution from scratch.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the architect-toolkit plugin — 7 skills shipped together

Good fit Use it while designing systems to find suitable communication, data, messaging, structural, behavioral, or architectural patterns.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/sethdford/claude-skills/architecture-patterns-catalog
Install

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.

Any agent
npx skills add sethdford/claude-skills --skill architecture-patterns-catalog
Clone the repo
git clone --depth 1 https://github.com/sethdford/claude-skills

Made for: Claude Code.

Or install architect-toolkit, the plugin that ships this one along with the rest of its 7 skills.

Wrote 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.

agentmods badge for architecture-patterns-catalog

README.md
[![agentmods](https://agentmods.dev/badge/skills/sethdford/claude-skills/architecture-patterns-catalog/github.svg)](https://agentmods.dev/skills/sethdford/claude-skills/architecture-patterns-catalog)
Your own site
<a href="https://agentmods.dev/skills/sethdford/claude-skills/architecture-patterns-catalog"><img src="https://agentmods.dev/badge/skills/sethdford/claude-skills/architecture-patterns-catalog/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.

agentmods 80×15 button for architecture-patterns-catalog

Your own site · 80×15
<a href="https://agentmods.dev/skills/sethdford/claude-skills/architecture-patterns-catalog"><img src="https://agentmods.dev/badge/skills/sethdford/claude-skills/architecture-patterns-catalog.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 825 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00033 $0.00825
Opus 5 $0.00016 $0.00413
Sonnet 5 $0.00007 $0.00165
Haiku 4.5 $0.00003 $0.00082

Measured 11d ago against content hash 702dc9ef4f37, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

architecture-patterns-catalog 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 11d 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.

architect/architect-toolkit/skills/architecture-patterns-catalog/SKILL.md · 73 lines

How it starts

The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Architecture Patterns Catalog

Curated reference of proven patterns with guidance on when and how to apply them.

Context

You are designing a system and want to know proven patterns that solve your problem. Reference catalog of patterns: when to use, tradeoffs, real-world examples.

Domain Context

Based on pattern catalogs (Gang of Four, Enterprise Patterns, Domain-Driven Design):

  • Structural Patterns: How components fit together (Adapter, Facade, Bridge)
  • Behavioral Patterns: How components interact (Observer, Strategy, State)
  • Architectural Patterns: System-level patterns (Microservices, Event-Driven, CQRS)
  • Data Patterns: How data flows (ETL, CDC, Event Sourcing)
  • Messaging Patterns: How services communicate (Request-Reply, Pub-Sub, Saga)

Pattern Categories with Examples

  1. Communication Patterns:

    • Synchronous (Request-Reply): REST, gRPC. Blocking, tight coupling, simple.
    • Asynchronous (Pub-Sub): Message broker, events. Loose coupling, eventual consistency.
    • Saga Pattern: Distributed transaction across services. Orchestrator vs choreographer.
  2. Data Patterns:

    • Event Sourcing: Store events as source of truth. Auditability, temporal queries, replay.
    • CQRS: Separate read and write models. Scalability, complexity.
    • Polyglot Persistence: Different databases for different workloads. Flexibility, operational complexity.
  3. Resilience Patterns:

    • Circuit Breaker: Stop calling failing service, fast-fail. Prevent cascade failure.
    • Bulkhead: Isolate resources (threads, connections). One service failure doesn't starve others.
    • Retry with Backoff: Retry with exponential backoff. Transient failures recover.
  4. Scalability Patterns:

    • Sharding: Partition data across databases. Horizontal scaling, complexity.
    • Caching: Cache hot data. Latency, consistency trade-off.
    • Load Balancing: Distribute across instances. Horizontal scaling.

Read the full file on GitHub · 73 lines

Changes

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.

  1. 11d ago First seen · 73 lines · 33 tokens per session scan A 702dc9ef4f37

Subscribe to this mod's changes

architecture-patterns-catalog is a skill published in the GitHub repository sethdford/claude-skills (40 stars, last pushed 6mo ago), licensed MIT. It adds 33 tokens to every session and 825 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.

Related

Other skills, from other repositories