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-verify/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-verify)<a href="https://agentmods.dev/skills/sergei-thinker/vpn-setup/vpn-verify"><img src="https://agentmods.dev/badge/skills/sergei-thinker/vpn-setup/vpn-verify/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-verify"><img src="https://agentmods.dev/badge/skills/sergei-thinker/vpn-setup/vpn-verify.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.00040 | $0.01068 |
| Opus 5 | $0.00020 | $0.00534 |
| Sonnet 5 | $0.00008 | $0.00214 |
| Haiku 4.5 | $0.00004 | $0.00107 |
Grade A, and why
vpn-verify 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 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.
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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VPN Deployment Verification
Mandatory verification checklist after ANY deployment or change to VPN infrastructure. No completion claims without fresh evidence.
When to Use
AUTOMATICALLY (do not wait for user to ask):
- After running
ssh_exec.py deploy quick-rebuild.sh - After running any
deploy-*.shscript - After
ssh_exec.py restart - Before saying "done", "deployed", "VPN is ready", or any success claim
On request:
- User asks "is it working?", "did it deploy correctly?"
- User asks to verify/check the VPN
The Iron Law
NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE
If you haven't run ssh_exec.py status in THIS message, you cannot claim deployment succeeded.
"Should be working" is not verification. Run the command.
Verification Checklist
Execute ALL checks. Report results as pass/fail with evidence.
Check 1: Xray Process Running
Command: python ssh_exec.py status
| Output | Result |
|---|---|
| Shows "xray" with "running" status | PASS |
| Shows "stopped", "failed", or no xray info | FAIL -> python ssh_exec.py restart, then re-check |
| SSH connection error | FAIL -> run vpn-troubleshoot |
Check 2: VLESS URIs Generated
What to verify: Deployment script output contained at least one line starting with vless://
| Condition | Result |
|---|---|
| 1+ VLESS URIs captured from deploy output | PASS |
| No URIs in output | FAIL -> check deploy logs, may need to re-run |
Check 3: Server IP Matches Config
What to verify: The IP address in the VLESS URI matches VPN_HOST in .env
How: Read .env, extract VPN_HOST, compare with the IP in captured VLESS URIs.
| Condition | Result |
|---|---|
| IPs match | PASS |
| IPs differ | FAIL -> .env may be outdated or URI is from old deployment |
Check 4: SSH Port Changed
Command: Check VPN_SSH_PORT in .env OR run python ssh_exec.py exec "grep -E '^Port ' /etc/ssh/sshd_config"
| Condition | Result |
|---|---|
| SSH port is NOT 22 (typically 49152) | PASS |
| SSH port is still 22 | WARN -> "TSPU can block port 22 to foreign IPs. Consider changing." |
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 · 127 lines · 40 tokens per session scan A 1efd0bc65932
vpn-verify is a skill published in the GitHub repository Sergei-thinker/vpn-setup (184 stars, last pushed 4mo ago), licensed MIT. It adds 40 tokens to every session and 1,068 once invoked, about $0.0002 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.
setup-3xui
Install and manage 3X-UI panels for VPS-based VLESS Reality services. Use when the user provides a VPS IP/host, SSH username, password, SSH port, and system version and asks Codex to 搭建 3X-UI, install a 3X-UI/X-UI panel, create a backend management Word document, add a customer/client node, associate a client with an…
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.