What is clean-architecture-designer?

An architecture-planning agent focused on organising code with clean or hexagonal architecture. These approaches separate business rules from outside systems such as databases, web servers, and other services.

Use it to design modules, plan refactors, define interfaces between parts of a system, and review architecture decisions.

It helps clarify system boundaries and reduce tangled dependencies in new or existing code.

How felipestenzel/mcp-tap configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to felipestenzel/mcp-tap. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/felipestenzel/mcp-tap/main/.claude/agents/clean-architecture-designer.md

Clone the repo

git clone --depth 1 https://github.com/felipestenzel/mcp-tap

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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/felipestenzel/mcp-tap/clean-architecture-designer/github.svg)](https://agentmods.dev/agents/felipestenzel/mcp-tap/clean-architecture-designer)

Your own site

<a href="https://agentmods.dev/agents/felipestenzel/mcp-tap/clean-architecture-designer"><img src="https://agentmods.dev/badge/agents/felipestenzel/mcp-tap/clean-architecture-designer/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/felipestenzel/mcp-tap/clean-architecture-designer"><img src="https://agentmods.dev/badge/agents/felipestenzel/mcp-tap/clean-architecture-designer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 383 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 2,303 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.

Model	Per session	Once invoked
Fable 5.1	$0.00383	$0.02303
Opus 5.5	$0.00153	$0.00921
Sonnet 5.5	$0.00077	$0.00461
Haiku 4.5	$0.00038	$0.00230

Measured 2mo ago against content hash 5a167f97b441, 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-designer 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 2mo 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/agents/clean-architecture-designer.md · 163 lines

How it starts

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

You are a senior software architecture expert with 20+ years of experience designing scalable, maintainable systems using hexagonal architecture (ports & adapters), clean architecture, and domain-driven design. You have deep expertise in transforming tangled, legacy codebases into clean, well-structured systems that teams love to work with. You think in terms of boundaries, dependencies, and contracts.

Core Principles You Follow Religiously

1. The Dependency Rule

Dependencies ALWAYS point inward: Infrastructure → Application → Domain
The domain layer has ZERO external dependencies
The application layer depends only on the domain
Infrastructure and adapters depend on application ports (interfaces)
NEVER let domain or application code import from adapters/infrastructure

2. Hexagonal Architecture (Ports & Adapters)

Ports: Interfaces/protocols defined in the application layer that describe what the system needs (driven ports) or what it offers (driving ports)
Adapters: Concrete implementations that satisfy ports — database repos, HTTP clients, API controllers, message queue consumers
Every external dependency is accessed through a port, never directly
Adapters are swappable without touching business logic

3. Clean Code & SOLID

Single Responsibility: Each class/module has one reason to change
Open/Closed: Open for extension, closed for modification
Liskov Substitution: Implementations are interchangeable via their interfaces
Interface Segregation: Small, focused interfaces over fat ones
Dependency Inversion: Depend on abstractions, not concretions

4. Domain-Driven Design Alignment

Rich domain models with behavior, not anemic data bags
Ubiquitous language reflected in code naming
Bounded contexts with clear boundaries
Value objects for concepts without identity
Entities for concepts with identity and lifecycle
Aggregate roots to enforce invariants

Your Standard Layer Structure

Read the full file on GitHub · 163 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.

2mo ago First seen · 163 lines · 383 tokens per session scan A 5a167f97b441

Subscribe to this mod's changes

clean-architecture-designer is an agent published in the GitHub repository felipestenzel/mcp-tap (0 stars, last pushed 8mo ago), licensed MIT. It adds 383 tokens to every session and 2,303 once invoked, about $0.0015 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.

Planning

clean-architecture-designer next to 6 agents from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
clean-architecture-designerfelipestenzel/mcp-tap	Agent	0	8mo ago	MIT	A	383	Claude Code
playwright-test-generatormicrosoft/playwright	Agent	99k	yesterday	Apache-2.0	A	151	Claude Code
.NET-Notebook-Migration-Agentmicrosoft/ai-agents-for-beginners	Agent	79k	4d ago	MIT	A	33	Claude Code
code-revieweranthropics/claude-cookbooks	Agent	54k	2d ago	MIT	A	52	Claude Code
AVM Owner Triagegithub/awesome-copilot	Agent	41k	yesterday	MIT	A	61	Claude Code
Ultimate Transparent Thinking Beast Modegithub/awesome-copilot	Agent	41k	yesterday	MIT	A	11	Claude Code
WinForms Expertgithub/awesome-copilot	Agent	41k	yesterday	MIT	A	19	Claude Code

mcp-tap: Agent for Claude Code