Borrowing it
Nothing to install: this file belongs to Sergei-thinker/vpn-setup. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Sergei-thinker/vpn-setup/master/.claude/skills/vpn-troubleshoot/SKILL.mdgit clone --depth 1 https://github.com/Sergei-thinker/vpn-setupWrote 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/sergei-thinker/vpn-setup/vpn-troubleshoot)<a href="https://agentmods.dev/skills/sergei-thinker/vpn-setup/vpn-troubleshoot"><img src="https://agentmods.dev/badge/skills/sergei-thinker/vpn-setup/vpn-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/sergei-thinker/vpn-setup/vpn-troubleshoot"><img src="https://agentmods.dev/badge/skills/sergei-thinker/vpn-setup/vpn-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.00052 | $0.02385 |
| Opus 5 | $0.00026 | $0.01192 |
| Sonnet 5 | $0.00010 | $0.00477 |
| Haiku 4.5 | $0.00005 | $0.00238 |
Grade A, and why
vpn-troubleshoot scanned grade A with 0 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 12d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VPN Troubleshooting
Decision tree for diagnosing and fixing VPN infrastructure problems. For beginners — specific commands and solutions, not abstract methodology.
When to Use
Use when the user reports ANY VPN problem:
- "VPN not working", "can't connect", "stopped working"
- "No internet", "slow speed", "works on Wi-Fi but not LTE"
- Deployment script failed
- Any error message related to VPN
The Iron Law
DIAGNOSE BEFORE FIXING. RUN THE COMMAND BEFORE CLAIMING THE RESULT.
Never suggest a fix without first running diagnostics. Never claim "fixed" without verifying.
Decision Tree
Step 1: Can we SSH to the server?
Run: python ssh_exec.py status
| Result | Diagnosis | Action |
|---|---|---|
| Success (shows xray info) | SSH works | Go to Step 2 |
| "Connection refused" | Port blocked or SSH not running | Go to Branch A |
| "Authentication failed" | Wrong credentials | Go to Branch B |
| "Connection timed out" | VPS down or IP wrong | Go to Branch C |
| "No such file: .env" | Missing config | Tell user to create .env from .env.example |
Branch A: Connection Refused
- Check current SSH port in
.env(VPN_SSH_PORT) - If port is 22: TSPU often blocks port 22 to foreign IPs
- Change
VPN_SSH_PORT=49152in.env - Retry
python ssh_exec.py status
- Change
- If port is 49152 and still refused:
- VPS firewall may block it, or SSH service is down
- Ask user to log into VPS provider's web console and check
Branch B: Authentication Failed
- Check
.envforVPN_SSH_KEYandVPN_SSH_PASS - If using key: verify the key file exists at the specified path
- If using password: ask user to verify password is correct (no extra spaces)
- Common issue: key is for a different server (user changed VPS but kept old key)
Branch C: Connection Timed Out
- Ask user: "Is your VPS running? Check in your provider's dashboard."
- Try ping:
ping -c 3 <VPN_HOST from .env> - If ping works but SSH doesn't: firewall blocks SSH port
- If ping fails: VPS is down, IP is wrong, or ISP blocks the IP entirely
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.
- 12d ago First seen · 208 lines · 52 tokens per session scan A bcb976181d08
vpn-troubleshoot is a skill published in the GitHub repository Sergei-thinker/vpn-setup (186 stars, last pushed 4mo ago), licensed MIT. It adds 52 tokens to every session and 2,385 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
Xrayebator: your own VPN on a VPS (Xray Reality)
Use when the user needs their own VPN/proxy on a VPS to bypass regional blocks or DPI so research APIs and browsers work through a clean exit. One-script Xray VLESS+REALITY installer and client manager.
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…