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/yonatangross/orchestkit/architecture-patternsnpx skills add yonatangross/orchestkit --skill architecture-patternsgit clone --depth 1 https://github.com/yonatangross/orchestkitWrote 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/yonatangross/orchestkit/architecture-patterns)<a href="https://agentmods.dev/skills/yonatangross/orchestkit/architecture-patterns"><img src="https://agentmods.dev/badge/skills/yonatangross/orchestkit/architecture-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.00056 | $0.03266 |
| Opus 5 | $0.00028 | $0.01633 |
| Sonnet 5 | $0.00011 | $0.00653 |
| Haiku 4.5 | $0.00006 | $0.00327 |
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 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 — 269 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)
What ships with it
23 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.
- checklists/solid-checklist.md 4.4 KB
- metadata.json 616 B
- references/naming-conventions.md 2.2 KB
- references/ork-delta.md 3.3 KB
- references/structure-import-direction.md 4.5 KB
- references/testing-naming-conventions.md 3.6 KB
- rules/_sections.md 2.1 KB
- rules/_template.md 339 B
- rules/backend-di.md 2.0 KB
- rules/backend-layers.md 2.7 KB
- rules/backend-repository.md 1.8 KB
- rules/clean-dependency-rule.md 2.4 KB
- rules/clean-hexagonal.md 3.5 KB
- rules/clean-ports-adapters.md 2.4 KB
- rules/right-sizing-decision.md 3.0 KB
- rules/right-sizing-tiers.md 3.6 KB
- rules/structure-conventions.md 2.2 KB
- rules/structure-folders.md 2.3 KB
- rules/testing-aaa.md 2.1 KB
- rules/testing-coverage.md 1.7 KB
- rules/testing-naming.md 1.8 KB
- scripts/domain-entity-template.py 9.3 KB runs code
- test-cases.json 5.7 KB
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 First seen · 269 lines · 56 tokens per session scan A 9d957f9e720c
architecture-patterns is a skill published in the GitHub repository yonatangross/orchestkit (225 stars, last pushed today), licensed MIT. It adds 56 tokens to every session and 3,266 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
plugin-review
Review plugin quality with tiered checks and dependency scoping. Use for PR and pre-release audits.
api-design-patterns
Comprehensive API design patterns covering REST, GraphQL, gRPC, versioning, authentication, and modern API best practices.
convert-three-locks
Architect the Three Locks persuasion sequence: Lock 1 Want (sell the state), Lock 2 Trust (earn belief through proof + voice), Lock 3 Excuse (give the rational justification). Outputs the lock-by-lock blueprint that the rest of the asset writes against. Use when planning the persuasion architecture of a sales page…
ios-architecture-expert
Use when the user is designing, structuring, refactoring, or reviewing the architecture of an iOS/Swift app: separating features into modules/layers (domain, API, cache, presentation, UI), choosing between MVC/MVVM/MVP, wiring dependencies in a composition root, breaking up a view controller that coordinates too much…
mpm-circuit-breaker-enforcement
Complete circuit breaker enforcement patterns with examples and remediation.
skill-adr
Registra decisões arquiteturais com contexto, alternativas, drivers, consequências, evidência e plano de revisão.