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/scitix/siclaw/pvc-debugnpx skills add scitix/siclaw --skill pvc-debuggit clone --depth 1 https://github.com/scitix/siclawWhat 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.00046 | $0.01510 |
| Opus 5 | $0.00023 | $0.00755 |
| Sonnet 5 | $0.00009 | $0.00302 |
| Haiku 4.5 | $0.00005 | $0.00151 |
Grade A, and why
pvc-debug 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 3d 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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PersistentVolumeClaim Failure Diagnosis
When a PVC is stuck in Pending, a pod cannot mount its volume, or storage provisioning fails, follow this flow to identify the root cause.
Scope: This skill is for diagnosis only. Once you identify the root cause, report it to the user and stop. Do NOT attempt to modify PVCs, PVs, or StorageClasses — that should be left to the user or cluster administrator.
Diagnostic Flow
1. Check PVC status
kubectl get pvc <pvc-name> -n <ns>
Note the STATUS, VOLUME, CAPACITY, and STORAGECLASS columns.
Bound— PVC is healthy, issue may be elsewhere (pod mount, permissions)Pending— PVC is waiting for a PV to be provisioned or boundLost— The PV the PVC was bound to has been deleted
2. Describe the PVC
kubectl describe pvc <pvc-name> -n <ns>
Focus on:
- Events — provisioner errors, binding failures, or quota exceeded messages
- Access Modes — requested access mode (ReadWriteOnce, ReadWriteMany, ReadOnlyMany)
- StorageClass — which StorageClass is requested
- Volume Name — if bound, which PV it is bound to
3. Check the StorageClass
kubectl get storageclass
Verify the StorageClass referenced by the PVC exists and note:
- PROVISIONER — the volume provisioner responsible for creating PVs
- RECLAIMPOLICY — Delete or Retain
- VOLUMEBINDINGMODE — Immediate or WaitForFirstConsumer
If the StorageClass uses WaitForFirstConsumer, the PV will not be provisioned until a pod using the PVC is scheduled to a node.
4. Check available PVs (for static provisioning)
If the cluster uses pre-created PVs instead of dynamic provisioning:
kubectl get pv
For a PVC to bind to a PV, the PV must:
- Be in
Availablestatus - Match the PVC's requested
storageClassName - Meet the PVC's capacity request (PV capacity >= PVC request)
- Support the PVC's access mode
- Match any
selectorlabels on the PVC
Check a specific PV:
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.
- 3d ago First seen · 170 lines · 46 tokens per session scan A 56f3f362b17e
pvc-debug is a skill published in the GitHub repository scitix/siclaw (230 stars, last pushed 4d ago), licensed Apache-2.0. It adds 46 tokens to every session and 1,510 once invoked, about $0.0002 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-30.
Other skills, from other repositories
k8s-service-connectivity
Service 连通性问题通常由 Endpoints 缺失、Selector 不匹配、[[networkpolicy|NetworkPolicy]] 阻断或 kube-proxy 异常引起。.
k8s-dns-failure
DNS 解析问题诊断与修复：CoreDNS 是 Kubernetes 集群 DNS 的核心组件。DNS 问题会导致服务发现失败、外部依赖不可访问等连锁问题。.
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.
k8s-incident-triage
Read-only Kubernetes incident triage using kubectl. Accepts natural language or structured input. Produces root-cause hypotheses, evidence, and next-step commands.
ariadne-kubernetes-graph
Use for Ariadne MCP-backed Kubernetes state questions: translate operational questions into Cypher, repair graphquery failures, and decide when graphschema or graphhealth is needed. Best for live or snapshot-backed graph data about resource relationships; do not use for codebase-only tasks or generic Kubernetes…
k8s-deployment-rollout
Kubernetes Deployment 发布失败、滚动更新卡住的完整诊断-修复-验证 Skill.