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 G1Joshi/Agent-Skills --skill clean-architecturegit clone --depth 1 https://github.com/G1Joshi/Agent-SkillsWrote 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/g1joshi/agent-skills/clean-architecture)<a href="https://agentmods.dev/skills/g1joshi/agent-skills/clean-architecture"><img src="https://agentmods.dev/badge/skills/g1joshi/agent-skills/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/g1joshi/agent-skills/clean-architecture"><img src="https://agentmods.dev/badge/skills/g1joshi/agent-skills/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.00015 | $0.00773 |
| Opus 5 | $0.00008 | $0.00387 |
| Sonnet 5 | $0.00003 | $0.00155 |
| Haiku 4.5 | $0.00002 | $0.00077 |
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 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clean Architecture
Clean Architecture, popularized by Robert C. Martin (Uncle Bob), separates software into layers to ensure independence from frameworks, databases, and UIs. The core principle is the Dependency Rule: source code dependencies can only point inwards.
When to Use
- Building enterprise applications with complex business logic.
- Long-lived projects where frameworks/databases might change over time.
- Large teams requiring clear separation of concerns to work in parallel.
Quick Start
// 1. Entity (Enterprise Logic) - Inner Layer
class User {
constructor(
public id: string,
public name: string,
) {
if (name.length < 2) throw new Error("Name too short");
}
}
// 2. Use Case (Application Logic)
class CreateUserUseCase {
constructor(private userRepository: UserRepository) {} // Depends on interface
async execute(name: string): Promise<User> {
const user = new User(crypto.randomUUID(), name);
await this.userRepository.save(user);
return user;
}
}
// 3. Interface Adapter (Repository Interface)
interface UserRepository {
save(user: User): Promise<void>;
}
// 4. Frameworks & Drivers (Implementation) - Outer Layer
class SqlUserRepository implements UserRepository {
async save(user: User): Promise<void> {
await db.query("INSERT INTO users ...", [user.id, user.name]);
}
}
Core Concepts
The Dependency Rule
Inner layers (Entities) know nothing about outer layers (Controllers, Presenters). Outer layers depend on inner layers.
Entities
Enterprise-wide business rules. These are the least likely to change when something external changes (e.g., page navigation security).
Application Business Rules (Use Cases)
Orchestrate the flow of data to and from the entities. They contain the specific business rules of the application (e.g., "Create Order").
Common Patterns
Dependency Injection
The glue that makes Clean Architecture possible. Outer layers inject concrete implementations (e.g., SqlUserRepository) into inner layers (which expect UserRepository interface).
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 · 101 lines · 15 tokens per session scan A 431bdc3f6145
clean-architecture is a skill published in the GitHub repository G1Joshi/Agent-Skills (12 stars, last pushed 7mo ago), licensed MIT. It adds 15 tokens to every session and 773 once invoked, about $0.0001 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
image-describe
Describe the contents of an image file or URL in structured detail.
pake
Package any website or local web build into a lightweight desktop app using Pake (Tauri/Rust). Use when the user wants to: wrap a URL as a native app, build a desktop app from a website or a local dist/ folder, use Pake CLI to package a page, set up proxy for a packaged app, customize app icons or bundle IDs, or…
ponytail-lazy-senior-dev
Applies the "lazy senior developer" mindset. Use this skill whenever generating, modifying, reviewing code, or fixing bugs to prioritize code reuse, minimalism, YAGNI principles, and root-cause fixes. Also use whenever the user says "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni"…
tdd-explore-ideas
Systematic codebase exploration, architectural critique, and 5-step Idea Assessment with TDD hypothesis verification for Phase 0.
laravel-expert
Laravel & PHP Development Instructions for GitHub Copilot.
orchestrate
Drive a plan to completion by orchestrating implementer, reviewer, and critic agents across waves of parallel work. Use when the user says "orchestrate", "implement this plan", "execute plan", "drive this", or approves a plan for execution.