Borrowing it
Nothing to install: this file belongs to atilladeniz/Kubeli. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/atilladeniz/Kubeli/main/.claude/skills/refactor/SKILL.mdgit clone --depth 1 https://github.com/atilladeniz/KubeliWrote 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/atilladeniz/kubeli/refactor)<a href="https://agentmods.dev/skills/atilladeniz/kubeli/refactor"><img src="https://agentmods.dev/badge/skills/atilladeniz/kubeli/refactor/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/atilladeniz/kubeli/refactor"><img src="https://agentmods.dev/badge/skills/atilladeniz/kubeli/refactor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 478 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 485 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00048 | $0.08076 |
| Opus 5.5 | $0.00019 | $0.03230 |
| Sonnet 5.5 | $0.00010 | $0.01615 |
| Haiku 4.5 | $0.00005 | $0.00808 |
Grade A, and why
refactor 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 2mo 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 — 1,175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Strategic Refactoring Skill
You are a senior software architect performing strategic refactoring based on John Ousterhout's "A Philosophy of Software Design" principles.
Your Goal: Transform code to reduce complexity while maintaining functionality. Every change should make the system look like it was designed with this feature in mind from the start.
Kubeli Tech Stack
- Frontend: Vite 7+, React 19, TypeScript
- Desktop: Tauri 2.0 (Rust backend)
- State: Zustand
- Styling: Tailwind CSS
- K8s Client: kube-rs (Rust)
Phase 1: Analysis (Use /software-design-review principles)
Before any refactoring, analyze the code against these 15 Ousterhout principles:
- Strategic vs. Tactical Programming
- Module Depth (Deep vs. Shallow)
- Somewhat General-Purpose (Generalization)
- Different Layers, Different Abstractions
- Information Hiding & Leaks
- Pull Complexity Downward
- Together or Separate?
- Define Errors Out of Existence
- Design Twice
- Consistency
- Code Should Be Obvious
- Comments & Documentation
- Names
- Write Comments First
- Modifying Existing Code
Phase 2: Safety Checklist
Before ANY refactoring:
- Tests exist for the code being refactored
- All tests pass currently
- Code is committed (clean git state)
- You understand what the code does (read it first!)
If tests don't exist:
- Write characterization tests first
- Test the component as a black box
- Validate end results, not implementation details
Phase 3: Clean Code Smells Checklist (Robert Martin)
In addition to Ousterhout's principles, check for these code smells:
Comments (C1-C5)
| Code | Smell | Fix |
|---|---|---|
| C1 | Ungeeignete Informationen (Change history, author info) | Remove, use git |
| C2 | Überholte Kommentare | Update or delete |
| C3 | Redundante Kommentare | Delete if code is self-explanatory |
| C4 | Schlecht geschriebene Kommentare | Rewrite clearly |
| C5 | Auskommentierter Code | Delete (git has history) |
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.
- 2mo ago First seen · 1,175 lines · 48 tokens per session scan A bcd41a19ae87
refactor is a skill published in the GitHub repository atilladeniz/Kubeli (397 stars, last pushed 10d ago), licensed MIT. It adds 48 tokens to every session and 8,076 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-30.
Other skills, from other repositories
kubernetes-expert
Expert-level Kubernetes cluster management, deployment strategies, networking, and production operations. Use when the user mentions containers, orchestration, devops, or cloud native, or when the task involves Kubernetes Architecture, Pods, Deployments, or Services.
k8s-generator
Generate production-ready Kubernetes manifests with Deployments, Services, ConfigMaps, and Ingress.
Pr Review
Review pull requests against team standards and best practices.
Code Review
Review code quality, patterns, and best practices.
kubectl-basics
A guide to kubectl, the command-line tool used to manage Kubernetes clusters, which run containerized applications.
k8s-deployer
Kubernetes deployment management - generate manifests, Helm charts, manage rollouts, check cluster status, and apply security best practices.