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-resource-insufficientgit 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-resource-insufficient)<a href="https://agentmods.dev/skills/scitix/siclaw/volcano-resource-insufficient"><img src="https://agentmods.dev/badge/skills/scitix/siclaw/volcano-resource-insufficient/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-resource-insufficient"><img src="https://agentmods.dev/badge/skills/scitix/siclaw/volcano-resource-insufficient.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.00036 | $0.02372 |
| Opus 5 | $0.00018 | $0.01186 |
| Sonnet 5 | $0.00007 | $0.00474 |
| Haiku 4.5 | $0.00004 | $0.00237 |
Grade A, and why
volcano-resource-insufficient 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 — 316 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resource Insufficiency Diagnosis
This guide helps diagnose resource shortage issues in Volcano-scheduled workloads. Resource insufficiency is one of the most common causes of scheduling failures.
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 resource quotas or delete workloads.
When to Use This Guide
Use this skill when:
- Events show
Insufficient cpuorInsufficient memory - Pods are stuck in
Pendingwith resource-related events - Nodes show zero allocatable resources
- Pods are being
OOMKilled(Out of Memory) FailedSchedulingevents mention resource constraints
Types of Resource Issues
1. Cluster-Wide Resource Exhaustion
The entire cluster lacks sufficient resources to meet the workload demands.
2. Resource Fragmentation
Total resources exist but are distributed across too many nodes to satisfy specific scheduling constraints (like Gang scheduling).
3. Per-Node Resource Shortage
Individual nodes lack enough resources, even though the cluster as a whole has capacity.
4. Queue Resource Limits
The Queue has reached its deserved resource limit, preventing new pods from being scheduled.
Diagnostic Steps
Step 1: Identify Resource Shortage Type
Check the specific error message in events:
kubectl get events -n <namespace> --field-selector involvedObject.name=<pod-name> --sort-by='.lastTimestamp'
Common error patterns:
| Error Message | Resource Type | Scope |
|---|---|---|
Insufficient cpu |
CPU | Node-level |
Insufficient memory |
Memory | Node-level |
Insufficient nvidia.com/gpu |
GPU | Node-level |
0/N nodes are available |
General | Cluster-level |
exceeded quota |
Queue-level | Queue limit |
Step 2: Check Pod Resource Requests
Determine how much resources the pod is requesting:
kubectl get pod <pod-name> -n <namespace> -o jsonpath='{.spec.containers[*].resources.requests}'
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 · 316 lines · 36 tokens per session scan A b55a04dc2e99
volcano-resource-insufficient is a skill published in the GitHub repository scitix/siclaw (233 stars, last pushed yesterday), licensed Apache-2.0. It adds 36 tokens to every session and 2,372 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-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.
devops-deployment
Use when setting up CI/CD pipelines, containerizing applications, deploying to Kubernetes, or writing infrastructure as code. DevOps & Deployment covers GitHub Actions, Docker, Helm, and Terraform patterns.
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.
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.
lucas-runbook
Lucas runbook-driven troubleshooting for Kubernetes issues. Use when investigating pod errors, crashes, restarts, or any Kubernetes problem. Automatically search runbooks before taking action.