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 pproenca/dot-skills --skill clean-codegit clone --depth 1 https://github.com/pproenca/dot-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/pproenca/dot-skills/clean-code)<a href="https://agentmods.dev/skills/pproenca/dot-skills/clean-code"><img src="https://agentmods.dev/badge/skills/pproenca/dot-skills/clean-code/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/pproenca/dot-skills/clean-code"><img src="https://agentmods.dev/badge/skills/pproenca/dot-skills/clean-code.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- 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.00052 | $0.01711 |
| Opus 5 | $0.00026 | $0.00856 |
| Sonnet 5 | $0.00010 | $0.00342 |
| Haiku 4.5 | $0.00005 | $0.00171 |
Grade A, and why
clean-code 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 5d 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Robert C. Martin (Uncle Bob) Clean Code Best Practices
Comprehensive software craftsmanship guide based on Robert C. Martin's "Clean Code: A Handbook of Agile Software Craftsmanship", updated with modern corrections where the original 2008 advice has been superseded. Contains 48 rules across 10 categories, prioritized by impact to guide code reviews, refactoring decisions, and new development. Examples are primarily in Java but principles are language-agnostic.
When to Apply
Reference these guidelines when:
- Writing new functions, classes, or modules
- Naming variables, functions, classes, or files
- Reviewing code for maintainability issues
- Refactoring existing code to improve clarity
- Writing or improving unit tests
- Wrapping third-party dependencies
Rule Categories by Priority
| Priority | Category | Impact | Prefix |
|---|---|---|---|
| 1 | Meaningful Names | CRITICAL | name- |
| 2 | Functions | CRITICAL | func- |
| 3 | Comments | HIGH | cmt- |
| 4 | Formatting | HIGH | fmt- |
| 5 | Error Handling | HIGH | err- |
| 6 | Objects and Data Structures | MEDIUM-HIGH | obj- |
| 7 | Boundaries | MEDIUM-HIGH | bound- |
| 8 | Classes and Systems | MEDIUM-HIGH | class- |
| 9 | Unit Tests | MEDIUM | test- |
| 10 | Emergence and Simple Design | MEDIUM | emerge- |
Quick Reference
1. Meaningful Names (CRITICAL)
name-intention-revealing- Use names that reveal intentname-avoid-disinformation- Avoid misleading namesname-meaningful-distinctions- Make meaningful distinctionsname-pronounceable- Use pronounceable namesname-searchable- Use searchable namesname-avoid-encodings- Avoid encodings in namesname-class-noun- Use noun phrases for class namesname-method-verb- Use verb phrases for method names
What ships with it
51 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.
- assets/templates/_template.md 773 B
- metadata.json 961 B
- references/_sections.md 2.2 KB
- references/bound-learning-tests.md 1.9 KB
- references/bound-wrap-third-party.md 2.4 KB
- references/class-cohesion.md 2.0 KB
- references/class-isolate-from-change.md 2.1 KB
- references/class-organize-for-change.md 1.9 KB
- references/class-separate-concerns.md 2.4 KB
- references/class-small.md 2.1 KB
- references/cmt-avoid-commented-out-code.md 1.4 KB
- references/cmt-avoid-redundant.md 1.4 KB
- references/cmt-explain-intent.md 1.6 KB
- references/cmt-express-in-code.md 1.8 KB
- references/cmt-warning-consequences.md 1.9 KB
- references/emerge-expressiveness.md 1.7 KB
- references/emerge-simple-design.md 2.2 KB
- references/err-avoid-null.md 2.2 KB
- references/err-define-by-caller-needs.md 1.8 KB
- references/err-provide-context.md 1.6 KB
- references/err-use-exceptions.md 3.0 KB
- references/err-write-try-catch-first.md 1.8 KB
- references/fmt-horizontal-alignment.md 1.7 KB
- references/fmt-indentation.md 1.5 KB
- references/fmt-team-rules.md 1.5 KB
- references/fmt-vertical-formatting.md 2.1 KB
- references/func-abstraction-level.md 2.3 KB
- references/func-command-query-separation.md 1.5 KB
- references/func-dry.md 2.7 KB
- references/func-minimize-arguments.md 1.7 KB
- references/func-no-side-effects.md 2.4 KB
- references/func-one-thing.md 2.5 KB
- references/func-small.md 2.9 KB
- references/name-avoid-disinformation.md 1.2 KB
- references/name-avoid-encodings.md 1.8 KB
- references/name-class-noun.md 1.3 KB
- references/name-intention-revealing.md 1.5 KB
- references/name-meaningful-distinctions.md 1.4 KB
- references/name-method-verb.md 1.8 KB
- references/name-pronounceable.md 1.1 KB
- references/name-searchable.md 1.2 KB
- references/obj-avoid-hybrids.md 1.9 KB
- references/obj-data-abstraction.md 1.8 KB
- references/obj-data-object-asymmetry.md 2.0 KB
- references/obj-dto.md 1.9 KB
- references/obj-law-of-demeter.md 1.5 KB
- references/test-build-operate-check.md 1.8 KB
- references/test-first-law.md 1.7 KB
- references/test-first-principles.md 2.0 KB
- references/test-keep-clean.md 1.7 KB
- references/test-one-assert.md 2.3 KB
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.
- 5d ago First seen · 129 lines · 52 tokens per session scan A fad8fb133e02
clean-code is a skill published in the GitHub repository pproenca/dot-skills (205 stars, last pushed 24d ago), licensed MIT. It adds 52 tokens to every session and 1,711 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
test-review
You are an expert DataHub test reviewer. Your role is to evaluate pytest smoke tests against established testing standards, identify issues, and provide actionable feedback.
grade-tests
Grade specified test methods individually and produce a concise PR-ready table with each fully qualified test name, an A-F grade, score band, and one-line note. USE FOR per-test feedback on a curated list such as new or modified tests in a pull request, not a suite-wide audit. Polyglot: .NET, Python, TS/JS, Java, Go…
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
quality-checklist
Validate implementation quality through custom checklists, scoring against constitution standards, specification coverage, and producing remediation recommendations.
brooks-test
Test quality review drawing on twelve classic engineering books — with primary focus on xUnit Test Patterns, The Art of Unit Testing, How Google Tests Software, and Working Effectively with Legacy Code — that diagnoses structural problems in an existing test suite: brittleness, mock abuse, coverage illusions, slow…
refactor
Refactors code for quality and maintainability. Triggers: refactor, clean up, restructure, improve code, modernize.