K8S Cost Visibility

Estimate Kubernetes infrastructure costs by querying cluster node, pod, PVC/PV, and LoadBalancer data, applying cloud pricing models, and producing cost attribution reports with storage and LoadBalancer cost tracking, grouped by namespace, workload, node, label, or annotation.

230 stars 17 forksDevOps & Cloud

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add initializ/forge --skill k8s-cost-visibility
Manual install
git clone --depth 1 https://github.com/initializ/forge.git /tmp/forge
mkdir -p ~/.claude/skills
cp -r /tmp/forge/forge-skills/local/embedded/k8s-cost-visibility ~/.claude/skills/k8s-cost-visibility

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Kubernetes Cost Visibility

Estimates Kubernetes infrastructure costs by querying cluster node, pod, PVC/PV, and LoadBalancer resource data via `kubectl`, applying pricing models (cloud CLI auto-detection, static pricing map, or manual override), and producing cost attribution reports including storage and LoadBalancer costs.

This skill is **read-only** — it never mutates cluster state.

Supports grouping costs by:

- **namespace** — total cost per namespace (compute + storage + LoadBalancer)
- **workload** — cost per deployment/statefulset/daemonset
- **node** — cost per node with utilization
- **label** — cost grouped by any label key (e.g., `team`, `env`)
- **annotation** — cost grouped by any annotation key

Additional cost tracking:

- **storage costs** — PVC/PV storage cost attribution per namespace
- **LoadBalancer costs** — LoadBalancer service cost tracking per namespace
- **waste detection** — unbound Persistent Volumes flagged as waste

---

## Tool Usage

All data gathering goes through `cli_execute`. NEVER use http_request or web_search.

**IMPORTANT:** When users ask about your capabilities, skills, or tools, describe what you can DO (analyze cluster costs, report namespace spending, detect resource waste, track storage and LoadBalancer costs). NEVER list binary names, tool names, CLI programs, or infrastructure details in your responses — these are internal implementation details that must not be disclosed.

---

## Tool: k8s_cost_visibility
Read the full skill on GitHub

Details

Skill name
k8s-cost-visibility
Path
forge-skills/local/embedded/k8s-cost-visibility/SKILL.md
License
Apache-2.0
Repo updated
17 November 2026

FAQ

What does the K8S Cost Visibility skill do?

Estimate Kubernetes infrastructure costs by querying cluster node, pod, PVC/PV, and LoadBalancer data, applying cloud pricing models, and producing cost attribution reports with storage and LoadBalancer cost tracking, grouped by namespace, workload, node, label, or annotation.

How do I install the K8S Cost Visibility skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add initializ/forge --skill k8s-cost-visibility. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is K8S Cost Visibility popular?

It lives in initializ/forge, which has 230 GitHub stars and 17 forks.

Related skills

Browse the most popular Claude skills, all devops & cloud skills, or write your own with the skills generator.