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.
git clone --depth 1 https://github.com/CacinieP/network-troubleshoot-skillWrote 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/rules/caciniep/network-troubleshoot-skill/windsurfrules)<a href="https://agentmods.dev/rules/caciniep/network-troubleshoot-skill/windsurfrules"><img src="https://agentmods.dev/badge/rules/caciniep/network-troubleshoot-skill/windsurfrules/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/rules/caciniep/network-troubleshoot-skill/windsurfrules"><img src="https://agentmods.dev/badge/rules/caciniep/network-troubleshoot-skill/windsurfrules.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.00987 | $0.00987 |
| Opus 5.5 | $0.00395 | $0.00395 |
| Sonnet 5.5 | $0.00197 | $0.00197 |
| Haiku 4.5 | $0.00099 | $0.00099 |
Grade A, and why
windsurfrules 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 today.
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.
- npm install, pip install, git push/pull, docker pull, curl, wget failing How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Network Troubleshoot Rules
When detecting network errors in code or commands, apply systematic diagnosis.
Triggers
- ECONNREFUSED, ECONNRESET, ETIMEDOUT, ENOTFOUND, timeout, connection refused, connection reset, SSL, certificate, proxy, DNS, 502, 503, 504
- npm install, pip install, git push/pull, docker pull, curl, wget failing
- network, connect, timeout, DNS, proxy, VPN, offline
Error Classification
- ECONNREFUSED → Service not running, wrong port, firewall rejecting
- ECONNRESET → Firewall reset, server crash, keepalive timeout
- ETIMEDOUT → Network unreachable, firewall drop, DNS timeout
- ENOTFOUND → DNS resolution failure
- EACCES, EPERM → Firewall / Permissions
- Proxy errors → Proxy not running or misconfigured
- SSL/TLS errors → Certificate chain, expiry, CA trust
- HTTP 5xx → Server-side issue
- npm ERR! network, pip timeout → Package Manager
- fatal: unable to access (git) → Git / Network
Diagnostic Flow
Step 1: Identify Category
Match the error message to a category above.
Step 2: Run Diagnostics
Connectivity:
ping -c 4 <host> # Linux/macOS
ping -n 4 <host> # Windows
curl -v telnet://<host>:<port> --connect-timeout 5 # cross-platform port check
nc -zv <host> <port> # Linux/macOS only
DNS:
nslookup <host>
nslookup <host> 8.8.8.8
Proxy:
echo $HTTP_PROXY $HTTPS_PROXY $ALL_PROXY
curl -x http://127.0.0.1:7890 https://www.google.com --connect-timeout 5
git config --global --get http.proxy
npm config get proxy
SSL:
openssl s_client -connect <host>:443 -showcerts </dev/null
echo | openssl s_client -connect <host>:443 2>/dev/null | openssl x509 -noout -dates
curl -vvv https://<host> 2>&1 | grep -E "SSL|TLS|certificate"
HTTP:
curl -vvv -o /dev/null -w "HTTP %{http_code}\nTime: %{time_total}s\n" https://<host>/<path>
Package Managers:
npm config list && npm ping
pip config list
docker info 2>&1 | grep -i "registry\|proxy"
git config --list | grep -i proxy
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.
- today First seen · 103 lines · 987 tokens per session scan A 5a029e94b0c1
windsurfrules is a cursor rule published in the GitHub repository CacinieP/network-troubleshoot-skill (8 stars, last pushed yesterday), licensed MIT. It adds 987 tokens to every session, about $0.0039 per session on Opus 5.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-10-15.
Other cursor rules, from other repositories
connect
Connect, authenticate, and verify any SaaS CLI tool.
20-routing
Routing manifest rules — single source app/routes.ts. See rules/core/routing.md.
40-styling
CSS modules colocated with components, kebab-case filenames. See rules/core/styling.md.
aws
AWS: well-architected patterns, IAM, serverless.
deployment
Rails Deployment with Kamal.
aws-iam
AWS IAM Security Best Practices.