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 GktuOktay/ai-skills --skill clean-code-reviewergit clone --depth 1 https://github.com/GktuOktay/ai-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/gktuoktay/ai-skills/clean-code-reviewer)<a href="https://agentmods.dev/skills/gktuoktay/ai-skills/clean-code-reviewer"><img src="https://agentmods.dev/badge/skills/gktuoktay/ai-skills/clean-code-reviewer/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/gktuoktay/ai-skills/clean-code-reviewer"><img src="https://agentmods.dev/badge/skills/gktuoktay/ai-skills/clean-code-reviewer.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.00068 | $0.00450 |
| Opus 5.5 | $0.00027 | $0.00180 |
| Sonnet 5.5 | $0.00014 | $0.00090 |
| Haiku 4.5 | $0.00007 | $0.00045 |
Grade A, and why
clean-code-reviewer 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.
What it actually says
Clean Code & Production-Grade Code Reviewer
This skill eliminates technical debt and maximizes maintainability, readability, type safety, and production-grade code quality through deep code reviews, Google engineering standards, and refactoring patterns.
🧹 Refactoring & Engineering Principles
1. SOLID & Clean Code Standards
- Single Responsibility (SRP): Split overloaded files/functions into modular components.
- DRY (Don't Repeat Yourself): Abstract duplicate code into reusable helpers or hooks.
- KISS & YAGNI: Avoid over-engineering; simplify overly complex abstractions.
2. Addy Osmani Production-Grade Standards
- Zero Implicit State Mutation: Never mutate global or private third-party state directly; keep mutations scoped and immutable.
- Strict Guard Clauses: Flatten nested
if/elseloops using early returns and validation gates. - Explicit Error Boundaries: Never swallow exceptions or return dummy fallbacks silently; handle errors gracefully or propagate.
- Type Safety Discipline: Remove all
anytypes; enforce strict TypeScript types and type guards.
3. Complexity Reduction & Naming
- Intent-Revealing Naming: Replace vague variables (
data,temp,x) with domain-specific names. - Memory & Resource Safety: Verify that all subscriptions, timers, and listeners have proper cleanup hooks.
Output Template
- 🔍 Code Review Findings: Code strengths, anti-patterns, and technical debt detected.
- 🔄 Refactoring Proposal (Before / After):
- Before: Problematic code.
- After: Refactored, production-ready Clean Code.
- ⚡ Impact & Benefits: Performance, readability, and maintenance advantages gained.
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 · 40 lines · 68 tokens per session scan A 24d129f34d76
clean-code-reviewer is a skill published in the GitHub repository GktuOktay/ai-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 68 tokens to every session and 450 once invoked, about $0.0003 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
doubt-driven-development
Subjects every non-trivial decision to a fresh-context adversarial review before it stands. Use when you want every assumption cross-examined before proceeding, when stress-testing a plan for hidden failure modes, when correctness matters more than speed, when working in unfamiliar code, when stakes are high…
squid-architecture-review
Periodic architectural sweep — reads existing ADRs, maps modules/dependencies/layering, and reports up to 10 prioritised findings shaped as refactor proposals /squid-refactor can consume directly.
predict
Analyzes diffs for regression risk and blast radius, generates risk-scored impact report. Triggers: PR review, code change risk, breaking change, blast radius, regression check.
analyze
Analyzes code quality, complexity, patterns across codebase. Triggers: quality report, hotspot scan, code analysis, architecture signal.
graph-it-live
Analyze code dependencies, call graphs, and architecture using the graph-it CLI. Use this skill whenever the user wants to understand how their code is connected — even if they don't say "dependency graph" explicitly. Trigger for: "what calls this function", "who uses this class", "is it safe to delete X", "what…
Systematic debugging
Use when you hit a bug, test failure, or unexpected behavior — find the root cause before changing code.