What is architecture-patterns?

A reference guide for choosing and comparing software architecture patterns, such as monoliths, microservices, serverless systems, event-driven systems, and CQRS. These patterns describe how an application is divided and how its parts communicate.

It supports recommendations and evaluations for new systems, including decisions about service boundaries, deployment complexity, scaling, data storage, and experimentation speed.

It helps match an architecture to team size, operational skills, budget, consistency needs, and scaling requirements instead of choosing a pattern in isolation.

architecture-patterns — Skill for Claude Code by AhmedHabiba

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 AhmedHabiba/architor --skill architecture-patterns

Clone the repo

git clone --depth 1 https://github.com/AhmedHabiba/architor

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/ahmedhabiba/architor/architecture-patterns/github.svg)](https://agentmods.dev/skills/ahmedhabiba/architor/architecture-patterns)

Your own site

<a href="https://agentmods.dev/skills/ahmedhabiba/architor/architecture-patterns"><img src="https://agentmods.dev/badge/skills/ahmedhabiba/architor/architecture-patterns/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/ahmedhabiba/architor/architecture-patterns"><img src="https://agentmods.dev/badge/skills/ahmedhabiba/architor/architecture-patterns.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 661 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.

Model	Per session	Once invoked
Fable 5.1	$0.00045	$0.00661
Opus 5	$0.00023	$0.00331
Sonnet 5	$0.00009	$0.00132
Haiku 4.5	$0.00005	$0.00066

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

Security

Grade A, and why

architecture-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 9d 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.

.claude/skills/architecture-patterns/SKILL.md · 72 lines

How it starts

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

Architecture Patterns Knowledge

Pattern Selection Framework

When recommending a pattern, evaluate against these criteria:

Team Fit

Team size < 5 → Strongly favor monolith or modular monolith
Team size 5-15 → Modular monolith or bounded microservices
Team size 15+ → Microservices viable if org supports it
No DevOps/Platform team → Avoid Kubernetes-heavy architectures
Junior-heavy team → Favor simpler patterns with clear boundaries

Operational Reality

1 DevOps engineer → Cannot sustain >3 independently deployed services
No dedicated DBA → Avoid polyglot persistence
Limited monitoring experience → Start with monolith + good observability
Budget constrained → Serverless for spiky loads, monolith for steady

Requirement Signals

Independent scaling needs → Microservices or serverless
Strong consistency requirements → Monolith or synchronous microservices
Event-heavy domain → Event-driven architecture
Read/write asymmetry → CQRS
Rapid experimentation needed → Modular monolith (fastest to change)
Regulatory isolation → Service per compliance boundary

Pattern Comparison Quick Reference

Monolith

Best for: Small teams, rapid development, strong consistency needs
Risks: Scaling bottleneck, deployment coupling, team scaling limits
Migrate to: Modular monolith → microservices (progressive)

Modular Monolith

Best for: Teams 3-10, need clear boundaries without operational overhead
Risks: Module coupling creep, single deployment unit
Migrate to: Extract modules to services as needed

Microservices

Best for: Large teams, independent scaling, polyglot needs
Risks: Distributed system complexity, data consistency, operational overhead
Prerequisite: CI/CD maturity, monitoring, team autonomy

Event-Driven

Best for: Async workflows, decoupled services, audit trails
Risks: Eventual consistency complexity, debugging difficulty, event schema evolution
Prerequisite: Team comfort with async patterns, good monitoring

Read the full file on GitHub · 72 lines

Files

What ships with it

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

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.

9d ago First seen · 72 lines · 45 tokens per session scan A 9c5cb5cbb6f6

Subscribe to this mod's changes

architecture-patterns is a skill published in the GitHub repository AhmedHabiba/architor (6 stars, last pushed 6mo ago), licensed MIT. It adds 45 tokens to every session and 661 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-31.

Claude Code Planning ai ai-agents architecture-automation claude claude-code-plugin

create-site

Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…

microsoft/power-platform-skills · 73 tokens

google-ads-audit

Google Ads account audit and business context setup. Run this first — it gathers business information, analyzes account health, and saves context that all other ads skills reuse. Trigger on "audit my ads", "ads audit", "set up my ads", "onboard", "account overview", "how's my account", "ads health check", "what should…

nowork-studio/notfair-plugin · 114 tokens

architecture-patterns