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 dns-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/dns-debug)<a href="https://agentmods.dev/skills/scitix/siclaw/dns-debug"><img src="https://agentmods.dev/badge/skills/scitix/siclaw/dns-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/dns-debug"><img src="https://agentmods.dev/badge/skills/scitix/siclaw/dns-debug.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 143 Code deploys a privileged Kubernetes workload (privileged container, hostPath mount, or host namespaces). This grants root on the node and is a node/cluster takeover vector.Fix: Remove privileged, hostPath, and host-namespace settings from workloads. Use a least-privilege securityContext, drop capabilities, and avoid mounting the host filesystem.
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.00033 | $0.01271 |
| Opus 5.5 | $0.00013 | $0.00508 |
| Sonnet 5.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 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 — 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.
- 1mo ago First seen · 146 lines · 33 tokens per session scan A 97cdf1ca4fcd
dns-debug is a skill published in the GitHub repository scitix/siclaw (238 stars, last pushed 6d ago), licensed Apache-2.0. It adds 33 tokens to every session and 1,271 once invoked, about $0.0001 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-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.
ariadne-kubernetes-graph
Use for Ariadne MCP-backed Kubernetes state questions: translate operational questions into Cypher, repair graphquery failures, and decide when graphschema or graphhealth is needed. Best for live or snapshot-backed graph data about resource relationships; do not use for codebase-only tasks or generic Kubernetes…
k8s-service-connectivity
A troubleshooting guide for Kubernetes service connectivity, where services provide stable network access to groups of running containers. It focuses on missing endpoints, selector mismatches, network policies, and kube-proxy problems.
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.