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 skills add LuuOW/meridian-mcp --skill wireguardgit clone --depth 1 https://github.com/LuuOW/meridian-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/luuow/meridian-mcp/wireguard)<a href="https://agentmods.dev/skills/luuow/meridian-mcp/wireguard"><img src="https://agentmods.dev/badge/skills/luuow/meridian-mcp/wireguard/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.
<a href="https://agentmods.dev/skills/luuow/meridian-mcp/wireguard"><img src="https://agentmods.dev/badge/skills/luuow/meridian-mcp/wireguard.svg" alt="Reviewed on agentmods" width="80" 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.00041 | $0.01913 |
| Opus 5 | $0.00020 | $0.00957 |
| Sonnet 5 | $0.00008 | $0.00383 |
| Haiku 4.5 | $0.00004 | $0.00191 |
Grade B, and why
wireguard 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 6d 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.
chmod 600 /etc/wireguard/private.key How it starts
The opening of the file, as written. The whole thing — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
wireguard
Production WireGuard VPN for securing admin access to VPS infrastructure. Covers server setup, client configuration, key lifecycle, routing topologies, and systemd persistence.
Key Generation
# Install
apt install wireguard
# Generate a key pair (do this for every peer — server and each client)
wg genkey | tee /etc/wireguard/private.key | wg pubkey > /etc/wireguard/public.key
chmod 600 /etc/wireguard/private.key
# Pre-shared key (optional, adds post-quantum resistance)
wg genpsk > /etc/wireguard/psk.key
chmod 600 /etc/wireguard/psk.key
# View keys
cat /etc/wireguard/public.key
Key hygiene:
- Private keys never leave the machine they were generated on
- Pre-shared key must be the same on both peers — share via encrypted channel (not chat)
- Rotate keys by regenerating the pair and re-distributing the new public key to all peers
Server Configuration
# /etc/wireguard/wg0.conf — server (hub in a hub-and-spoke topology)
[Interface]
Address = 10.8.0.1/24
ListenPort = 51820
PrivateKey = <server-private-key>
# Enable NAT so VPN clients can reach the internet through the server
PostUp = iptables -A FORWARD -i wg0 -j ACCEPT; \
iptables -A FORWARD -o wg0 -j ACCEPT; \
iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
PostDown = iptables -D FORWARD -i wg0 -j ACCEPT; \
iptables -D FORWARD -o wg0 -j ACCEPT; \
iptables -t nat -D POSTROUTING -o eth0 -j MASQUERADE
# ── Peer: developer laptop ──
[Peer]
PublicKey = <client-public-key>
PresharedKey = <psk> # optional
AllowedIPs = 10.8.0.2/32 # this peer's VPN IP only
# ── Peer: CI server ──
[Peer]
PublicKey = <ci-public-key>
AllowedIPs = 10.8.0.3/32
# Requires IP forwarding — verify it's on
sysctl net.ipv4.ip_forward # should be 1
# Make permanent:
echo 'net.ipv4.ip_forward=1' >> /etc/sysctl.d/99-wireguard.conf
sysctl -p /etc/sysctl.d/99-wireguard.conf
Client Configuration
# /etc/wireguard/wg0.conf — client (split-tunnel: only internal ranges via VPN)
[Interface]
Address = 10.8.0.2/24
PrivateKey = <client-private-key>
DNS = 10.8.0.1 # use server as DNS resolver (optional)
[Peer]
PublicKey = <server-public-key>
PresharedKey = <psk>
Endpoint = server-ip:51820
AllowedIPs = 10.8.0.0/24, 10.0.0.0/8 # split-tunnel: only VPN + internal ranges
PersistentKeepalive = 25 # keep NAT open (set if behind NAT)
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.
- 6d ago First seen · 206 lines · 41 tokens per session scan B dc9c97be000e
wireguard is a skill published in the GitHub repository LuuOW/meridian-mcp (0 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 1,913 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
vpn
A guide to setting up and managing VPNs, private network connections that protect or route traffic between devices and servers. It covers WireGuard, OpenVPN, and IPsec, with emphasis on WireGuard commands and configuration.
pilot-api-gateway-manager-setup
Deploy an API gateway management system with 4 agents. Use this skill when: 1. User wants to set up API gateway management with service discovery, routing, auth, and monitoring 2. User is configuring agents for API request routing, rate limiting, or backend health tracking 3. User asks about API gateway pipelines…
install-watchdog
Installs egregore watchdog daemon via launchd or systemd for autonomous relaunching. Use when setting up egregore on a new machine. Do not use on CI/CD runners.
aws-network-ops
AWS cloud networking — VPC, Transit Gateway, Cloud WAN, VPN, Network Firewall, ENI, flow logs. Use when auditing AWS VPCs, troubleshooting connectivity between EC2 instances, checking Transit Gateway routes, or investigating VPN tunnel status.
azure-network-ops
Azure cloud networking -- VNets, NSGs, ExpressRoute, VPN Gateways, Azure Firewalls, Load Balancers, Application Gateways, Route Tables, Network Watcher, Private Endpoints, DNS zones. Use when auditing Azure VNets, troubleshooting hybrid connectivity (ExpressRoute/VPN), checking NSG rules, inspecting firewall policies…
cis-aws-compute-2.9
Ensure use of AWS Systems Manager to manage EC2 instances.