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 CacinieP/network-troubleshoot-skill --skill network-troubleshootgit 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/skills/caciniep/network-troubleshoot-skill/network-troubleshoot)<a href="https://agentmods.dev/skills/caciniep/network-troubleshoot-skill/network-troubleshoot"><img src="https://agentmods.dev/badge/skills/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/skills/caciniep/network-troubleshoot-skill/network-troubleshoot"><img src="https://agentmods.dev/badge/skills/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.00062 | $0.04795 |
| Opus 5.5 | $0.00025 | $0.01918 |
| Sonnet 5.5 | $0.00012 | $0.00959 |
| Haiku 4.5 | $0.00006 | $0.00479 |
Grade C, and why
network-troubleshoot scanned grade C with 3 findings 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 4d 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
curl -X POST -H "Content-Type: application/json" -d '<body>' -vvv https://<host>/<path> Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo systemd-resolve --statistics # Linux systemd Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **Context**: what command triggered it (npm install, git push, curl, browser, app) How it starts
The opening of the file, as written. The whole thing — 396 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Network Troubleshoot Skill
You are a network diagnostics expert. When invoked, systematically diagnose and resolve network issues using the workflow below.
Safety Boundaries
Follow these rules strictly at all times:
- Read-only first. Prefer diagnostics that do not change state. Use the failing host, URL, registry, or service as the default probe target; ask before probing unrelated external services.
- Never print secrets. Do not print proxy URLs, credentials, tokens, auth headers, package index URLs, registry hostnames, internal hosts, or raw config values from npm, pnpm, yarn, pip, Git, Docker, shell, OS proxy, VPN, or certificate stores. Report only whether relevant settings appear present, without values.
- Never bypass TLS on your own initiative. Do not set
NODE_TLS_REJECT_UNAUTHORIZED=0,npm config set strict-ssl false,git config --global http.sslVerify false, orPYTHONHTTPSVERIFY=0without explicit user approval. If a bypass seems necessary, present it as a last-resort, development-only option and wait for approval. - No unapproved state changes. 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.
- Explain before fixing. Present findings clearly before suggesting fixes; remediation options are choices for the user, not automatic actions.
Step 1: Collect Symptom Information
Ask the user or infer from error output:
- Error message: exact text (e.g.,
ECONNREFUSED,ETIMEDOUT,ERR_NAME_NOT_RESOLVED) - Target: what host/port/URL is failing
- Context: what command triggered it (npm install, git push, curl, browser, app)
- Scope: everything or just specific hosts
- Timing: sudden failure or never worked
- Environment: OS, network type (home/office/VPN), proxy usage
If the user provides an error, extract these automatically without asking.
Step 2: Classify the Issue
Match against these categories by error pattern:
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.
- 4d ago First seen · 396 lines · 62 tokens per session scan C b3239ddd42f4
network-troubleshoot is a skill published in the GitHub repository CacinieP/network-troubleshoot-skill (8 stars, last pushed 4d ago), licensed MIT. It adds 62 tokens to every session and 4,795 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it C with 3 findings (sends data to an external url, asks for root, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-21.
Other skills, from other repositories
gh-fix-ci
Use when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions; use gh to inspect checks and logs, summarize failure context, draft a fix plan, and implement only after explicit approval. Treat external providers (for example Buildkite) as out of scope and report only the details URL.
test-failure-explorer
Import and query an existing Vitest 3.2 JSON report to explore test failures, file-level errors and original diagnostic evidence.
feedback
Skill "feedback" from Hmbown/Codewhale, covering feedback, when to use, setup, workflow and non-goals.
ccc
This skill should be used when code search is needed (whether explicitly requested or as part of completing a task), when indexing the codebase after changes, or when the user asks about ccc, cocoindex-code, or the codebase index. Trigger phrases include 'search the codebase', 'find code related to', 'update the…
agents-sdk-dotnet-debugging
Use when troubleshooting an agent built with the Microsoft Agents SDK (Microsoft.Agents.Hosting.AspNetCore and related packages) in C# / .NET. Trigger on any of these symptoms: build or C# compile errors, crashes on startup, 401 or auth errors on incoming requests, the bot not responding to messages, appsettings.json…
claude-delegate
Delegate a coding task to a separate Claude Code CLI process or another Claude session as an implementer, then review its diff and land it yourself. Use only when the user explicitly asks to delegate implementation to Claude Code, another Claude session, or the claude CLI — for example, "have another Claude implement…