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 pod-pending-debuggit 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/pod-pending-debug)<a href="https://agentmods.dev/skills/scitix/siclaw/pod-pending-debug"><img src="https://agentmods.dev/badge/skills/scitix/siclaw/pod-pending-debug/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/pod-pending-debug"><img src="https://agentmods.dev/badge/skills/scitix/siclaw/pod-pending-debug.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.00041 | $0.01507 |
| Opus 5.5 | $0.00016 | $0.00603 |
| Sonnet 5.5 | $0.00008 | $0.00301 |
| Haiku 4.5 | $0.00004 | $0.00151 |
Grade A, and why
pod-pending-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 1mo 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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pod Scheduling Failure Diagnosis
When a pod is stuck in Pending state, follow this flow to identify why the scheduler cannot place it on a node.
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 node taints, labels, or pod specs — that should be left to the user.
Diagnostic Flow
1. Read the pod and its events — one call
k8s_inspect(kind: "pod", name: "<pod>", namespace: "<ns>")
The scheduler's FailedScheduling event carries the reason, and this returns the pod's events
alongside its phase and container states in a single call.
Two things to read carefully:
- The
FailedSchedulingmessage — it says how many nodes were evaluated and why each was rejected, and that count is what separates "no capacity anywhere" from "one taint on one node". The compact bundle keeps substantially more of long scheduler messages, but if a line ends in…, fetch that event withkubectl get eventsorkubectl describe podbefore concluding from the missing tail. - The final
status:line.partial (events: …)means the events could not be read at all — nothing below applies until that is fixed.
An empty events section is not a conclusion. Events expire on a TTL (commonly one hour), so zero events means none are retained, which covers two opposite situations:
- the scheduler never spoke — a missing scheduler, an admission webhook, or a
schedulerNamenothing is servicing. Reachable, and a different problem from every pattern below. - the scheduler spoke long ago and the record aged out. This is the likely one for a pod that has been Pending for hours, i.e. exactly when the events are empty.
Use the pod's own PodScheduled condition to tell them apart — it is part of the object, so it does
not expire. PodScheduled=False (Unschedulable: …) carries the scheduler's verdict and its message
survives the event that first reported it; if the pod has no PodScheduled condition at all, the
scheduler genuinely has not processed it. Read the pod's age against the cluster's event retention
before treating an empty section as evidence of anything.
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.
- 1mo ago First seen · 180 lines · 41 tokens per session scan A ae2f01068d4b
pod-pending-debug is a skill published in the GitHub repository scitix/siclaw (238 stars, last pushed 10d ago), licensed Apache-2.0. It adds 41 tokens to every session and 1,507 once invoked, about $0.0002 per session on Opus 5.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.
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.
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
Kubernetes operations playbook for deploying services: core objects, probes, resource sizing, safe rollouts, and fast kubectl debugging.