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 batu-sonmez/infraclaude --skill k8s-troubleshootgit clone --depth 1 https://github.com/batu-sonmez/infraclaudeWrote 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/batu-sonmez/infraclaude/k8s-troubleshoot)<a href="https://agentmods.dev/skills/batu-sonmez/infraclaude/k8s-troubleshoot"><img src="https://agentmods.dev/badge/skills/batu-sonmez/infraclaude/k8s-troubleshoot/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/batu-sonmez/infraclaude/k8s-troubleshoot"><img src="https://agentmods.dev/badge/skills/batu-sonmez/infraclaude/k8s-troubleshoot.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.00000 | $0.00655 |
| Opus 5 | $0.00000 | $0.00328 |
| Sonnet 5 | $0.00000 | $0.00131 |
| Haiku 4.5 | $0.00000 | $0.00065 |
Grade A, and why
k8s-troubleshoot 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.
How it starts
The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kubernetes Troubleshooting Guide
When debugging Kubernetes issues, follow this systematic approach using InfraClaude tools.
Pod Not Starting
- Use
k8s_get_podsto identify the pod status - Use
k8s_describe_podto check the Events section - Common causes:
- ImagePullBackOff: Wrong image name/tag, private registry auth, rate limiting
- CrashLoopBackOff: Application error — check logs with
k8s_get_pod_logs(also tryprevious: true) - Pending: Insufficient resources — check
k8s_top_nodesfor node capacity - Init container failing: Check init container logs specifically with
containerparameter - CreateContainerConfigError: Missing ConfigMap/Secret references
High Latency Investigation
- Use
prom_instant_querywith:rate(http_request_duration_seconds_sum[5m]) / rate(http_request_duration_seconds_count[5m]) - Check upstream dependencies with
k8s_get_servicesand endpoint health - Look for resource saturation:
k8s_top_pods— pods at CPU limit will be throttled - Check for recent deployments:
k8s_rollout_status - Check for noisy neighbors on the same node:
k8s_top_nodes
Memory Leak Detection
- Use
prom_range_queryforcontainer_memory_working_set_bytesover 24h - Look for monotonically increasing memory without plateaus
- Check OOMKilled events:
k8s_get_eventswith type=Warning - Check container restart counts with
k8s_get_pods - Compare requested vs actual memory in
k8s_describe_pod
Deployment Rollout Issues
- Use
k8s_rollout_statusto check progress - Common issues:
- ProgressDeadlineExceeded: New pods failing to start — check pod events
- Insufficient replicas: Check resource quotas and node capacity
- Readiness probe failing: Application not healthy — check logs and probe config
- Use
k8s_rollback_deploymentif the new version is broken
Node Issues
- Use
k8s_get_nodesto check node status - Use
k8s_describe_nodeto check conditions:- MemoryPressure: Node running out of memory
- DiskPressure: Node disk is full
- PIDPressure: Too many processes
- Use
k8s_top_nodesto see actual resource usage - If a node is problematic, use
k8s_cordon_nodeto prevent new scheduling
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 · 58 lines · 0 tokens per session scan A 314d31262cab
k8s-troubleshoot is a skill published in the GitHub repository batu-sonmez/infraclaude (0 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 655 tokens. 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-31.
Other skills, from other repositories
hermes-s6-container-supervision
Modify or debug s6 services in the Hermes Docker image.
smoke-test
Health smoke tests + auto-fix for gbrain installs (and OpenClaw services when present). Run after machine/container restarts or whenever something seems broken. Tests critical services, auto-fixes bounded local issues, and reports worker topology without starting daemons. Extensible via user-defined test scripts in…
competition-container-runtime
Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for live container runtime analysis, mounted secrets, sidecars, namespaces, init containers, entrypoint drift, and route-to-container resolution. Use when the user asks why a live container differs from manifests, where a mounted secret is…
meta-home-it-rescue
Use this meta-skill instead of answering directly when the user needs help with home, small-team, laptop, browser, printer, Docker, Git, network, UI, or deployment troubleshooting that benefits from multi-skill orchestration across symptom intake, environment capture, web lookup, and repair planning.
debugging-local-replay
Debugs why session recordings aren't appearing in the local dev environment. Use when a developer reports that local replay ingestion isn't working, recordings aren't showing up despite /s calls, or the replay pipeline seems broken after hogli start. Covers the full local pipeline: SDK capture, Caddy proxy…
docker-debug
Debug Kurtosis running on local Docker. Inspect engine, API container, and service logs. Diagnose container crashes, port conflicts, and networking issues. Use when kurtosis commands fail or services aren't reachable on Docker.