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 agentmods add skills/andr-ca/agentharness/clean-architecturenpx skills add andr-ca/agentharness --skill clean-architecturegit clone --depth 1 https://github.com/andr-ca/agentharnessWrote 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/andr-ca/agentharness/clean-architecture)<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="Measured on agentmods" 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 | $0.00036 | $0.01075 |
| Opus 5 | $0.00018 | $0.00537 |
| Sonnet 5 | $0.00007 | $0.00215 |
| Haiku 4.5 | $0.00004 | $0.00108 |
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 4d 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 — 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))
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.
- 4d ago First seen · 130 lines · 36 tokens per session scan A 676bcfbbec80
clean-architecture is a skill published in the GitHub repository andr-ca/agentharness (1 stars, last pushed yesterday), licensed MIT. It adds 36 tokens to every session and 1,075 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
kami-deck
A lab-meeting deck on gut-microbiome links to sleep quality — the design, the results, the caveats, and the next experiment. Built as a decision-grade academic research deck for lab group, PI.
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
fs-editorial-forest
Art-directing a fashion house's annual report — the editorial system, the photography rhythm, and the data spreads. Built as a decision-grade design craft deck for brand stakeholders, exec audience.
html-ppt-zhangzara-stencil-tablet
A workplace-safety compliance review for a manufacturing regulator — findings, the evidence chain, and the corrective mandate. Built as a decision-grade policy briefing deck for regulator, plant leadership.
simple-deck
OpenDesign's operating review: growth, burn, and the concrete path to sustainability without losing the open ethos. Built as a decision-grade corporate strategy deck for leadership team.
html-ppt-zhangzara-coral
OpenDesign's community-growth campaign across GitHub, Discord, and X: the loops, the content calendar, and the pipeline math. Built as a decision-grade marketing & GTM deck for growth team, community lead.