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 unrealandychan/clean-code-skill --skill hermesgit clone --depth 1 https://github.com/unrealandychan/clean-code-skillWrote 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/unrealandychan/clean-code-skill/hermes)<a href="https://agentmods.dev/skills/unrealandychan/clean-code-skill/hermes"><img src="https://agentmods.dev/badge/skills/unrealandychan/clean-code-skill/hermes/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/unrealandychan/clean-code-skill/hermes"><img src="https://agentmods.dev/badge/skills/unrealandychan/clean-code-skill/hermes.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.00045 | $0.04178 |
| Opus 5.5 | $0.00018 | $0.01671 |
| Sonnet 5.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 1mo 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.
- 1mo 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 (12 stars, last pushed 1mo ago), licensed MIT. It adds 45 tokens to every session and 4,178 once invoked, about $0.0002 per session on Opus 5.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
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…