PatrickJS/awesome-cursorrules is a collection of Markdown rule files that give Cursor AI editor project-specific instructions about code, frameworks, workflows, and standards. Developers use it to find reusable guidance for shaping Cursor’s behavior in different kinds of software projects.
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 agentmods add rules/patrickjs/awesome-cursorrules/network-troubleshootgit clone --depth 1 https://github.com/PatrickJS/awesome-cursorrulesWrote 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/patrickjs/awesome-cursorrules/network-troubleshoot)<a href="https://agentmods.dev/rules/patrickjs/awesome-cursorrules/network-troubleshoot"><img src="https://agentmods.dev/badge/rules/patrickjs/awesome-cursorrules/network-troubleshoot.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.01865 | $0.01865 |
| Opus 5 | $0.00932 | $0.00932 |
| Sonnet 5 | $0.00373 | $0.00373 |
| Haiku 4.5 | $0.00186 | $0.00186 |
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 3d 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 Copies of this mod
1 near-identical copy found in the catalogue:
- network-troubleshoot — 91% identical, 75 lines differ
How it starts
The opening of the file, as written. The whole thing — 184 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 from config, or raw config values in shared output.
- Internal hosts and URLs may be collected for target-scoped local diagnostics, but replace them with placeholders before sharing logs or reports unless the user explicitly approves including them.
- 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.
- 3d ago First seen · 184 lines · 1,865 tokens per session scan A f18483af8597
network-troubleshoot is a cursor rule published in the GitHub repository PatrickJS/awesome-cursorrules (40,732 stars, last pushed 3mo ago), licensed CC0-1.0. It adds 1,865 tokens to every session, about $0.0093 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-09-03.
Other cursor rules, from other repositories
typescript-type-safety
Use when encountering TypeScript any types, type errors, or lax type checking - eliminates type holes and enforces strict type safety through proper interfaces, type guards, and module augmentation.
typescript-type-specialist
Enforce strict TypeScript type safety - eliminate all 'any' types, use proper type guards, and maintain zero tolerance for type safety violations.
performance
Performance: profiling-first optimization, caching, bottleneck patterns.
error-handling
Error handling: typed errors, boundaries, user messages.
logging
Logging: structured logs, levels, correlation.
vscode
VS Code: settings, extensions, workspace config.