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 bregman-arie/devops-sre-skills --skill diagnose-crashloopgit clone --depth 1 https://github.com/bregman-arie/devops-sre-skillsWrote 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/bregman-arie/devops-sre-skills/diagnose-crashloop)<a href="https://agentmods.dev/skills/bregman-arie/devops-sre-skills/diagnose-crashloop"><img src="https://agentmods.dev/badge/skills/bregman-arie/devops-sre-skills/diagnose-crashloop/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/bregman-arie/devops-sre-skills/diagnose-crashloop"><img src="https://agentmods.dev/badge/skills/bregman-arie/devops-sre-skills/diagnose-crashloop.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00020 | $0.00530 |
| Opus 5 | $0.00010 | $0.00265 |
| Sonnet 5 | $0.00004 | $0.00106 |
| Haiku 4.5 | $0.00002 | $0.00053 |
Grade A, and why
Diagnose CrashLoopBackOff 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 11d 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.
What it actually says
When to use
Use when a pod is in CrashLoopBackOff or restarting and you need to determine why.
Preconditions
- You have read access to the cluster and target namespace.
- You know the namespace and either a pod name or the owning workload.
Procedure
- Identify the crashing container and restart count.
- Inspect last termination reason/exit code and recent events.
- Pull logs for the previous container instance.
- Classify the failure mode (config, dependency, permissions, resource, app bug).
- Identify the minimal safe remediation and how to verify.
Decision points
- Exit code
137/OOMKilled: investigate memory limits/usage and leaks. - Exit code
1+ stack trace: likely application/config issue. - Readiness/liveness probe failures: check probe config and upstream dependencies.
- Image-related events: see
diagnose-imagepullbackoff.
Verification
- Pod transitions to
Runningand stays stable for multiple probe periods. - Error rate and latency for the workload return to baseline.
- Restart count stops increasing.
Rollback / undo
- If a remediation involved a rollout, rollback to the previous known-good revision.
- If configuration was changed, revert the config and redeploy.
Escalation
- Escalate to service owner if the issue is a code regression or requires a patch.
- Escalate to platform team if it appears cluster-wide (many namespaces affected).
Examples
Example investigation flow (parameterize values):
kubectl -n <ns> get pod <pod> -o wide
kubectl -n <ns> describe pod <pod>
kubectl -n <ns> logs <pod> --all-containers --previous --tail=200
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.
- 11d ago First seen · 75 lines · 20 tokens per session scan A b6c3bc0273c5
Diagnose CrashLoopBackOff is a skill published in the GitHub repository bregman-arie/devops-sre-skills (22 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 20 tokens to every session and 530 once invoked, about $0.0001 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-incident-triage
Read-only Kubernetes incident triage using kubectl. Accepts natural language or structured input. Produces root-cause hypotheses, evidence, and next-step commands.
networkpolicy-debug
Diagnose NetworkPolicy-related connectivity issues (traffic unexpectedly blocked, default-deny effects, egress blocking DNS). Identifies which NetworkPolicies affect a pod, checks ingress/egress rules, and verifies CNI support.
statefulset-debug
Diagnose StatefulSet rollout and scaling failures (ordered update stuck, OnDelete not updating, partition misconfiguration, PVC binding deadlocks). Checks update strategy, pod ordinal progression, PVC bindings, and ordered startup to identify why a StatefulSet is not progressing.
image-pull-debug
Diagnose container image pull failures (ErrImagePull / ImagePullBackOff). Checks pod status, containerd logs, and events to identify root cause.
pod-pending-debug
Diagnose pod scheduling failures (Pending, Unschedulable). Checks events, node resources, taints, affinity, and PVC bindings to identify why a pod cannot be scheduled.
deployment-rollout-debug
Diagnose Deployment rollout failures (stuck rollouts, ProgressDeadlineExceeded, replica mismatch). Checks rollout status, ReplicaSets, and new pod health to identify why an update is failing.