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 Sagargupta16/claude-skills --skill clean-codegit clone --depth 1 https://github.com/Sagargupta16/claude-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/sagargupta16/claude-skills/clean-code)<a href="https://agentmods.dev/skills/sagargupta16/claude-skills/clean-code"><img src="https://agentmods.dev/badge/skills/sagargupta16/claude-skills/clean-code.svg" alt="Measured on agentmods" 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.00066 | $0.01184 |
| Opus 5 | $0.00033 | $0.00592 |
| Sonnet 5 | $0.00013 | $0.00237 |
| Haiku 4.5 | $0.00007 | $0.00118 |
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 7d 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 Code (Python)
"Always leave the campground cleaner than you found it." — Robert Baden-Powell
"Always check a module in cleaner than when you checked it out." — Robert C. Martin, Clean Code
Rule Chapters
Load the chapter that matches the work. Rule IDs (N1, C5, G25, F3, T9...) are defined in these files:
| Chapter | When |
|---|---|
| references/full-catalog.md | Reviewing any Python -- the complete rule index (master) |
| references/names.md | Naming variables, functions, classes, modules |
| references/comments.md | Writing or editing comments and docstrings |
| references/functions.md | Creating or refactoring functions |
| references/general.md | Code quality review -- DRY, intent, abstractions |
| references/tests.md | Writing or reviewing tests |
The Philosophy
You don't have to make every module perfect. You simply have to make it a little bit better than when you found it.
If we all followed this simple rule:
- Our systems would gradually get better as they evolved
- Teams would care for the system as a whole
- The relentless deterioration of software would end
When Working on Code
Every time you touch code, look for at least one small improvement:
Quick Wins (Do These Immediately)
- Rename a poorly named variable → references/names.md
- Delete a redundant comment → references/comments.md
- Remove dead code or unused imports
- Replace a magic number with a named constant
- Extract a deeply nested block into a well-named function
Deeper Improvements (When Time Allows)
- Split a function that does multiple things → references/functions.md
- Remove duplication (DRY) → references/general.md
- Add missing boundary checks
- Improve test coverage → references/tests.md
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.
- 7d ago First seen · 117 lines · 66 tokens per session scan A a2c783dc9082
clean-code is a skill published in the GitHub repository Sagargupta16/claude-skills (5 stars, last pushed yesterday), licensed MIT. It adds 66 tokens to every session and 1,184 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-08-31.
Other skills, from other repositories
python-authoring
Write, edit, refactor, or review Python in easy-cheese with concise stdlib-first code, Python 3.12, Shiv .pyz packaging, and repository test and validation conventions. Use for Python changes under src/, scripts/, .github/scripts/, or tests/, especially when the user asks for Pythonic, succinct, de-slopped…
build-priority-queue
For ordered processing: A search, Dijkstra, event simulation, task scheduling. Efficient min/max extraction with heap-based queue.
cache-recursive-calls
For dynamic programming: overlapping subproblems, recursive solutions with repeated computations, memoization to avoid redundant work.
catch-expected-errors
For iteration with errors: catch exceptions during exploration, skip invalid cases, continue to next attempt.
intern-symbols-identity
For fast comparison: ensure only one instance of each symbol, use 'is' instead of '==', symbol tables for interpreters.
iterate-with-itertools
For combinatorial iteration: permutations, combinations, cartesian products, without storing all results in memory.