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 agentmods add skills/scitix/siclaw/dns-debugnpx skills add scitix/siclaw --skill dns-debuggit clone --depth 1 https://github.com/scitix/siclawWhat 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 | $0.00033 | $0.01271 |
| Opus 5 | $0.00016 | $0.00635 |
| Sonnet 5 | $0.00007 | $0.00254 |
| Haiku 4.5 | $0.00003 | $0.00127 |
Grade A, and why
dns-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 2d 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DNS Resolution Failure Diagnosis
When pods report DNS resolution failures (service discovery not working, NXDOMAIN errors, DNS timeouts), follow this flow to identify the root cause.
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 CoreDNS configuration or network policies — that should be left to the user or cluster administrator.
Diagnostic Flow
1. Verify DNS resolution from a pod
If a specific pod is having DNS issues, test DNS resolution from within that pod:
pod_exec: pod=<pod>, namespace=<ns>, command="nslookup <service-name>"
For cross-namespace service resolution:
pod_exec: pod=<pod>, namespace=<ns>, command="nslookup <service-name>.<target-namespace>.svc.cluster.local"
If nslookup is not available in the container, try:
pod_exec: pod=<pod>, namespace=<ns>, command="cat /etc/resolv.conf"
This shows the DNS server the pod is configured to use and the search domains.
2. Check CoreDNS pod status
kubectl get pods -n kube-system -l k8s-app=kube-dns -o wide
All CoreDNS pods should be Running and Ready. Note which nodes they are running on.
3. Check CoreDNS logs
kubectl logs -n kube-system -l k8s-app=kube-dns --tail=100
Look for error messages, SERVFAIL responses, or upstream DNS failures.
4. Check DNS Service and Endpoints
kubectl get svc -n kube-system kube-dns
kubectl get endpoints -n kube-system kube-dns
The kube-dns service should have a ClusterIP, and the endpoints should list the CoreDNS pod IPs. If endpoints are empty, CoreDNS pods are not ready.
5. Match error and conclude
NXDOMAIN / server can't find — Name does not exist
The DNS name cannot be resolved. Common causes:
- Typo in service name — verify the service exists:
kubectl get svc -n <target-namespace> <service-name> - Wrong namespace — services must be referenced as
<service>.<namespace>.svc.cluster.localfrom other namespaces - Service doesn't exist — the target service has not been created
- Headless service with no endpoints — the service exists but has no backing pods
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.
- 2d ago First seen · 146 lines · 33 tokens per session scan A 97cdf1ca4fcd
dns-debug is a skill published in the GitHub repository scitix/siclaw (230 stars, last pushed 3d ago), licensed Apache-2.0. It adds 33 tokens to every session and 1,271 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-cost-visibility
Estimate Kubernetes infrastructure costs by querying cluster node, pod, PVC/PV, and LoadBalancer data, applying cloud pricing models, and producing cost attribution reports with storage and LoadBalancer cost tracking, grouped by namespace, workload, node, label, or annotation.
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.
k8s-service-connectivity
Service 连通性问题通常由 Endpoints 缺失、Selector 不匹配、[[networkpolicy|NetworkPolicy]] 阻断或 kube-proxy 异常引起。.
k8s-deployment-rollout
Kubernetes Deployment 发布失败、滚动更新卡住的完整诊断-修复-验证 Skill.
k8s-pod-crashloop
Pod CrashLoopBackOff / OOMKilled 诊断与修复：Pod CrashLoopBackOff 和 OOMKilled 是 Kubernetes 工作负载中最常见的问题类型。本 Skill 覆盖从症状识别到修复验证的完整闭环。.
k8s-dns-failure
DNS 解析问题诊断与修复：CoreDNS 是 Kubernetes 集群 DNS 的核心组件。DNS 问题会导致服务发现失败、外部依赖不可访问等连锁问题。.