Borrowing it
Nothing to install: this file belongs to tiagosilva07/zyrax-guard. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/tiagosilva07/zyrax-guard/main/.agents/skills/clean-architecture/SKILL.mdgit clone --depth 1 https://github.com/tiagosilva07/zyrax-guardWrote 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/tiagosilva07/zyrax-guard/clean-architecture)<a href="https://agentmods.dev/skills/tiagosilva07/zyrax-guard/clean-architecture"><img src="https://agentmods.dev/badge/skills/tiagosilva07/zyrax-guard/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/tiagosilva07/zyrax-guard/clean-architecture"><img src="https://agentmods.dev/badge/skills/tiagosilva07/zyrax-guard/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.00083 | $0.00723 |
| Opus 5 | $0.00042 | $0.00362 |
| Sonnet 5 | $0.00017 | $0.00145 |
| Haiku 4.5 | $0.00008 | $0.00072 |
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 11d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clean architecture (applied, not dogmatic)
The goal is code that's easy to change safely. Use these principles as a lens, not a religion — apply the ones that reduce real coupling, skip ceremony that doesn't.
Core principles
- Separate concerns by responsibility. Transport (HTTP/handlers), business logic (services/use-cases), and data access (repositories) are three different jobs. Keep them in different units so a change to one doesn't ripple into the others.
- Depend inward, on abstractions. Business logic should not import the database driver or the web framework. Define interfaces it needs; let the outer layers implement them. Dependencies point toward the domain, never out of it.
- High cohesion, low coupling. Things that change together live together; things that don't, don't. A package/module should have one clear reason to exist.
- No leaky boundaries. Don't pass framework types (HTTP requests, ORM entities) into business logic. Translate at the edge.
- Single source of truth. One place for each piece of logic. Duplication is a bug waiting to diverge.
When structuring or refactoring, check:
- Can I describe each unit's single responsibility in one sentence? If not, split it.
- Does business logic depend on a concrete framework/DB? Invert it behind an interface.
- Is the same logic in more than one place? Consolidate.
- Could I swap the database or the web layer without touching business rules? That's the test for whether boundaries are clean.
- Am I adding a layer that doesn't pull its weight? Remove it. Simplicity wins.
Stack-specific shape
Go
/cmd entrypoints
/internal
/transport http handlers, routing, request/response mapping
/service business logic, depends on repo interfaces
/repository data access, implements interfaces
/domain core types, no external imports
Define repository interfaces in the service layer (consumer side), implement them in
/repository. Wrap errors with context as they cross boundaries.
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.
- 11d ago First seen · 71 lines · 83 tokens per session scan A ec1fad015165
clean-architecture is a skill published in the GitHub repository tiagosilva07/zyrax-guard (2 stars, last pushed 1mo ago), licensed MIT. It adds 83 tokens to every session and 723 once invoked, about $0.0004 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
cve
Look up CVE records via x cve — cached, zero-API-key, daily xz TSV. Load for cve, vulnerability id, kev, epss, nvd, cvelist, or security advisory.
wikipedia
Search and read Wikipedia via x wkp — MediaWiki API, no API key, zero install; query, extract, suggest, and DDG route in one module. Load for wiki, wikipedia, encyclopedia lookup, article summary.
voiden
Create and edit Voiden .void files for API testing. Covers the .void file format and all enabled extension block types.
lap
LAP CLI -- compile, search, and manage API specs for AI agents. Use when working with API specifications (OpenAPI, GraphQL, AsyncAPI, Protobuf, Postman), compiling specs to LAP format, searching the LAP registry, generating skills from API specs, or publishing APIs. Commands: init, compile, search, get, skill…
scaffold-project
Scaffold a new app, API, backend, fullstack project, mobile app, polyglot service, monorepo, or starter with Better Fullstack. Use when the user wants to create, start, bootstrap, initialize, or generate a project from a stack description. Prefer the bundled Better Fullstack MCP server: guidance, schema…
migrate-k2-nintex
Assess and migrate K2 / Nintex K2 applications to Mendix — SmartObjects to domain models, SmartForms to pages, K2 workflows to microflows and Mendix workflows. Use when analysing or converting a K2 application.