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/amartuvshins0404/clean-code-skills/clean-codenpx skills add Amartuvshins0404/clean-code-skills --skill clean-codegit clone --depth 1 https://github.com/Amartuvshins0404/clean-code-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/amartuvshins0404/clean-code-skills/clean-code)<a href="https://agentmods.dev/skills/amartuvshins0404/clean-code-skills/clean-code"><img src="https://agentmods.dev/badge/skills/amartuvshins0404/clean-code-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 | $0.00050 | $0.03069 |
| Opus 5 | $0.00025 | $0.01535 |
| Sonnet 5 | $0.00010 | $0.00614 |
| Haiku 4.5 | $0.00005 | $0.00307 |
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 4d 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 — 353 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clean Code
Clean code is code that makes its intent, behavior, boundaries, and failure modes easy for the next maintainer to understand and safely change.
This skill is language-agnostic. It does not mean "write Java everywhere" or "add object-oriented patterns everywhere." It means adapt clean-code principles to the project's language, framework, runtime, and local style.
For chapter-by-chapter depth, use references/chapter-map.md. It maps the full 17-chapter clean-code structure, concurrency appendix, legacy refactoring appendix, and heuristic cross-references into agent checklists.
For cross-canon principles drawn from peer-reviewed papers and other widely-cited engineering books (Parnas, Dijkstra, Knuth, Brooks, Hickey, Ousterhout, Hunt/Thomas, Martin, Fowler, GoF, McConnell, Software Engineering at Google), use references/canon.md. Reach for it when a decision concerns complexity, change, scale, optimization, or interface design and the chapter map is not enough.
When To Use
Use this skill for:
- new features
- bug fixes
- refactors
- tests
- reviews
- scripts and automation
- SQL and data transformations
- infrastructure as code
- UI components
- backend services
- libraries and public APIs
Use a lighter version for trivial edits, but still avoid unrelated changes.
Operating Loop
1. Frame The Change
Before editing, identify:
- the exact behavior or maintainability problem being solved
- assumptions that could change the implementation
- the smallest useful scope
- the verification command or manual check that will prove the change
Ask a question only when ambiguity changes the implementation. Otherwise state the assumption and proceed.
2. Read Local Context
Inspect the nearby code before changing it:
- naming vocabulary
- module and file boundaries
- error handling style
- test style and fixtures
- dependency patterns
- formatting conventions
- framework idioms
Local consistency beats generic preference.
3. Change The Smallest Slice
What ships with it
4 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.
- 4d ago First seen · 353 lines · 50 tokens per session scan A ae3e1c95fdff
clean-code is a skill published in the GitHub repository Amartuvshins0404/clean-code-skills (2 stars, last pushed 4mo ago), licensed MIT. It adds 50 tokens to every session and 3,069 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
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…