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 parisgroup-ai/imersao-ia-setup --skill clean-architecturegit clone --depth 1 https://github.com/parisgroup-ai/imersao-ia-setupWrote 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/parisgroup-ai/imersao-ia-setup/clean-architecture)<a href="https://agentmods.dev/skills/parisgroup-ai/imersao-ia-setup/clean-architecture"><img src="https://agentmods.dev/badge/skills/parisgroup-ai/imersao-ia-setup/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.
<a href="https://agentmods.dev/skills/parisgroup-ai/imersao-ia-setup/clean-architecture"><img src="https://agentmods.dev/badge/skills/parisgroup-ai/imersao-ia-setup/clean-architecture.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00041 | $0.00929 |
| Opus 5 | $0.00020 | $0.00464 |
| Sonnet 5 | $0.00008 | $0.00186 |
| Haiku 4.5 | $0.00004 | $0.00093 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clean Architecture Skill
Directory Structure
Organize by feature/domain, NOT by type:
src/
├── modules/
│ ├── users/
│ │ ├── domain/ # Entities, value objects
│ │ ├── application/ # Use cases, DTOs
│ │ ├── infrastructure/ # Repositories, adapters
│ │ └── presentation/ # Controllers
│ └── orders/
├── shared/
│ ├── domain/
│ ├── infrastructure/
│ └── utils/
└── main.ts
SOLID Principles
S - Single Responsibility: One class = one purpose O - Open/Closed: Extend via interfaces, not modification L - Liskov Substitution: Subtypes replaceable for base types I - Interface Segregation: Many small interfaces > one large D - Dependency Inversion: Depend on abstractions
Layer Rules
Domain (Core)
- Entities, Value Objects, Domain Services
- ZERO external dependencies
export class User {
static create(props: CreateUserProps): User {
return new User(generateId(), new Email(props.email), UserStatus.PENDING);
}
activate(): void {
if (this._status !== UserStatus.PENDING) {
throw new DomainError('Cannot activate');
}
this._status = UserStatus.ACTIVE;
}
}
Application
- Use Cases, DTOs, Port interfaces
- Depends only on Domain
export class CreateUserUseCase {
constructor(
private readonly userRepository: IUserRepository,
private readonly emailService: IEmailService
) {}
async execute(input: CreateUserInput): Promise<CreateUserOutput> {
const existing = await this.userRepository.findByEmail(input.email);
if (existing) throw new UserAlreadyExistsError(input.email);
const user = User.create(input);
await this.userRepository.save(user);
return { id: user.id };
}
}
Infrastructure
- Repository implementations, External adapters
- Implements Application interfaces
export class PrismaUserRepository implements IUserRepository {
constructor(private readonly prisma: PrismaClient) {}
async findByEmail(email: string): Promise<User | null> {
const data = await this.prisma.user.findUnique({ where: { email } });
return data ? UserMapper.toDomain(data) : null;
}
}
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.
- 12d ago First seen · 151 lines · 41 tokens per session scan A ee1f9fd4af55
clean-architecture is a skill published in the GitHub repository parisgroup-ai/imersao-ia-setup (1 stars, last pushed 29d ago), licensed MIT. It adds 41 tokens to every session and 929 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-08-31.
Other skills, from other repositories
design-code-architecture
Guided journey from an app idea to a deliberate architecture: boundaries, domain model, data decisions, and resilience, making only the expensive-to-reverse decisions and deferring the rest. Orchestrates eight skills phase by phase - clean-architecture, domain-driven-design, system-design, ddia-systems…
system-design
Design scalable distributed systems using structured approaches for load balancing, caching, database scaling, and message queues. Use when the user mentions "system design", "scale this", "high availability", "rate limiter", "design a URL shortener", "design Twitter", "design Uber", "design a news feed", "system…
plugin-system
Generic plugin system for Python applications. Auto-discovery, validation, fault tolerance. Zero dependencies (Python stdlib only).
Event-Driven Semantics & Delivery Guarantees
Ensure event-driven designs specify delivery guarantees, ordering, idempotency, schema evolution, and replay/backfill strategy.
External Dependencies & Vendor Risks
Ensure designs document third-party dependencies, SLAs, quotas, failure modes, and vendor lock-in mitigation.
Trust Boundaries & Authorization Architecture
Ensure designs define trust boundaries, authn/authz responsibilities, and propagation of identity/claims across services.