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 Benknightdark/neo-skills --skill neo-clean-architecturegit clone --depth 1 https://github.com/Benknightdark/neo-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/benknightdark/neo-skills/neo-clean-architecture)<a href="https://agentmods.dev/skills/benknightdark/neo-skills/neo-clean-architecture"><img src="https://agentmods.dev/badge/skills/benknightdark/neo-skills/neo-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/benknightdark/neo-skills/neo-clean-architecture"><img src="https://agentmods.dev/badge/skills/benknightdark/neo-skills/neo-clean-architecture.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.00076 | $0.01219 |
| Opus 5 | $0.00038 | $0.00609 |
| Sonnet 5 | $0.00015 | $0.00244 |
| Haiku 4.5 | $0.00008 | $0.00122 |
Grade A, and why
neo-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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clean Architecture
Design and review software systems using Clean Architecture. The core objective is separating concerns based on their rate of change, directing all source code dependencies inward toward the Domain core.
Gotchas
- Anemic Models: Entities that are mere data containers (only getters/setters) leak business logic. Entities must protect their invariants. State changes must go through explicit, business-oriented methods.
- Pointless Value Objects: Avoid wrapping primitives (e.g., string, number) unless they encapsulate validation (e.g., email format) or behavior (e.g., auto-slug generation).
- Deep Object Graphs: Do not nest full entities for associations. Loading a parent entity will trigger database performance issues. Reference other aggregates using IDs instead.
- Dependency Leakage: Repository interfaces must reside in the Application layer, with implementations in Infrastructure. Never return query streams (e.g.,
IQueryable) to Application, as it leaks database concerns. - Exception Control Flow: Do not throw runtime exceptions for expected business failures (e.g., duplicate title, user not found). Use the Result pattern for flow control.
Workflow Checklist
Progress:
- Step 1: Analyze Core & Boundaries (See
references/design_principles.md). - Step 2: Design Domain Layer (Build entities and value objects; protect invariants).
- Step 3: Design Application Layer (Define use case handlers, CQRS inputs, and repository interfaces).
- Step 4: Implement Outer Layers (Implement database mapping, external services, and API controllers).
- Step 5: Audit Architecture Health (Use
assets/review_checklist.mdto scan code).
Detailed Guidelines
Step 1 — Analyze Core & Boundaries
- Categorize business rules:
- Domain Layer: Core rules that would exist even without a computer system.
- Application Layer: System orchestration, workflows, and protocols.
- Outer Layers (Infrastructure/Presentation): Delivery mechanisms and persistence details.
- Read design_principles.md for architectural details.
What ships with it
6 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.
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 · 117 lines · 76 tokens per session scan A 06e95e9d0289
neo-clean-architecture is a skill published in the GitHub repository Benknightdark/neo-skills (7 stars, last pushed 6d ago), licensed MIT. It adds 76 tokens to every session and 1,219 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
html-portal-generator
Convert a codebase into a self-contained HTML portal app for ingestion into AI application systems. Produces a single deployable HTML file with embedded CSS, JS, and data.
api-designer
Design RESTful APIs with best practices for consistency and usability.
test-writer
Write thorough tests following TDD and BDD principles.
coding-assistant
Provides coding assistance with best practices and code review.
debug-helper
Systematic debugging approach for identifying and fixing issues.
git-workflow
Git best practices for version control and collaboration.