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.
curl -O https://raw.githubusercontent.com/MotherofallVPNs/MoaV/main/.claude/skills/moav-e2e/SKILL.mdgit clone --depth 1 https://github.com/MotherofallVPNs/MoaVWrote 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/motherofallvpns/moav/moav-e2e)<a href="https://agentmods.dev/skills/motherofallvpns/moav/moav-e2e"><img src="https://agentmods.dev/badge/skills/motherofallvpns/moav/moav-e2e.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.1 | $0.00122 | $0.02083 |
| Opus 5 | $0.00061 | $0.01042 |
| Sonnet 5 | $0.00024 | $0.00417 |
| Haiku 4.5 | $0.00012 | $0.00208 |
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 7d 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`. 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 themoavtool (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
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.
- 7d ago First seen · 125 lines · 122 tokens per session scan B 90474833c529
moav-e2e is a skill published in the GitHub repository MotherofallVPNs/MoaV (429 stars, last pushed yesterday), licensed MIT. It adds 122 tokens to every session and 2,083 once invoked, about $0.0006 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
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…
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.
test-warp-ui
Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…
pyats-dynamic-test
Generate and execute deterministic pyATS aetest validation scripts - interface state, OSPF neighbors, BGP paths, ping matrices, and custom compliance tests. Use when writing a network test, validating post-change state, running pass/fail checks, or building automated regression tests.
trailblaze
Use when working with Trailblaze — natural-language device control for coding agents across iOS, Android, and web, with replayable .trail.yaml files as the artifact. Trigger on mentions of Trailblaze, the trailblaze CLI, .trail.yaml files, trailmaps, waypoints, or requests to drive / author / debug / run UI tests on…