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 pantheon-org/tekhne --skill debuggit clone --depth 1 https://github.com/pantheon-org/tekhneWrote 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/pantheon-org/tekhne/debug)<a href="https://agentmods.dev/skills/pantheon-org/tekhne/debug"><img src="https://agentmods.dev/badge/skills/pantheon-org/tekhne/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/pantheon-org/tekhne/debug"><img src="https://agentmods.dev/badge/skills/pantheon-org/tekhne/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.00061 | $0.02889 |
| Opus 5 | $0.00030 | $0.01444 |
| Sonnet 5 | $0.00012 | $0.00578 |
| Haiku 4.5 | $0.00006 | $0.00289 |
Grade A, and why
k8s-debug scanned grade A with 1 finding 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 9d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl http://localhost:8080/api/v1/namespaces/<namespace>/pods/<pod-name> How it starts
The opening of the file, as written. The whole thing — 379 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kubernetes Debugging Skill
Debugging Mindset
Mental Model: Kubernetes debugging follows a layered approach—start broad (cluster health), narrow to affected components (pods, services), then drill into specific failures (logs, events, resource constraints).
Decision Framework:
- Gather context before jumping to solutions. Check
kubectl get eventsanddescriberesources first. - Verify assumptions about selectors, labels, and namespaces—label mismatches are the most common root cause.
- Test hypotheses systematically: network → resource → configuration → application.
- Document findings as you go—Kubernetes issues often involve multiple interacting failures.
When to use this skill:
- Pods stuck in Pending, CrashLoopBackOff, ImagePullBackOff, or Error states
- Services not routing traffic despite healthy pods
- Resource exhaustion (OOMKilled, CPU throttling)
- Deployments failing to roll out or stuck in progress
- Network policies blocking expected traffic
Quick Diagnostic Patterns
Pod Not Starting
# Quick assessment
kubectl get pod <pod-name> -n <namespace>
kubectl describe pod <pod-name> -n <namespace> # Events section is key
# Detailed diagnostics
python3 scripts/pod_diagnostics.py <pod-name> -n <namespace>
# Check previous logs if CrashLoopBackOff
kubectl logs <pod-name> -n <namespace> --previous
Service Connectivity Issues
# Verify service endpoints match pod IPs
kubectl get svc <service-name> -n <namespace>
kubectl get endpoints <service-name> -n <namespace>
# Network diagnostics
./scripts/network_debug.sh <namespace> <pod-name>
# Test from debug pod
kubectl run tmp-shell --rm -i --tty --image nicolaka/netshoot -- /bin/bash
Performance Degradation
# Resource usage by container
kubectl top pods -n <namespace> --containers
# Check for OOMKilled
kubectl get pod <pod-name> -n <namespace> -o yaml | grep -A 10 lastState
# Review recent logs
kubectl logs <pod-name> -n <namespace> --tail=100 --timestamps
What ships with it
14 files 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.
- .audits/2026-03-06/analysis.md 1.1 KB
- .audits/2026-03-06/audit.json 448 B
- .audits/2026-03-06/remediation-plan.md 3.4 KB
- .audits/latest 10 B
- evals/scenario-01.md 4.0 KB
- evals/scenario-02.md 4.3 KB
- evals/scenario-03.md 4.2 KB
- evals/scenario-04.md 4.0 KB
- evals/scenario-05.md 3.9 KB
- references/common_issues.md 8.1 KB
- references/troubleshooting_workflow.md 8.4 KB
- scripts/cluster_health.sh 3.2 KB runs code
- scripts/network_debug.sh 3.4 KB runs code
- scripts/pod_diagnostics.py 3.6 KB runs code
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.
- 9d ago First seen · 379 lines · 61 tokens per session scan A 7c31d6b06a74
k8s-debug is a skill published in the GitHub repository pantheon-org/tekhne (10 stars, last pushed yesterday), licensed MIT. It adds 61 tokens to every session and 2,889 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
zeabur-server-ssh
Use when debugging services on a user's dedicated server via SSH. Use when needing to run a command on the server, inspect pods, check container logs, view k8s resources, or run kubectl commands. Use when "service exec" is insufficient and you need server-level access. Use when user says "check my server", "run X on…
k8s-rbac-quota
A troubleshooting guide for Kubernetes access permissions and resource limits. Kubernetes is software for running and managing containers, while RBAC controls who can do what and ResourceQuota limits resource usage.
k8s-config-secret
A Kubernetes troubleshooting workflow for ConfigMaps and Secrets, which store configuration values and sensitive settings for applications.
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-image-pull
A Kubernetes troubleshooting workflow for ImagePullBackOff, a status meaning that a cluster cannot pull a container image and keeps retrying.
k8s-ingress-gateway
A troubleshooting guide for Kubernetes Ingress and Gateway configurations. Kubernetes is a system for running containers, and Ingress and Gateway components route web traffic to those containers.