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/therealaleph/masterhttprelayvpn-rust/maintainernpx skills add therealaleph/MasterHttpRelayVPN-RUST --skill maintainergit clone --depth 1 https://github.com/therealaleph/MasterHttpRelayVPN-RUSTWrote 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/therealaleph/masterhttprelayvpn-rust/maintainer)<a href="https://agentmods.dev/skills/therealaleph/masterhttprelayvpn-rust/maintainer"><img src="https://agentmods.dev/badge/skills/therealaleph/masterhttprelayvpn-rust/maintainer.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.00000 | $0.02355 |
| Opus 5 | $0.00000 | $0.01177 |
| Sonnet 5 | $0.00000 | $0.00471 |
| Haiku 4.5 | $0.00000 | $0.00235 |
Grade A, and why
maintainer 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 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.
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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
mhrv-rs maintenance
This document encodes the project context, recurring patterns, and conventions needed to ship code, triage issues, and respond to users effectively. It is the entry point to the broader knowledge base in references/.
Why this matters
mhrv-rs is infrastructure for circumvention. The bulk of the userbase is in Iran — under one of the world's heaviest internet censorship regimes — using this tool to reach YouTube, Wikipedia, Telegram, GitHub, news sites, banking, and (critically) to communicate with family abroad. A non-trivial fraction of users are in Russia, China, Belarus, and other censored networks, but Iran dominates the issue tracker.
The architecture's importance is the architecture itself: by routing traffic through Google Apps Script, the user's ISP only sees encrypted HTTPS to Google IPs (216.239.38.120 etc.) — the exact same fingerprint as www.google.com. ISPs that block conventional VPNs are forced to either let mhrv-rs through or break Google access for the entire country. This asymmetry is what makes the project work, and it shapes every architectural decision.
When responding to a Persian-language issue, the responder is often the only English-speaking maintainer the reporter has access to. Be clear, generous, and specific. When shipping a release, you're shipping it to people for whom the alternative is not "use a different tool" but "lose internet access". This drives the project's bias toward shipping over polish, toward backwards-compatible defaults, and toward documenting workarounds even when the proper fix is months away.
Working directory and conventions
This is a standard Rust project. cd into your local clone before running git/gh/cargo commands, or use absolute paths. Reply markdown files for gh issue comment --body-file are conventionally written to a temporary file (e.g., /tmp/...) before posting, to avoid HEREDOC quoting issues with backticks and $() substitutions.
Reference files (read as needed)
What ships with it
11 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- assets/changelog-template.md 1.3 KB
- assets/reply-marker.md 72 B
- README.md 1.4 KB
- references/architecture.md 12 KB
- references/contributors.md 7.0 KB
- references/diagnostic-taxonomy.md 10.0 KB
- references/issue-patterns.md 19 KB
- references/persian-templates.md 20 KB
- references/release-workflow.md 8.9 KB
- references/roadmap.md 9.3 KB
- references/workflow-conventions.md 11 KB
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 · 115 lines · 0 tokens per session scan A 2a9202812620
maintainer is a skill published in the GitHub repository therealaleph/MasterHttpRelayVPN-RUST (3,572 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,355 tokens. 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
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.
regression-tests
Run, scope, or debug telepresence regression tests under regressiontest/ — the integration-level suite. Use when the user wants to run an area, suite, or single test, debug a failure, or says "/regression-tests". Runs go test ./regressiontest scoped with -run, in the background, writing to a log file so heavy output…
changelog-entry
Add a new entry to CHANGELOG.yml under the current unreleased version (or create the version block if needed), then regenerate documentation. Use when the user says things like "add a changelog entry", "log this fix in the changelog", or "/changelog-entry".
prepare-release
Create the local release commit and tags by setting TELEPRESENCEVERSION and running make prepare-release. Stops at the local commit+tags - pushing is the ship-release skill's job. Use when the user explicitly asks to prepare a release, RC, or test build. User-only.
codex-e2e-test
Run PR-grade real Codex E2E validation through claude-tap, including resume turns, multiple tool calls, optional image input, viewer verification, and screenshot evidence.
build-wasm
Build the WASM plugins for Envoy. Use when WASM plugin code changes.