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/rule)<a href="https://agentmods.dev/rules/caciniep/network-troubleshoot-skill/rule"><img src="https://agentmods.dev/badge/rules/caciniep/network-troubleshoot-skill/rule.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.00682 | $0.00682 |
| Opus 5 | $0.00341 | $0.00341 |
| Sonnet 5 | $0.00136 | $0.00136 |
| Haiku 4.5 | $0.00068 | $0.00068 |
Grade A, and why
RULE 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 6d 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.
- Failing commands: npm install, pip install, git push/pull, docker pull, curl, wget How it starts
The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Network Troubleshooting Rule
When network errors occur, follow this structured diagnostic workflow.
Triggers
- Errors: ECONNREFUSED, ECONNRESET, ETIMEDOUT, ENOTFOUND, timeout, connection refused, connection reset, SSL, certificate, proxy, DNS
- HTTP status: 403, 407, 502, 503, 504
- Failing commands: npm install, pip install, git push/pull, docker pull, curl, wget
- Keywords: network, connect, timeout, DNS, proxy, VPN, offline
Classification
| Pattern | Category |
|---|---|
| ECONNREFUSED, Connection refused | Connectivity |
| ECONNRESET, Connection reset | Firewall |
| ETIMEDOUT, timed out | Routing/Timeout |
| ENOTFOUND, getaddrinfo ENOTFOUND | DNS |
| proxy connection failed | Proxy |
| CERT_HAS_EXPIRED, UNABLE_TO_VERIFY_LEAF_SIGNATURE | SSL/TLS |
| HTTP 403, 407, 502, 503, 504 | HTTP/Server |
| npm ERR! network, pip install timeout | Package Manager |
| fatal: unable to access (git) | Git |
Diagnostic Commands
Connectivity: ping <host>, curl -v telnet://<host>:<port>, nc -zv <host> <port>
DNS: nslookup <host>, nslookup <host> 8.8.8.8, dig <host>
Proxy: echo $HTTP_PROXY $HTTPS_PROXY, curl -x http://127.0.0.1:7890 https://www.google.com
SSL: openssl s_client -connect <host>:443 -showcerts </dev/null
HTTP: curl -vvv -o /dev/null -w "%{http_code}" https://<host>/<path>
Package Managers: npm config list, pip config list, git config --list | grep proxy
Resolution Matrix
| Finding | Fix |
|---|---|
| No internet | Check cable/WiFi, restart router |
| DNS fails, 8.8.8.8 works | Change DNS, flush cache |
| Proxy port not listening | Start Clash/V2Ray/SSR |
| Proxy works, target blocked | Switch proxy node |
| SSL cert expired | Renew cert; dev: NODE_TLS_REJECT_UNAUTHORIZED=0 |
| SSL self-signed | Import CA to trust store |
| HTTP 407 | Set proxy credentials |
| HTTP 502/503/504 | Server issue, retry |
| npm timeout | npm config set registry https://registry.npmmirror.com |
| pip timeout | pip config set global.index-url https://pypi.tuna.tsinghua.edu.cn/simple |
| git fails | git config --global http.proxy http://127.0.0.1:7890 |
| docker pull fails | Add mirror to daemon.json |
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.
- 6d ago First seen · 61 lines · 682 tokens per session scan A c3c99ab17b55
RULE is a cursor rule published in the GitHub repository CacinieP/network-troubleshoot-skill (5 stars, last pushed 1mo ago), licensed MIT. It adds 682 tokens to every session, about $0.0034 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-31.
Other cursor rules, from other repositories
error-handling
Error handling: typed errors, boundaries, user messages.
engine-internals
Coding Agent engine implementation details (Cursor + Claude Code) — reference when modifying engine.ts or debugging Agent behavior.
quick-fix
Streamlined fast-path for trivial data-only fixes — no TDD, no branching ceremony. Collapses 6 skills into 2 for changes that are purely data with no logic risk. Aborts with fallback to investigate-bug if guardrails trigger.
mcp-debugging
The mcp-debug agent provides essential tools to test and explore MCP (Model Context Protocol) servers. This guide focuses on using the agent to debug MCP server behavior and functionality.
fastapi-middleware
A small set of FastAPI rules covering expected errors, middleware, logging, error monitoring, and Pydantic models for checking request and response data.
api-investigation
title: API Endpoint Investigation from OpenAPI/Swagger when.