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 SebastienDegodez/copilot-instructions --skill clean-architecture-dotnetgit clone --depth 1 https://github.com/SebastienDegodez/copilot-instructionsWrote 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/sebastiendegodez/copilot-instructions/clean-architecture-dotnet)<a href="https://agentmods.dev/skills/sebastiendegodez/copilot-instructions/clean-architecture-dotnet"><img src="https://agentmods.dev/badge/skills/sebastiendegodez/copilot-instructions/clean-architecture-dotnet/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/sebastiendegodez/copilot-instructions/clean-architecture-dotnet"><img src="https://agentmods.dev/badge/skills/sebastiendegodez/copilot-instructions/clean-architecture-dotnet.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.00050 | $0.04628 |
| Opus 5 | $0.00025 | $0.02314 |
| Sonnet 5 | $0.00010 | $0.00926 |
| Haiku 4.5 | $0.00005 | $0.00463 |
Grade A, and why
clean-architecture-dotnet 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 10d 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 — 393 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clean Architecture in .NET
Overview
Clean Architecture organizes code into independent layers (Domain → Application → Infrastructure → API).
The Iron Law: Violating layer boundaries is a failure. If API references Application or Domain references Infrastructure, delete the change and start over.
Concrete violations that break the Iron Law:
using MyApp.Infrastructure;in a Domain class — Infrastructure must never flow inward.using MyApp.Application;in an API endpoint file — API must only interact viaICommandBus/IQueryBusor an injected use case interface.new AppDbContext()inside a Controller — bypasses both Infrastructure and Application layers.HttpClientinjected directly into a Domain or Application class — HTTP belongs in Infrastructure behind an interface.Fix: move the dependency to the correct outer layer and expose it through an interface pointing inward.
When to Use
- Business logic is leaking into Controllers or Repositories
- Circular dependencies occur between projects
- Need to isolate core business rules from external frameworks (EF Core, APIs)
- Autonomy is required: sealed Domain objects, strongly-typed IDs
When NOT to add CQRS or DDD:
- The feature is pure CRUD with no business rules, no invariants, and no domain events → use a CQS Application service (see Pattern A below)
- A query only reads data with no domain logic → inject the repository or a read service directly in the Application handler; no
IQueryBusrequired - You have fewer than 3 use cases with no cross-cutting concerns (logging pipeline, validation pipeline) → a CQRS bus adds ceremony without value
CQS vs CQRS vs DDD — Complexity Threshold
These three patterns are independent tools. Choose based on what the codebase actually needs.
| Pattern | Rule | Add it when… | Skip it when… |
|---|---|---|---|
| CQS (always) | Every handler/method is either a command (void) or a query (returns value) — never both | Always — zero exceptions | Never skip |
| CQRS + Bus (optional) | Separate ICommandBus / IQueryBus routing commands and queries through a pipeline |
Cross-cutting concerns (validation, logging pipelines), large teams writing many use cases, read/write model asymmetry | Simple CRUD; < 3 use cases; no cross-cutting pipeline needed |
| DDD (optional) | Aggregates, factory methods, value objects, domain events | Domain has invariants (rules that must be enforced on every state change), state machines, rich business logic | Entities are pure data (no if/throw to protect state); CRUD-only feature |
What ships with it
26 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.
- references/architecture-layers.md 1.6 KB
- references/convention-based-di.md 11 KB
- references/cqrs-patterns.md 3.1 KB
- references/ddd.md 10 KB
- references/interface-placement.md 9.0 KB
- references/layer-responsibilities.md 14 KB
- references/netarchtest-rules.md 10 KB
- references/project-structure.md 1.7 KB
- references/shared-kernel.md 5.8 KB
- scripts/init-project.ps1 15 KB runs code
- scripts/init-project.sh 7.2 KB runs code
- templates/Api/IApiMarker.cs 179 B
- templates/Application/IApplicationMarker.cs 211 B
- templates/Application/Shared/ICommandBus.cs 375 B
- templates/Application/Shared/ICommandHandler.cs 514 B
- templates/Application/Shared/IQueryBus.cs 265 B
- templates/Application/Shared/IQueryHandler.cs 264 B
- templates/Domain/IDomainMarker.cs 191 B
- templates/Infrastructure/CQRS/CommandBus.cs 1.1 KB
- templates/Infrastructure/CQRS/QueryBus.cs 789 B
- templates/Infrastructure/DependencyInjection.cs 1.8 KB
- templates/Infrastructure/IInfrastructureMarker.cs 223 B
- templates/IntegrationTests/ArchitectureTests.cs 4.4 KB
- tests/baseline-prompts.txt 2.2 KB
- tests/README.md 3.8 KB
- tests/validation.md 18 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.
- 10d ago First seen · 393 lines · 50 tokens per session scan A 5ca6cb7bf77b
clean-architecture-dotnet is a skill published in the GitHub repository SebastienDegodez/copilot-instructions (193 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 50 tokens to every session and 4,628 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-08-30.
Other skills, from other repositories
worker-services
Build long-running .NET background services with BackgroundService, Generic Host, graceful shutdown, configuration, logging, and deployment patterns suited to workers and daemons. USE FOR: background services; scheduled workers; hosted services; worker extraction; graceful shutdown, health checks, and service hosting…
minimal-apis
Design and implement Minimal APIs in ASP.NET Core using handler-first endpoints, route groups, filters, and lightweight composition suited to modern .NET services. USE FOR: building new HTTP APIs in ASP.NET Core; creating lightweight microservices; choosing between Minimal APIs and controllers. DO NOT USE FOR…
aspnet-core
Build, debug, modernize, or review ASP.NET Core applications with correct hosting, middleware, security, configuration, logging, and deployment patterns on current .NET. USE FOR: working on ASP.NET Core apps, services, or middleware; changing auth, routing, configuration, hosting, or deployment behavior; deciding…
web-api
Build or maintain controller-based ASP.NET Core APIs when the project needs controller conventions, advanced model binding, validation extensions, OData, JsonPatch, or existing API patterns. USE FOR: working on controller-based APIs in ASP.NET Core; needing controller-specific extensibility or conventions; migrating…
managedcode-communication
Use ManagedCode.Communication when a .NET application needs explicit result objects, structured errors, and predictable service or API boundaries instead of exception-driven control flow. USE FOR: integrating ManagedCode.Communication into services or APIs; replacing exception-driven result handling with explicit…
grpc
Build or review gRPC services and clients in .NET. USE FOR: ASP.NET Core gRPC, protobuf contracts, unary or streaming RPC, gRPC client factory, interceptors, deadlines, cancellation, channel reuse, backend service integration. DO NOT USE FOR: broad browser-facing APIs without gRPC-Web tradeoff review, SignalR realtime…