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 skills add athola/claude-night-market --skill architecture-paradigmsgit clone --depth 1 https://github.com/athola/claude-night-marketWrote 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/athola/claude-night-market/architecture-paradigms)<a href="https://agentmods.dev/skills/athola/claude-night-market/architecture-paradigms"><img src="https://agentmods.dev/badge/skills/athola/claude-night-market/architecture-paradigms/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.
<a href="https://agentmods.dev/skills/athola/claude-night-market/architecture-paradigms"><img src="https://agentmods.dev/badge/skills/athola/claude-night-market/architecture-paradigms.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00033 | $0.01950 |
| Opus 5 | $0.00016 | $0.00975 |
| Sonnet 5 | $0.00007 | $0.00390 |
| Haiku 4.5 | $0.00003 | $0.00195 |
Grade A, and why
architecture-paradigms 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.
How it starts
The opening of the file, as written. The whole thing — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When NOT To Use
- The paradigm is already chosen, so go straight to that paradigm's skill
- Reviewing an existing design against its ADRs (use
pensive:architecture-review)
Table of Contents
- Quick Scenario Router
- 3-Step Selection Workflow
- Available Paradigm Skills
- Integration with Other Skills
- Exit Criteria
Architecture Paradigm Router
This skill helps you select the right architecture paradigm(s) for your system, then routes you to the specific paradigm skill for implementation details.
Quick Scenario Router
Match your needs to the recommended paradigm:
| Your Scenario | Primary Paradigm | Load Skill |
|---|---|---|
| Enterprise app with multiple teams | Microservices or Modular Monolith | architecture-paradigm-microservices or architecture-paradigm-modular-monolith |
| Complex business rules & testing | Functional Core, Imperative Shell | architecture-paradigm-functional-core |
| Real-time/event processing | Event-Driven Architecture | architecture-paradigm-event-driven |
| Legacy system modernization | Hexagonal (Ports & Adapters) | architecture-paradigm-hexagonal |
| Cloud-native/bursty workloads | Serverless | architecture-paradigm-serverless |
| ETL/data processing pipeline | Pipeline Architecture | architecture-paradigm-pipeline |
| Simple CRUD app | Layered Architecture | architecture-paradigm-layered |
| Command/query separation | CQRS and Event Sourcing | architecture-paradigm-cqrs-es |
| Rich business rules to model | Domain-Driven Design | architecture-paradigm-domain-driven |
One of these is not like the others. Domain-Driven Design answers "what are the concepts and what do we call them." The rest answer "where does the code go." DDD composes with a structural paradigm (commonly layered, hexagonal, or modular monolith) rather than competing with it, so selecting it does not mean deselecting one of the others.
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 · 180 lines · 33 tokens per session scan A 02fd82cb123d
architecture-paradigms is a skill published in the GitHub repository athola/claude-night-market (337 stars, last pushed 2d ago), licensed MIT. It adds 33 tokens to every session and 1,950 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-09-03.
Other skills, from other repositories
blockchain-patterns
Use this skill when asked about blockchain design patterns, token standards, upgradeable contracts, oracle patterns, layer 2 scaling patterns, cross-chain communication patterns, and common blockchain architecture patterns. Covers ERC standards (20, 721, 1155, 4626, 4337), proxy patterns (UUPS, transparent, beacon)…
algolia-search-v2
Algolia Search Integration workflow skill. Use this skill when the user needs Expert patterns for Algolia search implementation, indexing and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
decision-backfill
Use when auditing an existing codebase, documentation set, plans, RFCs, or git history for architecture decisions that were made but never recorded as ADRs, and when triaging potential records before drafting them.
decision-memory
Use when planning, designing, reviewing, or changing code in a repository that keeps ADRs (usually docs/adr) — to load the decisions that already govern the work, check a plan or diff against them, or record a new decision. Also use when a choice feels already-settled and you cannot find where it was settled.
cloud-design-patterns
Choose and compare cloud design patterns for distributed systems. Use when reviewing architecture, selecting workload patterns, or mapping reliability, performance, messaging, security, and migration concerns to concrete design options.
adr-documentation
Architecture Decision Records (ADR) documentation practice. Use when documenting architectural decisions, recording technical trade-offs, creating decision logs, or establishing architectural patterns. Trigger keywords - "ADR", "architecture decision", "decision record", "trade-offs", "architectural decision"…