clean-architecture

clean-architecture is a skill for Claude Code from andr-ca/agentharness. It costs 36 tokens per session (1,075 once invoked), scanned A, original, MIT.

A guide for structuring applications so business rules stay separate from web frameworks, databases, queues, email systems, and other outside services. This approach is often called clean or hexagonal architecture.

In plain words
What is it for?
Use it when business logic is tangled with infrastructure, or when deciding how to divide domain, application, and infrastructure code.
Why use it?
It reduces the risk that changing a database or framework will require rewriting the core business logic.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: reads .claude/ paths.

Good fit Use it when business logic is tangled with infrastructure, or when deciding how to divide domain, application, and infrastructure code.

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

Made for: Claude Code.

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

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/andr-ca/agentharness/clean-architecture"><img src="https://agentmods.dev/badge/skills/andr-ca/agentharness/clean-architecture.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,075 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 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.00036 $0.01075
Opus 5.5 $0.00014 $0.00430
Sonnet 5.5 $0.00007 $0.00215
Haiku 4.5 $0.00004 $0.00108

Measured 1mo ago against content hash 676bcfbbec80, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

.claude/skills/clean-architecture/SKILL.md · 130 lines

How it starts

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

Clean Architecture (Hexagonal / Ports & Adapters)

Core rule: business logic must not depend on infrastructure. Infrastructure depends on business logic.

     ┌─────────────────────────────────────────┐
     │           Infrastructure                │
     │  (HTTP, DB, Queue, Email, S3, ...)      │
     │                                         │
     │     ┌───────────────────────────┐       │
     │     │     Application Layer     │       │
     │     │  (Use cases, Commands)    │       │
     │     │                           │       │
     │     │   ┌─────────────────┐    │       │
     │     │   │  Domain Layer   │    │       │
     │     │   │  (Entities,     │    │       │
     │     │   │  Value Objects, │    │       │
     │     │   │  Domain Events) │    │       │
     │     │   └─────────────────┘    │       │
     │     └───────────────────────────┘       │
     └─────────────────────────────────────────┘
         Dependencies only point INWARD →

Layers

Domain (innermost)

  • Entities: objects with identity and lifecycle (Order, User)
  • Value Objects: immutable, defined by value (Money, Email)
  • Domain Events: things that happened (OrderPlaced, PaymentFailed)
  • Domain Services: stateless logic that spans entities
  • Zero infrastructure imports — no SQLAlchemy, FastAPI, Stripe, etc.

Application

  • Use cases / handlers: orchestrate domain objects
  • Input/output ports (interfaces): what the use case needs from outside
  • No infrastructure imports — depends only on domain + port interfaces

Infrastructure (outermost)

  • Adapters that implement ports: SqlUserRepository, StripePaymentGateway
  • Framework glue: FastAPI routes, Django views, Express controllers
  • Depends on application layer — adapters implement domain/application interfaces

Ports & Adapters

A port is an interface defined in the domain/application layer. An adapter is an infrastructure class that implements a port.

# Port (in application/domain layer)
class UserRepository(Protocol):
    def find_by_id(self, id: UserId) -> User | None: ...
    def save(self, user: User) -> None: ...

# Adapter (in infrastructure layer)
class SqlUserRepository:
    def __init__(self, session: Session) -> None:
        self._session = session

    def find_by_id(self, id: UserId) -> User | None:
        return self._session.get(UserModel, id.value)

    def save(self, user: User) -> None:
        self._session.merge(UserModel.from_domain(user))

Read the full file on GitHub · 130 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. 1mo ago First seen · 130 lines · 36 tokens per session scan A 676bcfbbec80

Subscribe to this mod's changes

clean-architecture is a skill published in the GitHub repository andr-ca/agentharness (1 stars, last pushed 2d ago), licensed MIT. It adds 36 tokens to every session and 1,075 once invoked, about $0.0001 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-08-31.

Related

Other skills, from other repositories

deepstream-sop

Use this skill when building, deploying, evaluating, debugging, or measuring latency for the DeepStream SOP Inference Microservice — a GPU-accelerated FastAPI service that detects whether operators perform assembly-line steps in order via event boundary detection (GEBD) plus VLM classification. Trigger even if the…

NVIDIA/skills · 219 tokens

nemo-fabric-integrate

Use this skill when integrating NVIDIA NeMo Fabric into a consumer application, service, evaluation harness, or platform through the typed Python SDK — translating the consumer's own application, job, or deployment config into an in-memory FabricConfig, choosing the single-invocation convenience API or an explicitly…

NVIDIA/skills · 83 tokens

ambient-healthcare-agent-with-nemotron-voice-agent

Customize NVIDIA Nemotron Voice Agent's Generic Pipecat example for healthcare appointment, five-field patient intake, or custom tool-calling workflows without a separate backend.

NVIDIA/skills · 44 tokens

nemo-fabric-build-adapter

Build, migrate, review, and maintain third-party NVIDIA NeMo Fabric adapters against the public adapter contract. Use when creating adapter or target descriptors, mapping AgentConfig into an agent harness or custom-agent runtime, implementing start/invoke/stop, declaring schemas and capabilities, packaging discovery…

NVIDIA/skills · 87 tokens

earth2studio-create-datasource

Create and validate Earth2Studio data source wrappers (DataSource, ForecastSource, DataFrameSource, ForecastFrameSource) from remote stores. Do NOT use for fetching data with existing sources, model inference, or installation tasks.

NVIDIA/skills · 53 tokens

dynamo-recipe-runner

Select, validate, patch, and deploy existing NVIDIA Dynamo Kubernetes recipes. Use for model/backend/GPU/deployment-mode recipe bring-up; use router-starter for router-only mode work and troubleshoot for broken deployments.

NVIDIA/skills · 49 tokens