Agent skill

Vpn Verify

by Sergei-thinker in Sergei-thinker/vpn-setup

Post-deployment verification checklist for VPN. An agent skill from Sergei-thinker/vpn-setup.

Install Vpn Verify

skills CLI

$ npx skills add Sergei-thinker/vpn-setup --skill vpn-verify -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install Sergei-thinker/vpn-setup vpn-verify --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/Sergei-thinker/vpn-setup.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/vpn-verify .claude/skills/vpn-verify && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "vpn-verify" agent skill from https://github.com/Sergei-thinker/vpn-setup/tree/master/.claude/skills/vpn-verify into .claude/skills/vpn-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vpn-verify", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/Sergei-thinker/vpn-setup/tree/master/.claude/skills/vpn-verify

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add Sergei-thinker/vpn-setup --skill vpn-verify -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install Sergei-thinker/vpn-setup vpn-verify --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Sergei-thinker/vpn-setup.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/vpn-verify .agents/skills/vpn-verify && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "vpn-verify" agent skill from https://github.com/Sergei-thinker/vpn-setup/tree/master/.claude/skills/vpn-verify into .agents/skills/vpn-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vpn-verify", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Sergei-thinker/vpn-setup --skill vpn-verify -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install Sergei-thinker/vpn-setup vpn-verify --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Sergei-thinker/vpn-setup.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/vpn-verify .cursor/skills/vpn-verify && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "vpn-verify" agent skill from https://github.com/Sergei-thinker/vpn-setup/tree/master/.claude/skills/vpn-verify into .cursor/skills/vpn-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vpn-verify", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/Sergei-thinker/vpn-setup.git --path .claude/skills/vpn-verify

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add Sergei-thinker/vpn-setup --skill vpn-verify -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install Sergei-thinker/vpn-setup vpn-verify --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Sergei-thinker/vpn-setup.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/vpn-verify .gemini/skills/vpn-verify && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "vpn-verify" agent skill from https://github.com/Sergei-thinker/vpn-setup/tree/master/.claude/skills/vpn-verify into .gemini/skills/vpn-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vpn-verify", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install Sergei-thinker/vpn-setup vpn-verify

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add Sergei-thinker/vpn-setup --skill vpn-verify -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/Sergei-thinker/vpn-setup.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/vpn-verify .github/skills/vpn-verify && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "vpn-verify" agent skill from https://github.com/Sergei-thinker/vpn-setup/tree/master/.claude/skills/vpn-verify into .github/skills/vpn-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vpn-verify", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Sergei-thinker/vpn-setup --skill vpn-verify -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install Sergei-thinker/vpn-setup vpn-verify --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Sergei-thinker/vpn-setup.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/vpn-verify .opencode/skills/vpn-verify && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "vpn-verify" agent skill from https://github.com/Sergei-thinker/vpn-setup/tree/master/.claude/skills/vpn-verify into .opencode/skills/vpn-verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vpn-verify", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: vpn-verify
GitHub stars: 189
Token cost: ~1k tokens
SKILL.md length: 483 words
Files: 1
Skills in repo: 4
Repo updated: Apr 17, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Post-deployment verification checklist for VPN. An agent skill from Sergei-thinker/vpn-setup.

Works in 5 steps: Present the VLESS URIs clearly → Remind: "Import URI into your VPN client" → Remind: "Enable TUN mode" (critical) → …
Tasks that involve Deployment
SKILL.md covers When to Use, The Iron Law, Verification Checklist and Report Format, plus 2 more sections
Calls python

What it does

Vpn Verify is an agent skill from Sergei-thinker/vpn-setup. Post-deployment verification checklist for VPN. Use AUTOMATICALLY after any deployment action (deploy, rebuild, restart) and BEFORE claiming deployment is complete or successful. Evidence before assertions.

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in DevOps & Cloud, covering Deployment. It works with Python. The repository describes itself as: Multi-layer VPN (VLESS Reality + Yandex Cloud Relay + WebRTC) for bypassing Russian internet censorship. Automated deployment via Claude Code. The licence is MIT.

When your agent uses it

Tasks that involve Deployment

Example prompts

“/vpn-verify”

Requirements

Python 3

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

Present the VLESS URIs clearly
Remind: "Import URI into your VPN client"
Remind: "Enable TUN mode" (critical)
Remind: "Test by opening 2ip.ru — should show VPS country for non-Russian sites"
Point to platform-specific setup guide (client-configs/v2rayn-setup.md for Windows)

What it can do on your machine

Read from SKILL.md and the folder at commit 486bf50. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- python
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Vpn Verify loads about 1k tokens when it runs. Until then it costs about 54 tokens; SKILL.md has 483 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~54
When it runs · the whole SKILL.md, loaded when a task matches: ~1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

NoteMentions a .env fileSKILL.md:57

in the VLESS URI matches `VPN_HOST` in `.env`

NoteMentions a .env fileSKILL.md:59

**How:** Read `.env`, extract `VPN_HOST`, compare with the IP in captured VLESS URIs.

NoteMentions a .env fileSKILL.md:64

| IPs differ | FAIL -> `.env` may be outdated or URI is from old deployment |

NoteMentions a .env fileSKILL.md:68

**Command:** Check `VPN_SSH_PORT` in `.env` OR run `python ssh_exec.py exec "grep -E '^Port ' /etc/ssh/sshd_config"`

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Sergei-thinker/vpn-setup at commit 486bf50, republished under its MIT licence (© Sergei-thinker). 483 words, ~1,040 tokens.

Download SKILL.mdSave it as .claude/skills/vpn-verify/SKILL.md (or your agent's skills folder).

name: vpn-verify
description: Post-deployment verification checklist for VPN. Use AUTOMATICALLY after any deployment action (deploy, rebuild, restart) and BEFORE claiming deployment is complete or successful. Evidence before assertions.

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-*.sh script
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."

Show full SKILL.md (201 more words)Show less

Check 5: Firewall Active

Command: python ssh_exec.py exec "ufw status | head -1"

Output	Result
"Status: active"	PASS
"Status: inactive" or command not found	FAIL -> `python ssh_exec.py exec "ufw --force enable"`

Check 6: Inbound Ports Listening

Command: python ssh_exec.py exec "ss -tnlp | grep xray"

Output	Result
Shows ports 443, 8443, 2053 (at least one)	PASS
No xray ports listening	FAIL -> restart xray, check config

Report Format

After all checks, present a summary:

Результаты проверки деплоя:
  1. Xray процесс:     [PASS/FAIL]
  2. VLESS URI:         [PASS/FAIL]
  3. IP совпадает:      [PASS/FAIL]
  4. SSH порт:          [PASS/WARN]
  5. Firewall:          [PASS/FAIL]
  6. Порты слушают:     [PASS/FAIL]

If ALL pass: provide user with VLESS URIs and client setup instructions. If ANY fail: diagnose the failure, do NOT claim success.

Red Flags — STOP Immediately

You are about to violate this rule if you catch yourself:

Writing "deployed successfully" without running ssh_exec.py status first
Saying "VPN is ready" based on script exit code alone
Assuming firewall is active because the script enables it
Presenting URIs without verifying xray is actually running
Using words like "should work", "probably deployed", "looks good"

After Verification Passes

Tell user (in Russian):

Present the VLESS URIs clearly
Remind: "Import URI into your VPN client"
Remind: "Enable TUN mode" (critical)
Remind: "Test by opening 2ip.ru — should show VPS country for non-Russian sites"
Point to platform-specific setup guide (client-configs/v2rayn-setup.md for Windows)

Files

Just SKILL.md in .claude/skills/vpn-verify of Sergei-thinker/vpn-setup.

Open the folder on GitHubat commit 486bf50

Compare with similar skills

Vpn Verify next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Vpn Verify compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Vpn Verify this skillSergei-thinker/vpn-setup	189	—	~1k	Automated safety check: Notes	MIT	5 mo ago
AWS Cdk Developmentzxkane/aws-skills	367	2 repos	~2.5k	Automated safety check: Pass	MIT	3 mo ago
Azure Architecture Autopilotgithub/awesome-copilot	40k	1 repos	~1.9k	Automated safety check: Pass	MIT	yesterday
Blocks Networkblocksnetwork/blocks-sdk	146	—	~2.3k	Automated safety check: Notes	Proprietary	2 days ago
DDNS Build and Release MaintenanceNewFuture/DDNS	4.7k	—	~444	Automated safety check: Pass	MIT	2 days ago
Generate Ors Envadithya-s-k/FineEnvs	461	—	~2.3k	Automated safety check: Notes	Apache-2.0	2 days ago

Similar skills

AWS Cdk Development
zxkane/aws-skills
AWS Cloud Development Kit (CDK) expert for building cloud infrastructure with TypeScript/Python.
367 GitHub starsUsed in 2 repos~2.5k tokens
DevOps & CloudAuto-check passed
Azure Architecture Autopilot
github/awesome-copilot
Official
Designs Azure infrastructure from a natural-language description, or diagrams an existing resource group, then refines the design through conversation and deploys it with Bicep.
40k GitHub starsUsed in 1 repo~1.9k tokens
DevOps & CloudAuto-check passed
Blocks Network
blocksnetwork/blocks-sdk
Modify, validate, run, register, publish, consume, and troubleshoot agents on Blocks Network.
146 GitHub stars~2.3k tokensUpdated 2 days ago
DevOps & CloudAuto-check: notes
DDNS Build and Release Maintenance
NewFuture/DDNS
Maintains the DDNS project's GitHub Actions, Docker and Nuitka builds, packaging and release preparation without touching publishing credentials.
4.7k GitHub stars~444 tokensUpdated 2 days ago
DevOps & CloudAuto-check passed
Generate Ors Env
adithya-s-k/FineEnvs
Builds an Open Reward Standard (ORS) variant of an RL environment using the official openreward Python package.
461 GitHub stars~2.3k tokensUpdated 2 days ago
DevOps & CloudAuto-check: notes
Google Agents CLI Deploy
pifferologo/cloud-agents-cli
This skill should be used when the user wants to "deploy an agent", "deploy my ADK agent", "set up CI/CD", "configure secrets", "troubleshoot a deployment", or needs guidance on Agent Runtime, Cloud…
129 GitHub starsUsed in 1 repo~6k tokens
DevOps & CloudAuto-check passed

Questions about Vpn Verify

What does Vpn Verify do?

Post-deployment verification checklist for VPN. An agent skill from Sergei-thinker/vpn-setup. Vpn Verify is an agent skill from Sergei-thinker/vpn-setup. Post-deployment verification checklist for VPN.

When should I use Vpn Verify?

Vpn Verify fits situations like: tasks that involve Deployment.

How do I install Vpn Verify in Claude Code?

Run `npx skills add Sergei-thinker/vpn-setup --skill vpn-verify -a claude-code`. Or copy the skill folder (.claude/skills/vpn-verify in Sergei-thinker/vpn-setup) into .claude/skills/vpn-verify in your project. Claude Code loads it when a task matches its description.

How do I install Vpn Verify in Codex?

Run `npx skills add Sergei-thinker/vpn-setup --skill vpn-verify -a codex`. Or copy the skill folder (.claude/skills/vpn-verify in Sergei-thinker/vpn-setup) into .agents/skills/vpn-verify in your project. Codex loads it when a task matches its description.

Can I use Vpn Verify in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Sergei-thinker/vpn-setup --skill vpn-verify -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vpn-verify, .gemini/skills/vpn-verify, .github/skills/vpn-verify and .opencode/skills/vpn-verify in your project.

What does Vpn Verify need to run?

Going by SKILL.md and its folder, Vpn Verify needs the command-line tools its instructions call (python). Our summary lists: Python 3.

Does Vpn Verify access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Vpn Verify safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Vpn Verify use?

Vpn Verify is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Vpn Verify use?

About 1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Vpn Verify?

Skills that share tags, products or a category with Vpn Verify: AWS Cdk Development (zxkane/aws-skills, 367 stars), Azure Architecture Autopilot (github/awesome-copilot, 40k stars), Blocks Network (blocksnetwork/blocks-sdk, 146 stars) and DDNS Build and Release Maintenance (NewFuture/DDNS, 4.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Vpn Verify?

Sergei-thinker (a GitHub user) maintains it in Sergei-thinker/vpn-setup, which has 189 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on April 17, 2026.

Source: Sergei-thinker/vpn-setup on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Vpn Verify

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

VPN Deployment Verification

When to Use

The Iron Law

Verification Checklist

Check 1: Xray Process Running

Check 2: VLESS URIs Generated

Check 3: Server IP Matches Config

Check 4: SSH Port Changed

Check 5: Firewall Active

Check 6: Inbound Ports Listening

Report Format

Red Flags — STOP Immediately

After Verification Passes

Files

Compare with similar skills

Similar skills

More from Sergei-thinker/vpn-setup

Related

Questions about Vpn Verify