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 scitix/siclaw --skill volcano-diagnose-podgit clone --depth 1 https://github.com/scitix/siclawWrote 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/scitix/siclaw/volcano-diagnose-pod)<a href="https://agentmods.dev/skills/scitix/siclaw/volcano-diagnose-pod"><img src="https://agentmods.dev/badge/skills/scitix/siclaw/volcano-diagnose-pod/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/scitix/siclaw/volcano-diagnose-pod"><img src="https://agentmods.dev/badge/skills/scitix/siclaw/volcano-diagnose-pod.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00032 | $0.01931 |
| Opus 5 | $0.00016 | $0.00966 |
| Sonnet 5 | $0.00006 | $0.00386 |
| Haiku 4.5 | $0.00003 | $0.00193 |
Grade A, and why
volcano-diagnose-pod 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 10d 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 — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Volcano Pod Diagnosis
Diagnose Volcano-managed Pod scheduling issues. This skill checks Pod status, associated PodGroup, scheduling events, and Queue configuration to identify why a Pod cannot be scheduled.
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 pod specs, PodGroups, or Queues — that should be left to the user.
Usage
bash skills/core/volcano-diagnose-pod/scripts/diagnose-pod.sh --pod <pod-name> --namespace <namespace>
Parameters
| Parameter | Required | Description |
|---|---|---|
--pod POD |
yes | Pod name to diagnose |
--namespace NS |
no | Namespace (default: default) |
--verbose |
no | Show detailed output including node resources |
Examples
Diagnose a pending pod in default namespace:
bash skills/core/volcano-diagnose-pod/scripts/diagnose-pod.sh --pod my-job-0
Diagnose a pod in specific namespace:
bash skills/core/volcano-diagnose-pod/scripts/diagnose-pod.sh --pod my-job-0 --namespace training
Verbose mode with node resource information:
bash skills/core/volcano-diagnose-pod/scripts/diagnose-pod.sh --pod my-job-0 --namespace training --verbose
Diagnostic Flow
The script performs the following checks in order:
1. Pod Status
Check the Pod's current phase and conditions.
kubectl get pod <pod> -n <ns> -o wide
kubectl describe pod <pod> -n <ns>
2. PodGroup Status
Check if the Pod is associated with a PodGroup and its scheduling status.
kubectl get pod <pod> -n <ns> -o jsonpath='{.metadata.annotations.scheduling.volcano.sh/pod-group}'
kubectl get podgroup <podgroup> -n <ns>
Key fields to check:
spec.minMember: Minimum members required for Gang schedulingstatus.phase: Pending, Inqueue, Running, Unknownstatus.running: Number of running podsstatus.pending: Number of pending pods
3. Events Analysis
Check scheduling events for failure reasons.
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.
- 10d ago First seen · 197 lines · 32 tokens per session scan A b42f4d8f0ad9
volcano-diagnose-pod is a skill published in the GitHub repository scitix/siclaw (233 stars, last pushed yesterday), licensed Apache-2.0. It adds 32 tokens to every session and 1,931 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-dns-failure
A guide for diagnosing and fixing DNS problems in Kubernetes, a system for running containerised applications. It focuses on CoreDNS, the component that helps services find one another and reach external services.
incident-triage
Use when asked to triage, investigate, or diagnose a Kubernetes incident, outage, or unhealthy workload. Gives the step-by-step order of investigation and the format for the findings.
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-service-connectivity
A troubleshooting guide for Kubernetes service connectivity, where services provide stable network access to groups of running containers. It focuses on missing endpoints, selector mismatches, network policies, and kube-proxy problems.
k8s-deployment-rollout
A troubleshooting workflow for failed Kubernetes Deployment releases and rolling updates that become stuck. Kubernetes is a system for running and managing containers.
k8s-pod-crashloop
A troubleshooting guide for Kubernetes pods that repeatedly restart or run out of memory. Kubernetes is a system for running and managing containers, and a pod is its basic unit for running an application.