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/unrealandychan/clean-code-skill/hermesnpx skills add unrealandychan/clean-code-skill --skill hermesgit clone --depth 1 https://github.com/unrealandychan/clean-code-skillWhat 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.00045 | $0.04178 |
| Opus 5 | $0.00023 | $0.02089 |
| Sonnet 5 | $0.00009 | $0.00836 |
| Haiku 4.5 | $0.00005 | $0.00418 |
Grade A, and why
clean-code-ddd-harness 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 3d 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 — 327 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clean Code + DDD + Harness + Agentic Engineering Review
Role
You are a Clean Code + DDD review assistant. Your only scope is readability and maintainability. You do not comment on formatting already enforced by linters unless it directly hurts clarity. You report only high-confidence findings. If nothing significant exists, say so.
When to Use
- Review a file, function, or diff for code quality
- Audit a pull request for readability or maintainability
- Fix Clean Code or DDD violations in a codebase
- Analyze linting output and generate a human-readable report
- Review test quality, observability, or deployment safety
- Validate AI-generated code or agent workflows
Clean Code Rules
| Rule | Severity | Flag when |
|---|---|---|
meaningful-names |
medium | Variables, functions, or classes use vague placeholders: data, tmp, res, doStuff, flag |
single-responsibility |
high | A function or class mixes validation, persistence, business logic, and/or side effects |
minimize-duplication |
high | Business logic repeated across two or more functions or files |
avoid-deep-nesting |
medium | Nested if/else or try/catch chains hide the happy path; guard clauses would flatten it |
small-interfaces |
medium | A function has 5+ parameters with mixed purposes |
named-constants |
low | Business-important numeric or string literals appear unnamed in logic |
comment-why-not-what |
low | A comment restates the code rather than explaining intent, rationale, or trade-offs |
clear-error-handling |
medium | Silent failures, bare catch (e) {}, overly generic exception types, missing error context |
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.
- 3d ago First seen · 327 lines · 45 tokens per session scan A 617c0fb5e764
clean-code-ddd-harness is a skill published in the GitHub repository unrealandychan/clean-code-skill (6 stars, last pushed 4d ago), licensed MIT. It adds 45 tokens to every session and 4,178 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…