A set of end-to-end tests for MoaV, run against a live server rather than simulated services. MoaV is tested as both a network client and a command-line tool.

Use it to validate a branch before release, test protocol connectivity, check the MoaV command-line interface, and investigate connection failures.

It checks whether the real protocols, server connection, security certificates, and command-line workflows work together. This can reveal problems that unit tests and mocked services miss.

How MotherofallVPNs/MoaV configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to MotherofallVPNs/MoaV. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/MotherofallVPNs/MoaV/main/.claude/skills/moav-e2e/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/MotherofallVPNs/MoaV

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/motherofallvpns/moav/moav-e2e/github.svg)](https://agentmods.dev/skills/motherofallvpns/moav/moav-e2e)

Your own site

<a href="https://agentmods.dev/skills/motherofallvpns/moav/moav-e2e"><img src="https://agentmods.dev/badge/skills/motherofallvpns/moav/moav-e2e/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/motherofallvpns/moav/moav-e2e"><img src="https://agentmods.dev/badge/skills/motherofallvpns/moav/moav-e2e.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 122 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,083 The whole file, excluding the scripts and references it only reads on demand.

Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector warn 7 Sept 2026

SkillSpector: 3 findings, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

high Privilege Escalation · line 57
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
medium Privilege Escalation · line 68
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.

Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
medium MCP Rug Pull · line 97
Docker image references without a specific tag (:latest is implicit) or digest (@sha256:...) can be silently replaced by a malicious image.

Fix: Pin the image: image:tag or image@sha256:abc123

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

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.00122	$0.02083
Opus 5.5	$0.00049	$0.00833
Sonnet 5.5	$0.00024	$0.00417
Haiku 4.5	$0.00012	$0.00208

Measured 2mo ago against content hash 90474833c529, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade B, and why

moav-e2e 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 2mo 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 chown -R "$(id -u):$(id -g)" configs state outputs`.

.claude/skills/moav-e2e/SKILL.md · 125 lines

How it starts

The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.

MoaV end-to-end testing

Two layers run against a live server (not mocks):

tests/client-test.sh (moav test <user> [--json] [-v]) — stands up a client-side tunnel per protocol and checks the exit IP. This is the protocol matrix.
tests/cli-smoke-test.sh — exercises the moav tool (help/status/users/doctor/cert/ export→import/user add+revoke/admin password/…), each hang-guarded.

The per-PR CI (ci.yml) only lints + unit-tests; it never brings the stack up. Full e2e is .github/workflows/e2e.yml on a self-hosted runner (a test VPS with a real test domain), because it builds ~25 images and needs real TLS certs. Human setup doc: docs/devdocs/E2E-TESTING.md.

How to run

Preferred: the self-hosted workflow

# domainless — no cert, no Let's Encrypt dependency. Fast to iterate, validates the
# IP-only protocols + the client image build. START HERE when debugging.
gh workflow run e2e.yml -R MotherofallVPNs/moav --ref <branch> -f verbose=true -f domainless=true

# domain — full matrix incl. the TLS-domain protocols (Trojan/Hysteria2/AnyTLS/CDN).
# Reuses the cert across runs; DON'T run more than ~5/week (LE limit).
gh workflow run e2e.yml -R MotherofallVPNs/moav --ref <branch> -f verbose=true

# full — also build --local + a second domainless phase + image-removal uninstall (slow).
gh workflow run e2e.yml -R MotherofallVPNs/moav --ref <branch> -f full=true

Then get the run id and watch it (watch in the background so tool output stays out of context):

sleep 8
gh run list -R MotherofallVPNs/moav --workflow e2e.yml --limit 1 --json databaseId,status
gh run watch <id> -R MotherofallVPNs/moav   # run in background; you're re-invoked on finish

The workflow must live on the default branch (main) for workflow_dispatch to show up; dispatch then runs the selected branch's copy.

Local (on the test VPS itself)

cp .env.example .env      # set DOMAIN, ACME_EMAIL, ADMIN_PASSWORD, SERVER_IP,
                          # INITIAL_USERS=1, DEFAULT_PROFILES=all  (empty DOMAIN = domainless)
./moav.sh build
./moav.sh bootstrap --yes
./moav.sh start all
sleep 45
./moav.sh user add e2e-test
./moav.sh test e2e-test --json   # machine-readable matrix; add -v for per-protocol debug

Read the full file on GitHub · 125 lines

Changes

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.

2mo ago First seen · 125 lines · 122 tokens per session scan B 90474833c529

Subscribe to this mod's changes

moav-e2e is a skill published in the GitHub repository MotherofallVPNs/MoaV (453 stars, last pushed today), licensed MIT. It adds 122 tokens to every session and 2,083 once invoked, about $0.0005 per session on Opus 5.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.

E2E testing Testing circumvention-tool digital-rights infrastructure internet-freedom vpn vpn-manager

ferrogate-test

Use when working in the FerroGate repo and the task involves the ferrogate-test Rust CLI itself — running Admin API or gateway API E2E coverage, CI harness verification, Docker-backed cluster scenarios, editing tools/ferrogate-test, or release-grade end-to-end validation. For deciding which test layer a change needs…

lianluo-esign/ferrogate · 82 tokens

verify-omnigent

Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…

omnigent-ai/omnigent · 100 tokens

test-master

Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…

Jeffallan/claude-skills · 104 tokens

eval-dataset-design

A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.

bojieli/ai-agent-book · 138 tokens

dogfood

Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.

callstack/agent-device · 55 tokens

cua-driver

Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.

davidondrej/skills · 68 tokens

MoaV: Skill for Claude Code