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 skills/howdeploy/deploychan_mcp/xrayebatornpx skills add howdeploy/deploychan_mcp --skill xrayebatorgit clone --depth 1 https://github.com/howdeploy/deploychan_mcpWrote 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/howdeploy/deploychan_mcp/xrayebator)<a href="https://agentmods.dev/skills/howdeploy/deploychan_mcp/xrayebator"><img src="https://agentmods.dev/badge/skills/howdeploy/deploychan_mcp/xrayebator.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 | $0.00060 | $0.01041 |
| Opus 5 | $0.00030 | $0.00521 |
| Sonnet 5 | $0.00012 | $0.00208 |
| Haiku 4.5 | $0.00006 | $0.00104 |
Grade B, and why
Xrayebator: your own VPN on a VPS (Xray Reality) scanned grade B 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 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo bash xrayebator How it starts
The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Xrayebator — your own VPN on a VPS (Xray Reality)
A single script spins up and manages an Xray Reality VPN on your VPS. The tech is VLESS +
REALITY: traffic is indistinguishable from an ordinary HTTPS connection to a real site, with no
domain or certificate of your own. Ordinary protocols (OpenVPN, WireGuard, Shadowsocks) get
caught by DPI on their signature; REALITY masquerades as legitimate TLS to someone else's site —
and so it doesn't get flagged by packet inspection. Public: howdeploy/Xrayebator (v2.0), MIT.
Legality. Your own VPN for privacy and access to your own services is legitimate in many countries, but not everywhere. This is for personal access and research, not for breaking the law. Check your local rules; responsibility for use is on the user.
Why this is in deploychan
Some services are unavailable from your region or flag public VPNs. The agent-internet and
agent-voice guides point right at this: research APIs, the browser, ElevenLabs, Stripe may not
work from within your region. Xrayebator gives you your own clean exit — the agent runs
research and the browser through your VPS, not through a flagged public VPN. Your own VPN = your
own control.
Install and management
The script is interactive — run it on a clean VPS as root:
git clone https://github.com/howdeploy/Xrayebator.git
cd Xrayebator
sudo bash xrayebator
First run — installation (installs Xray-core, generates Reality keys, brings up the node). Every subsequent run — a management menu:
- Install — deploy Xray Reality on this VPS.
- Add client — generate a new client (VLESS link + QR).
- Remove — remove a client or tear down Xray.
Keys and config live in /usr/local/etc/xray/. Masking is configured via the SNI list (which
real site the connection mimics).
Transport profiles
v2.0 supports several combinations for different network and DPI conditions:
- VLESS + TCP + Reality + Vision — the baseline, the most stable.
- + Mux / + uTLS — multiplexing and TLS-fingerprint spoofing.
- VLESS + XHTTP + Reality — an HTTP wrapper, more resilient where TCP gets cut.
- VLESS + gRPC + Reality — gRPC transport (careful, slower).
- VLESS PQ encryption (
mlkem768x25519plus) — post-quantum encryption.
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 · 95 lines · 60 tokens per session scan B 2434d230fcf3
Xrayebator: your own VPN on a VPS (Xray Reality) is a skill published in the GitHub repository howdeploy/deploychan_mcp (11 stars, last pushed 6d ago), licensed MIT. It adds 60 tokens to every session and 1,041 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
vpn-verify
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-troubleshoot
VPN troubleshooting decision tree. Use when user reports VPN problems: 'VPN not working', 'can't connect', 'stopped working', 'no internet through VPN', 'slow VPN', 'troubleshoot'. Also use when deployment fails.
vpn-security-check
Infrastructure security audit for VPN server. Use when user asks 'check security', 'is my VPN safe', 'audit security', 'security check'. Also use after deployment when user has security concerns.
vpn-deploy
Guided VPN deployment wizard. Use when user says 'deploy VPN', 'deploy my VPN', 'set up VPN', 'install VPN'. Also use when opening the project for the first time and user wants to get started.
ship-release
Drive a Telepresence release from a prepared branch all the way through CI, docs, the Releases workflow, and PR merges. Assumes make prepare-release has already been run locally and the branch with that commit was pushed and a PR opened. Use when the user says "ship the release", or "complete the release". User-only.
aws-investigation
Investigates AWS infrastructure issues affecting Buildkite build agents (EC2, AutoScaling, Lambda). Returns structured JSON to the parent for formatting. Triggers when users ask about build agents not running, EC2 issues, ASG scaling problems, or infrastructure health.