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/network-troubleshoot)<a href="https://agentmods.dev/rules/caciniep/network-troubleshoot-skill/network-troubleshoot"><img src="https://agentmods.dev/badge/rules/caciniep/network-troubleshoot-skill/network-troubleshoot/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/network-troubleshoot"><img src="https://agentmods.dev/badge/rules/caciniep/network-troubleshoot-skill/network-troubleshoot.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.00000 | $0.01485 |
| Opus 5 | $0.00000 | $0.00743 |
| Sonnet 5 | $0.00000 | $0.00297 |
| Haiku 4.5 | $0.00000 | $0.00148 |
Grade A, and why
network-troubleshoot 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 9d 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.
curl -v telnet://<target-host>:<port> --connect-timeout 5 This is a copy
91% identical to network-troubleshoot — 75 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Network Troubleshoot
Use this rule as a concise decision guide for developer network failures. Keep diagnostics safe, target-scoped, and read-only. Do not turn this rule into an automated remediation toolkit.
Safety Boundaries
- Prefer read-only diagnostics and trusted project-provided diagnostic scripts.
- Use the failing host, URL, registry, or service as the default probe target.
- Ask before probing unrelated external services.
- Do not print proxy URLs, credentials, tokens, auth headers, package index URLs, registry hostnames, internal hosts, or raw config values.
- Do not dump local config from npm, pnpm, yarn, pip, Git, Docker, shell, OS proxy, VPN, or certificate stores.
- Do not disable, bypass, or skip TLS or certificate verification.
- Do not change OS networking, DNS, proxy, package manager, Git, Docker, shell, VPN, or trust-store settings without explicit user approval for the exact action.
Workflow
- Collect: Capture the exact error, failing command, target host/URL/port, OS/shell, proxy/VPN context, and whether the failure affects one target or many.
- Classify: Match the symptom to the most likely category.
- Diagnose: Run only read-only checks scoped to the failing target.
- Explain: Interpret the output before suggesting any fix.
- Advise: Present remediation options as choices and wait for user approval before changing state.
- Verify: Re-run the original failing command or an equivalent target-scoped check.
Error Classification
| Error Pattern | Likely Category |
|---|---|
ECONNREFUSED, ERR_CONNECTION_REFUSED, Connection refused |
Target service or port is not listening |
ECONNRESET, socket hang up, Connection reset |
Connection dropped by target, proxy, firewall, or middlebox |
ETIMEDOUT, ERR_CONNECTION_TIMED_OUT, timed out |
Routing, firewall, proxy, or target availability |
ENOTFOUND, EAI_NONAME, ERR_NAME_NOT_RESOLVED, getaddrinfo |
DNS or hostname issue |
ERR_PROXY_CONNECTION_FAILED, proxy tunnel errors, HTTP 407 |
Proxy configuration or proxy authentication |
UNABLE_TO_VERIFY_LEAF_SIGNATURE, CERT_HAS_EXPIRED, self signed, ERR_CERT_* |
TLS certificate or local trust issue |
HTTP 403 |
Authorization, IP allowlist, CORS, or policy block |
HTTP 502, 503, 504 |
Upstream service, gateway, CDN, or transient server issue |
npm ERR! network, package install timeout, pip timeout |
Package registry, proxy, DNS, or network path issue |
fatal: unable to access, Git fetch/push timeout |
Git remote, proxy, DNS, TLS, or network path issue |
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.
- 9d ago First seen · 129 lines · 1,485 tokens per session scan A c441809316e4
network-troubleshoot is a cursor rule published in the GitHub repository CacinieP/network-troubleshoot-skill (5 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,485 tokens. A static security scan graded it A with 1 finding (makes network calls). It is 91% identical to network-troubleshoot, differing in 75 lines, and is treated as a copy.
Other cursor rules, from other repositories
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.
vscode
VS Code: settings, extensions, workspace config.
40-styling
CSS modules colocated with components, kebab-case filenames. See rules/core/styling.md.
06-error-handling
Cursor rule "06-error-handling" from orbitalsonic/AndroidPilot, covering error handling, never, always, coroutines and validation.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.