architecture-patterns

architecture-patterns is a skill for Claude Code from yonatangross/orchestkit. It costs 56 tokens per session (3,049 once invoked), scanned A, original, MIT.

A set of rules for organizing software into clear layers and boundaries, such as separating web routes, business services, and data access. It also covers clean architecture, project folders, dependency injection, and test standards.

In plain words
What is it for?
Use it when designing backend systems, choosing folder and layer boundaries, enforcing import direction, defining test conventions, or reviewing whether an architecture is too complex.
Why use it?
It reduces tangled dependencies, inconsistent project structures, and code that is difficult to test or change. The right-sizing guidance helps avoid adding architecture that a project does not need.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions Claude Code.

Part of the ork plugin — 111 skills, 38 commands, 36 agents, 32 hooks shipped together

Good fit Use it when designing backend systems, choosing folder and layer boundaries, enforcing import direction, defining test conventions, or reviewing whether an architecture is too complex.

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

Made for: Claude Code.

Or install ork, the plugin that ships this one along with the rest of its 111 skills, 38 commands, 36 agents, 32 hooks.

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/yonatangross/orchestkit/architecture-patterns/github.svg)](https://agentmods.dev/skills/yonatangross/orchestkit/architecture-patterns)
Your own site
<a href="https://agentmods.dev/skills/yonatangross/orchestkit/architecture-patterns"><img src="https://agentmods.dev/badge/skills/yonatangross/orchestkit/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/yonatangross/orchestkit/architecture-patterns"><img src="https://agentmods.dev/badge/skills/yonatangross/orchestkit/architecture-patterns.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 56 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,049 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. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • high Prompt Injection · line 28
    Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
    Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
How audits are shown
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.00056 $0.03049
Opus 5.5 $0.00022 $0.01220
Sonnet 5.5 $0.00011 $0.00610
Haiku 4.5 $0.00006 $0.00305

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

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/domain-entity-template.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

plugins/ork/skills/architecture-patterns/SKILL.md · 262 lines

How it starts

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

Architecture Patterns

Consolidated architecture validation and enforcement patterns covering clean architecture, backend layer separation, project structure conventions, and test standards. Each category has individual rule files in rules/ loaded on-demand. House scars and dated decisions rescued from retired reference tutorials live in references/ork-delta.md; the tutorials themselves are upstream's job (see "Upstream coverage" below).

Quick Reference

Category Rules Impact When to Use
Clean Architecture 3 HIGH SOLID principles, hexagonal architecture, ports & adapters, DDD
Project Structure 2 HIGH Folder conventions, nesting depth, import direction, barrel files
Backend Layers 3 HIGH Router/service/repository separation, DI, file naming
Test Standards 3 MEDIUM AAA pattern, naming conventions, coverage thresholds
Right-Sizing 2 HIGH Architecture tier selection, over-engineering prevention, context-aware enforcement

Total: 13 rules across 5 categories

Quick Start

# Clean Architecture: Dependency Inversion via Protocol
class IUserRepository(Protocol):
    async def get_by_id(self, id: str) -> User | None: ...

class UserService:
    def __init__(self, repo: IUserRepository):
        self._repo = repo  # Depends on abstraction, not concretion

# FastAPI DI chain: DB -> Repository -> Service
def get_user_service(db: AsyncSession = Depends(get_db)) -> UserService:
    return UserService(PostgresUserRepository(db))
# Project Structure: Unidirectional Import Architecture
shared/lib  ->  components  ->  features  ->  app
(lowest)                                    (highest)

# Backend Layers: Strict Separation
Routers (HTTP) -> Services (Business Logic) -> Repositories (Data Access)

Read the full file on GitHub · 262 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 Changed · -1 lines 6e1685b6b15f
  2. 19d ago Changed · -5 lines c09d4a143e8b
  3. 20d ago Changed · -1 lines 64d1a02b6ca2
  4. 28d ago Changed 10bc1d7bb4d7
  5. 1mo ago Changed ed1575cbdb10
  6. 1mo ago First seen · 269 lines · 56 tokens per session scan A 9d957f9e720c

Subscribe to this mod's changes

architecture-patterns is a skill published in the GitHub repository yonatangross/orchestkit (296 stars, last pushed today), licensed MIT. It adds 56 tokens to every session and 3,049 once invoked, about $0.0002 per session on Opus 5.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-09-03.

Related

Other skills, from other repositories

test-writer

How to write pytest tests for modules in this workspace. Load whenever you are about to write or extend tests.

genkit-ai/genkit · 26 tokens

deepeval

Use when discussing or working with DeepEval (the python AI evaluation framework).

sammcj/agentic-coding · 19 tokens

spring-boot-test-patterns

Provides comprehensive testing patterns for Spring Boot applications covering unit, integration, slice, and container-based testing with JUnit 5, Mockito, Testcontainers, and performance optimization. Use when writing tests, @Test methods, @MockBean mocks, or implementing test suites for Spring Boot applications.

giuseppe-trisciuoglio/developer-kit · 64 tokens

unit-test-caching

Provides patterns for unit testing Spring Cache annotations (@Cacheable, @CachePut, @CacheEvict). Generates test code that mocks cache managers, verifies cache hit/miss behavior, tests cache key generation with SpEL expressions, validates eviction strategies, and checks conditional caching scenarios. Triggers: caching…

giuseppe-trisciuoglio/developer-kit · 88 tokens

unit-test-config-properties

Provides patterns for unit testing @ConfigurationProperties classes with @ConfigurationPropertiesTest. Validates property binding, tests validation constraints, verifies default values, checks type conversions, and mocks property sources for Spring Boot configuration properties. Use when testing application…

giuseppe-trisciuoglio/developer-kit · 75 tokens

unit-test-json-serialization

Provides patterns for unit testing JSON serialization/deserialization with Jackson and @JsonTest. Validates JSON mapping, custom serializers, date formats, and polymorphic types. Use when testing JSON serialization, validating custom serializers, or writing JSON unit tests in Spring Boot applications.

giuseppe-trisciuoglio/developer-kit · 59 tokens