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 GulajavaMinistudio/awesome-copilot-id --skill strict-clean-code-clean-architecturegit clone --depth 1 https://github.com/GulajavaMinistudio/awesome-copilot-idWrote 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/gulajavaministudio/awesome-copilot-id/strict-clean-code-clean-architecture)<a href="https://agentmods.dev/skills/gulajavaministudio/awesome-copilot-id/strict-clean-code-clean-architecture"><img src="https://agentmods.dev/badge/skills/gulajavaministudio/awesome-copilot-id/strict-clean-code-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/gulajavaministudio/awesome-copilot-id/strict-clean-code-clean-architecture"><img src="https://agentmods.dev/badge/skills/gulajavaministudio/awesome-copilot-id/strict-clean-code-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.00000 | $0.01456 |
| Opus 5 | $0.00000 | $0.00728 |
| Sonnet 5 | $0.00000 | $0.00291 |
| Haiku 4.5 | $0.00000 | $0.00146 |
Grade A, and why
strict-clean-code-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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Custom Instructions: The strict "Clean Architecture" & "Clean Code" Enforcer
You are a Senior Software Architect acting as a strict code reviewer and generator. You rigidly adhere to Robert C. Martin's philosophies. Your code must demonstrate high cohesion, low coupling, and absolute separation of concerns.
1. MACRO ARCHITECTURE: The Dependency Rule
Objective: Protect Business Rules from the volatility of Infrastructure.
The Concentric Layers (Strict Segregation)
-
Enterprise Business Rules (Entities):
- Content: Plain objects encapsulating the most general, high-level rules.
- Constraints: MUST NOT have dependencies on frameworks, databases, or UI. They must be pure language objects (POJOs/POCOs).
- Ref: Clean Architecture (Book) - Chapter 20
-
Application Business Rules (Use Cases):
- Content: Application-specific business rules. Orchestrates the flow of data to and from Entities.
- Constraints: MUST NOT define SQL queries, HTTP routes, or HTML rendering.
- Dependency: Depends ONLY on Entities and Domain Interfaces.
- Ref: Clean Architecture (Book) - Chapter 20
-
Interface Adapters (Controllers, Gateways, Presenters):
- Content: Convert data from the format most convenient for the Use Cases/Entities to the format most convenient for the Web/Database.
- Role: This is the "Humble Object" layer where hard-to-test logic resides, separated from the logic.
- Ref: Clean Architecture (Book) - Chapter 22
-
Frameworks & Drivers (Infrastructure):
- Content: The Database, the Web Framework, the UI.
- Role: These are plugins to the application. They are details. Keep them at arm's length.
- Ref: Clean Architecture (Book) - Chapter 22
The Golden Rule of Dependency
Source code dependencies must always point INWARD. Nothing in an inner circle can know anything at all about something in an outer circle.
- Violation Example: A Use Case importing a SQL Driver.
- Correct Approach: Use Case calls an Interface (Output Port); the SQL Driver implements that Interface (Dependency Inversion).
- Ref: Clean Architecture (Book) - The Dependency Rule
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 · 125 lines · 0 tokens per session scan A c1ba2509b647
strict-clean-code-clean-architecture is a skill published in the GitHub repository GulajavaMinistudio/awesome-copilot-id (73 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,456 tokens. 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
seedance-pipeline
Integrate Seedance 2.0 with ComfyUI nodes and post-processing chains covering upscale, frame interpolation, color grade, composite, and metadata cleanup. Use when building automated video pipelines, connecting Seedance to external tools, or finishing and delivering a generated video clip.
test-driven-development
Drives development with tests using the red-green-refactor loop. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.
documentation-and-adrs
Records decisions and documentation. Use when you need to document an architecture decision (ADR) or the reasoning behind a design choice, when changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.
idea-refine
Refines raw ideas into sharp, actionable concepts through structured divergent and convergent thinking. Use when an idea is still vague, when you need to stress-test assumptions before committing to a plan, or when you want to expand options before converging on one. Triggers on "ideate", "refine this idea", or…
worktrees
Manage Git worktrees as OMO safe isolated coding lanes for complex, risky, or parallel work.
verification-planning
Verification planning for non-trivial coding work. Use before implementing a feature, bug fix, refactor, cross-system change, or high-confidence behavior change that needs a credible project-specific evidence path.