software-design-clean-architecture

software-design-clean-architecture is a skill for Claude Code, Codex from xiaohei-info/oh-my-multica. It costs 122 tokens per session (4,096 once invoked), scanned A, original, MIT.

A software-architecture guide based on Clean Architecture, where business rules stay independent from frameworks, databases, user interfaces, and other outside details.

In plain words
What is it for?
Use it when designing architecture, reviewing module boundaries, or deciding how dependencies should flow between business rules and external systems.
Why use it?
It helps keep core logic easier to test and makes it less costly to replace technical details or change how users access the system.

Skill for Claude CodeCodex

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

Good fit Use it when designing architecture, reviewing module boundaries, or deciding how dependencies should flow between business rules and external systems.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/xiaohei-info/oh-my-multica/software-design-clean-architecture
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 xiaohei-info/oh-my-multica --skill software-design-clean-architecture
Clone the repo
git clone --depth 1 https://github.com/xiaohei-info/oh-my-multica

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 software-design-clean-architecture

README.md
[![agentmods](https://agentmods.dev/badge/skills/xiaohei-info/oh-my-multica/software-design-clean-architecture/github.svg)](https://agentmods.dev/skills/xiaohei-info/oh-my-multica/software-design-clean-architecture)
Your own site
<a href="https://agentmods.dev/skills/xiaohei-info/oh-my-multica/software-design-clean-architecture"><img src="https://agentmods.dev/badge/skills/xiaohei-info/oh-my-multica/software-design-clean-architecture/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 software-design-clean-architecture

Your own site · 80×15
<a href="https://agentmods.dev/skills/xiaohei-info/oh-my-multica/software-design-clean-architecture"><img src="https://agentmods.dev/badge/skills/xiaohei-info/oh-my-multica/software-design-clean-architecture.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 122 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,096 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 pass 7 Sept 2026
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.00122 $0.04096
Opus 5 $0.00061 $0.02048
Sonnet 5 $0.00024 $0.00819
Haiku 4.5 $0.00012 $0.00410

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

Security

Grade A, and why

software-design-clean-architecture 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 12d 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.

src/omac/agents/architect/skills/software-design-clean-architecture/SKILL.md · 225 lines

How it starts

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

Clean Architecture Framework

A disciplined approach to structuring software so that business rules remain independent of frameworks, databases, and delivery mechanisms. Apply these principles when designing system architecture, reviewing module boundaries, or advising on dependency management.

Core Principle

Source code dependencies must point inward -- toward higher-level policies. Nothing in an inner circle can know anything about something in an outer circle. This single rule, applied consistently, produces systems that are testable, independent of frameworks, independent of the UI, independent of the database, and independent of any external agency.

The foundation: Software architecture is about drawing lines -- boundaries -- that separate things that matter from things that are details. Business rules are what matter. Databases, web frameworks, and delivery mechanisms are details. When details depend on policies (not the other way around), you can defer decisions, swap implementations, and test business logic in isolation.

Scoring

Goal: 10/10. When reviewing or creating software architecture, rate it 0-10 based on adherence to the principles below. A 10/10 means full alignment with all guidelines; lower scores indicate gaps to address. Always provide the current score and specific improvements needed to reach 10/10.

The Clean Architecture Framework

Six principles for building systems that survive the passage of time:

1. Dependency Rule and Concentric Circles

Core concept: The architecture is organized as concentric circles. The innermost circle contains Entities (enterprise business rules). The next circle contains Use Cases (application business rules). Then Interface Adapters. The outermost circle contains Frameworks and Drivers. Source code dependencies always point inward.

Why it works: When high-level policies don't depend on low-level details, you can change the database from MySQL to MongoDB, swap a web framework, or replace a REST API with GraphQL -- all without touching business logic. The system becomes resilient to the most volatile parts of the technology stack.

Read the full file on GitHub · 225 lines

Files

What ships with it

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

  1. 12d ago First seen · 225 lines · 122 tokens per session scan A 4bb384336801

Subscribe to this mod's changes

software-design-clean-architecture is a skill published in the GitHub repository xiaohei-info/oh-my-multica (26 stars, last pushed 5d ago), licensed MIT. It adds 122 tokens to every session and 4,096 once invoked, about $0.0006 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-30.