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 tahirraufkeeyu/software-development-agent-stack--sdas --skill network-diagnosticsgit clone --depth 1 https://github.com/tahirraufkeeyu/software-development-agent-stack--sdasWrote 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/tahirraufkeeyu/software-development-agent-stack--sdas/network-diagnostics)<a href="https://agentmods.dev/skills/tahirraufkeeyu/software-development-agent-stack--sdas/network-diagnostics"><img src="https://agentmods.dev/badge/skills/tahirraufkeeyu/software-development-agent-stack--sdas/network-diagnostics.svg" alt="Measured on agentmods" 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.00079 | $0.02772 |
| Opus 5 | $0.00039 | $0.01386 |
| Sonnet 5 | $0.00016 | $0.00554 |
| Haiku 4.5 | $0.00008 | $0.00277 |
Grade A, and why
network-diagnostics 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 7d 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.
- `kubectl`, `dig`, `nslookup`, `host`, `getent`, `nc` (netcat), `telnet`, `mtr`, `traceroute`, `tcpdump`, `ss`, `ip`, `openssl`, `curl`, `wget`, `jq`. How it starts
The opening of the file, as written. The whole thing — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to use
- User says "can't connect to …", "times out", "dns doesn't resolve", "certificate error", "SYN but no SYN-ACK", "works from my laptop but not from the pod".
- Cross-namespace or cross-cluster traffic broke after a NetworkPolicy / CNI / security-group change.
- A previously-working external dependency (database, SaaS, S3) started returning errors.
- VPN, peering, Transit Gateway, or route table changes are suspected.
- MTU issues after a new CNI or VPN tunnel (symptom: small requests work, larger ones hang).
Do not use this skill for application-level 4xx/5xx without a connectivity symptom (route that to the owning service's logs and monitoring-setup).
Inputs
- Source (pod / node / laptop) and destination (hostname or IP:port).
- Expected protocol (HTTP, HTTPS, gRPC, TCP, UDP).
- What changed recently (deploys, NetworkPolicy, security-group, DNS records, CNI upgrade).
- Symptom class: "doesn't resolve", "refused", "times out", "resets", "TLS error".
Outputs
- A layer-by-layer report:
Layer | Test | Result | Evidence | Verdict. - The specific failing layer (DNS / routing / firewall / TLS / application) with the root cause.
- A concrete fix (command, manifest patch, cloud console action).
- Optional: a runbook entry so the next occurrence is resolved in minutes.
Tool dependencies
kubectl,dig,nslookup,host,getent,nc(netcat),telnet,mtr,traceroute,tcpdump,ss,ip,openssl,curl,wget,jq.- Kubernetes MCP for NetworkPolicy / Endpoints inspection.
- AWS/GCP/Azure MCP for security-group / NSG / firewall-rule inspection.
- A debug pod image (
nicolaka/netshoot) for in-cluster diagnostics:kubectl run netshoot -n <ns> --rm -it --image=nicolaka/netshoot --restart=Never -- bash
Procedure
Walk these layers in order. Stop at the first failure and fix before continuing; downstream layers cannot pass if upstream layers fail.
1. DNS resolution
From the affected source:
dig +short A api.example.com
dig +short AAAA api.example.com
dig +trace api.example.com # authoritative path
nslookup api.example.com 8.8.8.8 # bypass the local resolver
getent hosts api.example.com # what libc sees (includes /etc/hosts, NSS)
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.
- 7d ago First seen · 227 lines · 79 tokens per session scan A 469d57e4c501
network-diagnostics is a skill published in the GitHub repository tahirraufkeeyu/software-development-agent-stack--sdas (18 stars, last pushed 4mo ago), licensed MIT. It adds 79 tokens to every session and 2,772 once invoked, about $0.0004 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-08-30.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.