architecture-patterns

architecture-patterns is a skill for Claude Code, Codex from marysatasselshaped667/skills-collection-1. It costs 34 tokens per session (367 once invoked), scanned A, a copy of architecture-patterns, MIT.

A guide to organizing backend software with established patterns such as Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. These patterns separate business rules from outside systems so code is easier to change and test.

In plain words
What is it for?
Use it to design backend systems, refactor monoliths, plan microservices, define domain boundaries, create testable modules, and design workflows that must survive failures, such as payments or order fulfillment.
Why use it?
It helps untangle tightly connected code and reduce the cost of future changes. It also gives teams a way to define module boundaries, interfaces, and service responsibilities before splitting or refactoring a system.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to design backend systems, refactor monoliths, plan microservices, define domain boundaries, create testable modules, and design workflows that must survive failures, such as payments or order fulfillment.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/marysatasselshaped667/skills-collection-1/architecture-patterns
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 marysatasselshaped667/skills-collection-1 --skill architecture-patterns
Clone the repo
git clone --depth 1 https://github.com/marysatasselshaped667/skills-collection-1

Made for: Claude Code, Codex.

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

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

agentmods 80×15 button for architecture-patterns

Your own site · 80×15
<a href="https://agentmods.dev/skills/marysatasselshaped667/skills-collection-1/architecture-patterns"><img src="https://agentmods.dev/badge/skills/marysatasselshaped667/skills-collection-1/architecture-patterns.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 367 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 86% copy Near-identical to another mod 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.00034 $0.00367
Opus 5 $0.00017 $0.00183
Sonnet 5 $0.00007 $0.00073
Haiku 4.5 $0.00003 $0.00037

Measured 7d ago against content hash 2c28ef0ab26e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, 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 7d 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.

Origin

This is a copy

86% identical to architecture-patterns — 5 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

SKILLS/architecture-patterns/SKILL.md · 46 lines

What it actually says

Architecture Patterns

Master proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design to build maintainable, testable, and scalable systems.

Use this skill when

  • Designing new backend systems from scratch
  • Refactoring monolithic applications for better maintainability
  • Establishing architecture standards for your team
  • Migrating from tightly coupled to loosely coupled architectures
  • Implementing domain-driven design principles
  • Creating testable and mockable codebases
  • Planning microservices decomposition

Do not use this skill when

  • You only need small, localized refactors
  • The system is primarily frontend with no backend architecture changes
  • You need implementation details without architectural design

Instructions

  1. Clarify domain boundaries, constraints, and scalability targets.
  2. Select an architecture pattern that fits the domain complexity.
  3. Define module boundaries, interfaces, and dependency rules.
  4. Provide migration steps and validation checks.
  5. For workflows that must survive failures (payments, order fulfillment, multi-step processes), use durable execution at the infrastructure layer — frameworks like DBOS persist workflow state, providing crash recovery without adding architectural complexity.

Refer to resources/implementation-playbook.md for detailed patterns, checklists, and templates.

Works well with: event-sourcing-architect, saga-orchestration, workflow-automation, dbos-*

Resources

  • resources/implementation-playbook.md for detailed patterns, checklists, and templates.
Files

What ships with it

1 file 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.

  1. 7d ago First seen · 46 lines · 34 tokens per session scan A 2c28ef0ab26e

Subscribe to this mod's changes

architecture-patterns is a skill published in the GitHub repository marysatasselshaped667/skills-collection-1 (1 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 367 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to architecture-patterns, differing in 5 lines, and is treated as a copy.