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/initializ/forge/k8s-cost-visibilitynpx skills add initializ/forge --skill k8s-cost-visibilitygit clone --depth 1 https://github.com/initializ/forgeWrote 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/initializ/forge/k8s-cost-visibility)<a href="https://agentmods.dev/skills/initializ/forge/k8s-cost-visibility"><img src="https://agentmods.dev/badge/skills/initializ/forge/k8s-cost-visibility.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.00058 | $0.02710 |
| Opus 5 | $0.00029 | $0.01355 |
| Sonnet 5 | $0.00012 | $0.00542 |
| Haiku 4.5 | $0.00006 | $0.00271 |
Grade A, and why
k8s-cost-visibility scanned grade A with 1 finding 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 5d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- pattern: '\b(kubectl|jq|awk|bc|curl)\b.*\b(kubectl|jq|awk|bc|curl)\b.*\b(kubectl|jq|awk|bc|curl)\b' How it starts
The opening of the file, as written. The whole thing — 280 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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
Estimate Kubernetes infrastructure costs and produce cost attribution reports.
Input: pricing_mode (string), group_by (string), namespace (string), label_selector (string), top (integer), output_format (string), cache_ttl (integer)
Output format: Markdown tables for cost reports. JSON for machine-readable output.
Parameters
| Parameter | Type | Default | Description |
|---|---|---|---|
pricing_mode |
string | auto |
Pricing source: auto (detect cloud CLI), aws, gcp, azure, static (built-in map), or custom:file.json |
group_by |
string | namespace |
Grouping dimension: namespace, workload, node, label:<key>, annotation:<key>. Use namespace to see storage and LoadBalancer cost columns. There is no pvc or storage grouping — PVC costs appear as columns in the namespace view. |
namespace |
string | (empty) | Filter to a single namespace. When set, only pods, PVCs, and services in this namespace are included. Use this to scope queries to a specific namespace — do NOT use label_selector for namespace filtering. |
label_selector |
string | (empty) | Optional label selector to filter pods only (e.g., app=web,env=prod). Does NOT filter PVCs or services. Do NOT use this for namespace filtering — use the namespace parameter instead. |
top |
integer | 0 |
Limit output to top N entries by cost (0 = show all) |
output_format |
string | markdown |
Output format: markdown or json |
cache_ttl |
integer | 300 |
Cache TTL in seconds for node pricing data (0 = no cache) |
What ships with it
1 file 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.
- 5d ago First seen · 280 lines · 58 tokens per session scan A be03124f2ba2
k8s-cost-visibility is a skill published in the GitHub repository initializ/forge (227 stars, last pushed yesterday), licensed Apache-2.0. It adds 58 tokens to every session and 2,710 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
cluster-events
Analyze cluster-wide Kubernetes events to identify issues and patterns. Aggregates Warning events, detects high-frequency patterns, and correlates related events.
ingress-debug
Diagnose Ingress failures (rules not matching, backend unreachable, TLS errors, no address assigned). Checks Ingress resources, IngressClass, backend Services, and controller health to identify why external traffic is not routed correctly.
quota-debug
Diagnose Kubernetes native ResourceQuota and LimitRange admission rejections (exceeded quota, forbidden by LimitRange, FailedCreate). Checks namespace quotas, current usage, LimitRange constraints, and ReplicaSet events to identify why pods cannot be created. Not applicable to Volcano Queue — use…
volcano-diagnose-pod
Diagnose Volcano-managed Pod scheduling issues. Checks Pod status, PodGroup, events, and Queue to identify scheduling failures.
volcano-job-diagnose
Diagnose Volcano Job status and issues. Check Job phases, task statuses, PodGroup associations, and overall job health.
volcano-node-resources
Query cluster node resources for Volcano scheduling. Check allocatable CPU, memory, GPU, and current usage.