[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BWWJSG6P91MFBW2M0P6ZBR":3,"skill-same:01M7BWWJSG6P91MFBW2M0P6ZBR":63},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":14,"repositoryHtmlUrl":45,"repositoryHomepageUrl":6,"ownerHtmlUrl":46,"ownerBlogUrl":6,"ownerDescription":47,"updatedAt":48,"install":49,"resources":62},"01M7BWWJSG6P91MFBW2M0P6ZBR","pinggy-tunnel",null,"Zero-install localhost tunnels over SSH via Pinggy.","yuxua24\u002Fworkspace","yuxua24","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F145311182?v=4","01M7BWRX3SGTW32KC66ZKHKKJT","Yuxuan Ao","01M7BWRX4GD7VN7NV8WQPWHQJE",0,"MIT","https:\u002F\u002Fgithub.com\u002Fyuxua24\u002Fworkspace\u002Fblob\u002Fautoresearch\u002Fpi-agent-merchantbench-net-assets-workspace-omp-20260901\u002Fhermes-agent\u002Foptional-skills\u002Fdevops\u002Fpinggy-tunnel\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: pinggy-tunnel\ndescription: Zero-install localhost tunnels over SSH via Pinggy.\nversion: 0.1.0\nauthor: Teknium (teknium1), Hermes Agent\nlicense: MIT\nplatforms: [linux, macos, windows]\nmetadata:\n  hermes:\n    tags: [Pinggy, Tunnel, Networking, SSH, Webhook, Localhost]\n    related_skills: [cloudflared-quick-tunnel, webhook-subscriptions]\n---\n\n# Pinggy Tunnel Skill\n\nExpose a local service (dev server, webhook receiver, MCP endpoint, demo) to the public internet using a Pinggy SSH reverse tunnel. No daemon to install — the user's stock SSH client connects to `a.pinggy.io:443` and Pinggy hands back a public HTTP\u002FHTTPS URL.\n\nFree tier: 60-minute tunnels, random subdomain, no signup. Pro tier ($3\u002Fmo) is an opt-in with a token.\n\n## When to Use\n\n- User asks to \"expose this locally\", \"share my dev server\", \"make this URL public\", \"tunnel port N\", \"get a public URL for a webhook\"\n- Need to receive a webhook callback during a local task (Stripe, GitHub, Discord, AgentMail)\n- Sharing a one-off HTTP demo (MCP server, Ollama\u002FvLLM endpoint, dashboard) with a remote party\n- The host has SSH but no `cloudflared` \u002F `ngrok` binary, and installing one would be overkill\n\nIf the host already has `cloudflared` configured, prefer the `cloudflared-quick-tunnel` skill — Cloudflare quick tunnels don't expire after 60 minutes.\n\n## Prerequisites\n\n- `ssh` on PATH (`ssh -V`). Default on Linux, macOS, and Windows 10+. No other install.\n- A local service listening on `127.0.0.1:\u003Cport>` before the tunnel starts. Pinggy will return URLs but they'll 502 until the local origin is up.\n\nOptional:\n\n- `PINGGY_TOKEN` env var for paid Pro features (persistent subdomain, custom domain, multiple tunnels, no 60-minute cap). Free tier needs no credentials.\n\n## Quick Reference\n\n```bash\n# Plain HTTP\u002FHTTPS tunnel for port 8000 (free tier)\nssh -p 443 -o StrictHostKeyChecking=no -o ServerAliveInterval=30 \\\n    -R0:localhost:8000 free@a.pinggy.io\n\n# TCP tunnel (databases, raw SSH, etc.)\nssh -p 443 -o StrictHostKeyChecking=no -R0:localhost:5432 tcp@a.pinggy.io\n\n# TLS tunnel (Pinggy can't decrypt — bring your own certs at origin)\nssh -p 443 -o StrictHostKeyChecking=no -R0:localhost:443 tls@a.pinggy.io\n\n# Basic auth gate (b:user:pass)\nssh -p 443 -o StrictHostKeyChecking=no -R0:localhost:8000 \\\n    \"b:admin:secret+free@a.pinggy.io\"\n\n# Bearer token gate (k:token)\nssh -p 443 -o StrictHostKeyChecking=no -R0:localhost:8000 \\\n    \"k:mysecrettoken+free@a.pinggy.io\"\n\n# IP whitelist (w:CIDR)\nssh -p 443 -o StrictHostKeyChecking=no -R0:localhost:8000 \\\n    \"w:203.0.113.0\u002F24+free@a.pinggy.io\"\n\n# Enable CORS + force HTTPS redirect\nssh -p 443 -o StrictHostKeyChecking=no -R0:localhost:8000 \\\n    \"co+x:https+free@a.pinggy.io\"\n\n# Pro tier (persistent URL, no 60-min cap)\nssh -p 443 -o StrictHostKeyChecking=no -R0:localhost:8000 \"$PINGGY_TOKEN+a.pinggy.io\"\n```\n\n## Procedure — Start a Tunnel and Get the URL\n\nThe model SHOULD use the `terminal` tool. The tunnel must stay alive for the duration of the share, so run it as a background process and parse the public URL from stdout.\n\n### 1. Confirm a local origin is up\n\n```bash\ncurl -sI http:\u002F\u002F127.0.0.1:8000\u002F | head -1\n# expect HTTP\u002F1.x 200 (or any non-connection-refused response)\n```\n\nIf nothing is listening yet, start it first (e.g. `python3 -m http.server 8000 --bind 127.0.0.1`). Pinggy will happily return a URL pointed at nothing — the user will see 502 until the origin comes up.\n\n### 2. Launch the tunnel as a background process\n\nUse `terminal(background=True)` and capture output to a logfile (Pinggy prints the URLs on stdout, then keeps the connection open):\n\n```bash\nLOG=\u002Ftmp\u002Fpinggy-8000.log\nnohup ssh -p 443 \\\n    -o StrictHostKeyChecking=no \\\n    -o UserKnownHostsFile=\u002Fdev\u002Fnull \\\n    -o ServerAliveInterval=30 \\\n    -o ServerAliveCountMax=3 \\\n    -R0:localhost:8000 free@a.pinggy.io \\\n    > \"$LOG\" 2>&1 &\necho $! > \u002Ftmp\u002Fpinggy-8000.pid\n```\n\n`StrictHostKeyChecking=no` + `UserKnownHostsFile=\u002Fdev\u002Fnull` skips the first-run host-key prompt. `ServerAliveInterval=30` keeps the SSH session from getting torn down by an idle NAT.\n\n### 3. Parse the URL out of the log\n\n```bash\nsleep 4\ngrep -oE 'https:\u002F\u002F[a-z0-9-]+\\.[a-z]+\\.pinggy\\.link' \u002Ftmp\u002Fpinggy-8000.log | head -1\n```\n\nExpected output looks like:\n\n```\nYou are not authenticated.\nYour tunnel will expire in 60 minutes.\nhttp:\u002F\u002Fyqycl-98-162-69-48.a.free.pinggy.link\nhttps:\u002F\u002Fyqycl-98-162-69-48.a.free.pinggy.link\n```\n\nHand the `https:\u002F\u002F...pinggy.link` URL to the user.\n\n### 4. Verify\n\n```bash\ncurl -sI https:\u002F\u002F\u003Cthe-url>\u002F | head -3\n# expect 200\u002F302\u002Fwhatever the local origin actually returns\n```\n\nIf you get `502 Bad Gateway`, the SSH session is up but the local origin isn't listening — fix step 1 first.\n\n### 5. Teardown\n\n```bash\nkill \"$(cat \u002Ftmp\u002Fpinggy-8000.pid)\"\n# or, if the pid file got lost:\npkill -f 'ssh -p 443 .* free@a\\.pinggy\\.io'\n```\n\nIf you have a session_id from `terminal(background=True)`, prefer `process(action='kill', session_id=...)`.\n\n## Access Control via Username Keywords\n\nPinggy stacks control flags into the SSH username separated by `+`. Always quote the whole `user@host` argument when it contains a `+`:\n\n| Keyword | Effect |\n|---------|--------|\n| `b:user:pass` | HTTP Basic auth gate |\n| `k:token` | Bearer-token header gate (`Authorization: Bearer \u003Ctoken>`) |\n| `w:CIDR` | IP whitelist (single IP or CIDR, repeatable) |\n| `co` | Add `Access-Control-Allow-Origin: *` (CORS) |\n| `x:https` | Force HTTPS — auto-redirect HTTP to HTTPS |\n| `a:Name:Value` | Add request header |\n| `u:Name:Value` | Update request header |\n| `r:Name` | Remove request header |\n| `qr` | Print a QR code of the URL to stdout (handy for mobile sharing) |\n\nCombine freely: `\"b:admin:secret+co+x:https+free@a.pinggy.io\"`.\n\n## Web Debugger (optional)\n\nPinggy can mirror the inbound traffic to `localhost:4300` for inspection. Add a local forward to the SSH command:\n\n```bash\nssh -p 443 -L4300:localhost:4300 -R0:localhost:8000 free@a.pinggy.io\n```\n\nThen open `http:\u002F\u002Flocalhost:4300` in a browser to see live request\u002Fresponse pairs.\n\n## Pitfalls\n\n- **60-minute hard cap on the free tier.** The SSH session terminates at the 60-minute mark; the URL goes dead. For longer shares, either use `PINGGY_TOKEN` (Pro) or auto-restart with a shell loop (note that the URL changes on every restart for free-tier).\n- **Free-tier URL is random and changes on restart.** Don't bookmark it, don't paste it into a config file. Re-parse from the log each time.\n- **Concurrent free tunnels are limited to one per source IP.** Starting a second tunnel from the same machine usually kills the first. Pro tier lifts this.\n- **`+` in usernames must be quoted.** Bare `ssh ... b:admin:secret+free@a.pinggy.io` works in bash but breaks under shells that treat `+` specially or when assembled programmatically. Always wrap in double quotes.\n- **Don't tunnel anything sensitive without an access-control flag.** A bare HTTP tunnel is reachable by anyone with the URL. Use `b:`, `k:`, or `w:` for non-public services.\n- **`process(action='log')` may miss SSH banner output.** Pinggy prints the URLs and then the SSH session goes interactive. Always redirect to a logfile and `grep` the file directly — same pattern as `cloudflared-quick-tunnel`.\n- **Host-key prompt on first run.** Default OpenSSH config asks the user to accept Pinggy's host key. Always pass `-o StrictHostKeyChecking=no -o UserKnownHostsFile=\u002Fdev\u002Fnull` for unattended runs.\n- **TCP and TLS tunnels return a `\u003Csubdomain>.a.pinggy.online:\u003Cport>` pair, not an https URL.** Parse with a different regex (`tcp:\u002F\u002F` and a port). Don't assume every Pinggy tunnel is HTTP.\n- **Pro mode requires the token as the username, not a flag.** Use `\"$PINGGY_TOKEN+a.pinggy.io\"` (no `free@`). With a token you can also add `:persistent` for a stable subdomain — see `pinggy.io\u002Fdocs\u002F`.\n\n## Recipes\n\nComposite patterns combining a local origin with a Pinggy tunnel. Each recipe is self-contained — start the origin, start the tunnel, parse the URL, hand it back to the user.\n\n### Recipe 1 — Receive a webhook callback\n\nUse this when an external service (Stripe, GitHub, Discord, AgentMail, etc.) needs to POST to a publicly reachable URL during a local task.\n\n```bash\n# 1. Tiny capturing server: every request gets appended to \u002Ftmp\u002Fwebhook-hits.log\ncat >\u002Ftmp\u002Fwebhook-server.py \u003C\u003C'PY'\nimport http.server, json, datetime, pathlib\nLOG = pathlib.Path(\"\u002Ftmp\u002Fwebhook-hits.log\")\nclass H(http.server.BaseHTTPRequestHandler):\n    def _capture(self):\n        n = int(self.headers.get(\"content-length\") or 0)\n        body = self.rfile.read(n).decode(\"utf-8\", \"replace\") if n else \"\"\n        rec = {\"t\": datetime.datetime.utcnow().isoformat(), \"path\": self.path,\n               \"method\": self.command, \"headers\": dict(self.headers), \"body\": body}\n        with LOG.open(\"a\") as f: f.write(json.dumps(rec) + \"\\n\")\n        self.send_response(200); self.send_header(\"content-type\",\"application\u002Fjson\")\n        self.end_headers(); self.wfile.write(b'{\"ok\":true}\\n')\n    def do_GET(self): self._capture()\n    def do_POST(self): self._capture()\n    def log_message(self,*a,**k): pass\nhttp.server.HTTPServer((\"127.0.0.1\", 18080), H).serve_forever()\nPY\nnohup python3 \u002Ftmp\u002Fwebhook-server.py >\u002Ftmp\u002Fwebhook-server.log 2>&1 &\necho $! >\u002Ftmp\u002Fwebhook-server.pid\n\n# 2. Tunnel — bearer-token-gate so randos can't pollute the capture log\nnohup ssh -p 443 -o StrictHostKeyChecking=no -o UserKnownHostsFile=\u002Fdev\u002Fnull \\\n    -o ServerAliveInterval=30 \\\n    -R0:localhost:18080 \"k:$(openssl rand -hex 12)+free@a.pinggy.io\" \\\n    >\u002Ftmp\u002Fwebhook-pinggy.log 2>&1 &\necho $! >\u002Ftmp\u002Fwebhook-pinggy.pid\nsleep 5\nURL=$(grep -oE 'https:\u002F\u002F[a-z0-9-]+\\.[a-z]+\\.pinggy\\.link' \u002Ftmp\u002Fwebhook-pinggy.log | head -1)\necho \"Webhook URL: $URL\"\n\n# 3. While the agent works, watch hits land\ntail -f \u002Ftmp\u002Fwebhook-hits.log\n```\n\nHand `$URL` to the service that needs to call you. Teardown: `kill $(cat \u002Ftmp\u002Fwebhook-server.pid) $(cat \u002Ftmp\u002Fwebhook-pinggy.pid)`.\n\n### Recipe 2 — Expose an MCP server over HTTP\u002FSSE\n\nUse when a remote MCP client (Claude Desktop on another machine, a teammate's editor, etc.) needs to reach an MCP server running on the local box. Only works for MCP servers that speak HTTP transport — stdio-mode servers can't be tunneled.\n\n```bash\n# 1. Start the MCP server in HTTP mode (example: a FastMCP server on port 8765)\nnohup python3 my_mcp_server.py --transport http --port 8765 \\\n    >\u002Ftmp\u002Fmcp-server.log 2>&1 &\necho $! >\u002Ftmp\u002Fmcp-server.pid\n\n# 2. Tunnel with a bearer token — MCP traffic should not be open to the internet\nTOKEN=$(openssl rand -hex 16)\nnohup ssh -p 443 -o StrictHostKeyChecking=no -o UserKnownHostsFile=\u002Fdev\u002Fnull \\\n    -o ServerAliveInterval=30 \\\n    -R0:localhost:8765 \"k:$TOKEN+free@a.pinggy.io\" \\\n    >\u002Ftmp\u002Fmcp-pinggy.log 2>&1 &\necho $! >\u002Ftmp\u002Fmcp-pinggy.pid\nsleep 5\nURL=$(grep -oE 'https:\u002F\u002F[a-z0-9-]+\\.[a-z]+\\.pinggy\\.link' \u002Ftmp\u002Fmcp-pinggy.log | head -1)\necho \"MCP URL: $URL\"\necho \"Bearer token: $TOKEN\"\n```\n\nThe remote client connects to `$URL` with `Authorization: Bearer $TOKEN`. Hermes' own native MCP client config: `{\"transport\": \"http\", \"url\": \"\u003CURL>\", \"headers\": {\"Authorization\": \"Bearer \u003CTOKEN>\"}}`.\n\n### Recipe 3 — Expose a local LLM endpoint (Ollama \u002F vLLM \u002F llama.cpp)\n\nShare a local model with a remote caller (another agent, a phone, a teammate). Ollama listens on `:11434`, vLLM and llama.cpp typically on `:8000`.\n\n```bash\n# Pre-req: the model server is already running on 127.0.0.1:11434 (Ollama default)\nTOKEN=$(openssl rand -hex 16)\nnohup ssh -p 443 -o StrictHostKeyChecking=no -o UserKnownHostsFile=\u002Fdev\u002Fnull \\\n    -o ServerAliveInterval=30 \\\n    -R0:localhost:11434 \"k:$TOKEN+co+free@a.pinggy.io\" \\\n    >\u002Ftmp\u002Fllm-pinggy.log 2>&1 &\necho $! >\u002Ftmp\u002Fllm-pinggy.pid\nsleep 5\nURL=$(grep -oE 'https:\u002F\u002F[a-z0-9-]+\\.[a-z]+\\.pinggy\\.link' \u002Ftmp\u002Fllm-pinggy.log | head -1)\necho \"Endpoint: $URL\"\necho \"Token:    $TOKEN\"\n\n# Verify\ncurl -s \"$URL\u002Fapi\u002Ftags\" -H \"Authorization: Bearer $TOKEN\" | head\n```\n\n`co` enables CORS so a browser caller can hit the endpoint. Drop `co` for backend-only callers. For an OpenAI-compatible vLLM\u002Fllama.cpp endpoint, callers use base URL `$URL\u002Fv1` with `Authorization: Bearer $TOKEN` — but note Pinggy strips\u002Freplaces nothing in the body, so the model server itself sees Pinggy's token; the local server should be configured to ignore auth (it's already on `127.0.0.1`) and let Pinggy do the gating.\n\n### Recipe 4 — Share a dev server with a one-shot password\n\nThe fastest \"let a teammate poke at my running app\" pattern. Random password, prints once, dies when you Ctrl-C.\n\n```bash\nPASS=$(openssl rand -base64 12 | tr -d '+\u002F=' | head -c 12)\necho \"Dev server password: $PASS\"\nssh -p 443 -o StrictHostKeyChecking=no -o UserKnownHostsFile=\u002Fdev\u002Fnull \\\n    -o ServerAliveInterval=30 \\\n    -R0:localhost:3000 \"b:dev:$PASS+co+x:https+free@a.pinggy.io\"\n# URL prints to the terminal. Share URL + password. Ctrl-C to tear down.\n```\n\n`b:dev:$PASS` gates the URL with HTTP Basic auth. `x:https` forces TLS. `co` adds CORS for SPA frontends.\n\n## Verification\n\n```bash\n# End-to-end: spin up a trivial origin, tunnel it, hit it, tear down\npython3 -m http.server 18000 --bind 127.0.0.1 >\u002Ftmp\u002Forigin.log 2>&1 &\nORIGIN_PID=$!\n\nnohup ssh -p 443 \\\n    -o StrictHostKeyChecking=no \\\n    -o UserKnownHostsFile=\u002Fdev\u002Fnull \\\n    -R0:localhost:18000 free@a.pinggy.io >\u002Ftmp\u002Fpinggy-verify.log 2>&1 &\nSSH_PID=$!\n\nsleep 5\nURL=$(grep -oE 'https:\u002F\u002F[a-z0-9-]+\\.[a-z]+\\.pinggy\\.link' \u002Ftmp\u002Fpinggy-verify.log | head -1)\necho \"URL: $URL\"\ncurl -sI \"$URL\u002F\" | head -1\n\nkill \"$SSH_PID\" \"$ORIGIN_PID\"\n```\n\nExpected: a `pinggy.link` URL and `HTTP\u002F2 200` on the curl head.\n","# Pinggy Tunnel Skill\n\nExpose a local service (dev server, webhook receiver, MCP endpoint, demo) to the public internet using a Pinggy SSH reverse tunnel. No daemon to install — the user's stock SSH client connects to `a.pinggy.io:443` and Pinggy hands back a public HTTP\u002FHTTPS URL.\n\nFree tier: 60-minute tunnels, random subdomain, no signup. Pro tier ($3\u002Fmo) is an opt-in with a token.\n\n## When to Use\n\n- User asks to \"expose this locally\", \"share my dev server\", \"make this URL public\", \"tunnel port N\", \"get a public URL for a webhook\"\n- Need to receive a webhook callback during a local task (Stripe, GitHub, Discord, AgentMail)\n- Sharing a one-off HTTP demo (MCP server, Ollama\u002FvLLM endpoint, dashboard) with a remote party\n- The host has SSH but no `cloudflared` \u002F `ngrok` binary, and installing one would be overkill\n\nIf the host already has `cloudflared` configured, prefer the `cloudflared-quick-tunnel` skill — Cloudflare quick tunnels don't expire after 60 minutes.\n\n## Prerequisites\n\n- `ssh` on PATH (`ssh -V`). Default on Linux, macOS, and Windows 10+. No other install.\n- A local service listening on `127.0.0.1:\u003Cport>` before the tunnel starts. Pinggy will return URLs but they'll 502 until the local origin is up.\n\nOptional:\n\n- `PINGGY_TOKEN` env var for paid Pro features (persistent subdomain, custom domain, multiple tunnels, no 60-minute cap). Free tier needs no credentials.\n\n## Quick Reference\n\n```bash\n# Plain HTTP\u002FHTTPS tunnel for port 8000 (free tier)\nssh -p 443 -o StrictHostKeyChecking=no -o ServerAliveInterval=30 \\\n    -R0:localhost:8000 free@a.pinggy.io\n\n# TCP tunnel (databases, raw SSH, etc.)\nssh -p 443 -o StrictHostKeyChecking=no -R0:localhost:5432 tcp@a.pinggy.io\n\n# TLS tunnel (Pinggy can't decrypt — bring your own certs at origin)\nssh -p 443 -o StrictHostKeyChecking=no -R0:localhost:443 tls@a.pinggy.io\n\n# Basic auth gate (b:user:pass)\nssh -p 443 -o StrictHostKeyChecking=no -R0:localhost:8000 \\\n    \"b:admin:secret+free@a.pinggy.io\"\n\n# Bearer token gate (k:token)\nssh -p 443 -o StrictHostKeyChecking=no -R0:localhost:8000 \\\n    \"k:mysecrettoken+free@a.pinggy.io\"\n\n# IP whitelist (w:CIDR)\nssh -p 443 -o StrictHostKeyChecking=no -R0:localhost:8000 \\\n    \"w:203.0.113.0\u002F24+free@a.pinggy.io\"\n\n# Enable CORS + force HTTPS redirect\nssh -p 443 -o StrictHostKeyChecking=no -R0:localhost:8000 \\\n    \"co+x:https+free@a.pinggy.io\"\n\n# Pro tier (persistent URL, no 60-min cap)\nssh -p 443 -o StrictHostKeyChecking=no -R0:localhost:8000 \"$PINGGY_TOKEN+a.pinggy.io\"\n```\n\n## Procedure — Start a Tunnel and Get the URL\n\nThe model SHOULD use the `terminal` tool. The tunnel must stay alive for the duration of the share, so run it as a background process and parse the public URL from stdout.\n\n### 1. Confirm a local origin is up\n\n```bash\ncurl -sI http:\u002F\u002F127.0.0.1:8000\u002F | head -1\n# expect HTTP\u002F1.x 200 (or any non-connection-refused response)\n```\n\nIf nothing is listening yet, start it first (e.g. `python3 -m http.server 8000 --bind 127.0.0.1`). Pinggy will happily return a URL pointed at nothing — the user will see 502 until the origin comes up.\n\n### 2. Launch the tunnel as a background process\n\nUse `terminal(background=True)` and capture output to a logfile (Pinggy prints the URLs on stdout, then keeps the connection open):\n\n```bash\nLOG=\u002Ftmp\u002Fpinggy-8000.log\nnohup ssh -p 443 \\\n    -o StrictHostKeyChecking=no \\\n    -o UserKnownHostsFile=\u002Fdev\u002Fnull \\\n    -o ServerAliveInterval=30 \\\n    -o ServerAliveCountMax=3 \\\n    -R0:localhost:8000 free@a.pinggy.io \\\n    > \"$LOG\" 2>&1 &\necho $! > \u002Ftmp\u002Fpinggy-8000.pid\n```\n\n`StrictHostKeyChecking=no` + `UserKnownHostsFile=\u002Fdev\u002Fnull` skips the first-run host-key prompt. `ServerAliveInterval=30` keeps the SSH session from getting torn down by an idle NAT.\n\n### 3. Parse the URL out of the log\n\n```bash\nsleep 4\ngrep -oE 'https:\u002F\u002F[a-z0-9-]+\\.[a-z]+\\.pinggy\\.link' \u002Ftmp\u002Fpinggy-8000.log | head -1\n```\n\nExpected output looks like:\n\n```\nYou are not authenticated.\nYour tunnel will expire in 60 minutes.\nhttp:\u002F\u002Fyqycl-98-162-69-48.a.free.pinggy.link\nhttps:\u002F\u002Fyqycl-98-162-69-48.a.free.pinggy.link\n```\n\nHand the `https:\u002F\u002F...pinggy.link` URL to the user.\n\n### 4. Verify\n\n```bash\ncurl -sI https:\u002F\u002F\u003Cthe-url>\u002F | head -3\n# expect 200\u002F302\u002Fwhatever the local origin actually returns\n```\n\nIf you get `502 Bad Gateway`, the SSH session is up but the local origin isn't listening — fix step 1 first.\n\n### 5. Teardown\n\n```bash\nkill \"$(cat \u002Ftmp\u002Fpinggy-8000.pid)\"\n# or, if the pid file got lost:\npkill -f 'ssh -p 443 .* free@a\\.pinggy\\.io'\n```\n\nIf you have a session_id from `terminal(background=True)`, prefer `process(action='kill', session_id=...)`.\n\n## Access Control via Username Keywords\n\nPinggy stacks control flags into the SSH username separated by `+`. Always quote the whole `user@host` argument when it contains a `+`:\n\n| Keyword | Effect |\n|---------|--------|\n| `b:user:pass` | HTTP Basic auth gate |\n| `k:token` | Bearer-token header gate (`Authorization: Bearer \u003Ctoken>`) |\n| `w:CIDR` | IP whitelist (single IP or CIDR, repeatable) |\n| `co` | Add `Access-Control-Allow-Origin: *` (CORS) |\n| `x:https` | Force HTTPS — auto-redirect HTTP to HTTPS |\n| `a:Name:Value` | Add request header |\n| `u:Name:Value` | Update request header |\n| `r:Name` | Remove request header |\n| `qr` | Print a QR code of the URL to stdout (handy for mobile sharing) |\n\nCombine freely: `\"b:admin:secret+co+x:https+free@a.pinggy.io\"`.\n\n## Web Debugger (optional)\n\nPinggy can mirror the inbound traffic to `localhost:4300` for inspection. Add a local forward to the SSH command:\n\n```bash\nssh -p 443 -L4300:localhost:4300 -R0:localhost:8000 free@a.pinggy.io\n```\n\nThen open `http:\u002F\u002Flocalhost:4300` in a browser to see live request\u002Fresponse pairs.\n\n## Pitfalls\n\n- **60-minute hard cap on the free tier.** The SSH session terminates at the 60-minute mark; the URL goes dead. For longer shares, either use `PINGGY_TOKEN` (Pro) or auto-restart with a shell loop (note that the URL changes on every restart for free-tier).\n- **Free-tier URL is random and changes on restart.** Don't bookmark it, don't paste it into a config file. Re-parse from the log each time.\n- **Concurrent free tunnels are limited to one per source IP.** Starting a second tunnel from the same machine usually kills the first. Pro tier lifts this.\n- **`+` in usernames must be quoted.** Bare `ssh ... b:admin:secret+free@a.pinggy.io` works in bash but breaks under shells that treat `+` specially or when assembled programmatically. Always wrap in double quotes.\n- **Don't tunnel anything sensitive without an access-control flag.** A bare HTTP tunnel is reachable by anyone with the URL. Use `b:`, `k:`, or `w:` for non-public services.\n- **`process(action='log')` may miss SSH banner output.** Pinggy prints the URLs and then the SSH session goes interactive. Always redirect to a logfile and `grep` the file directly — same pattern as `cloudflared-quick-tunnel`.\n- **Host-key prompt on first run.** Default OpenSSH config asks the user to accept Pinggy's host key. Always pass `-o StrictHostKeyChecking=no -o UserKnownHostsFile=\u002Fdev\u002Fnull` for unattended runs.\n- **TCP and TLS tunnels return a `\u003Csubdomain>.a.pinggy.online:\u003Cport>` pair, not an https URL.** Parse with a different regex (`tcp:\u002F\u002F` and a port). Don't assume every Pinggy tunnel is HTTP.\n- **Pro mode requires the token as the username, not a flag.** Use `\"$PINGGY_TOKEN+a.pinggy.io\"` (no `free@`). With a token you can also add `:persistent` for a stable subdomain — see `pinggy.io\u002Fdocs\u002F`.\n\n## Recipes\n\nComposite patterns combining a local origin with a Pinggy tunnel. Each recipe is self-contained — start the origin, start the tunnel, parse the URL, hand it back to the user.\n\n### Recipe 1 — Receive a webhook callback\n\nUse this when an external service (Stripe, GitHub, Discord, AgentMail, etc.) needs to POST to a publicly reachable URL during a local task.\n\n```bash\n# 1. Tiny capturing server: every request gets appended to \u002Ftmp\u002Fwebhook-hits.log\ncat >\u002Ftmp\u002Fwebhook-server.py \u003C\u003C'PY'\nimport http.server, json, datetime, pathlib\nLOG = pathlib.Path(\"\u002Ftmp\u002Fwebhook-hits.log\")\nclass H(http.server.BaseHTTPRequestHandler):\n    def _capture(self):\n        n = int(self.headers.get(\"content-length\") or 0)\n        body = self.rfile.read(n).decode(\"utf-8\", \"replace\") if n else \"\"\n        rec = {\"t\": datetime.datetime.utcnow().isoformat(), \"path\": self.path,\n               \"method\": self.command, \"headers\": dict(self.headers), \"body\": body}\n        with LOG.open(\"a\") as f: f.write(json.dumps(rec) + \"\\n\")\n        self.send_response(200); self.send_header(\"content-type\",\"application\u002Fjson\")\n        self.end_headers(); self.wfile.write(b'{\"ok\":true}\\n')\n    def do_GET(self): self._capture()\n    def do_POST(self): self._capture()\n    def log_message(self,*a,**k): pass\nhttp.server.HTTPServer((\"127.0.0.1\", 18080), H).serve_forever()\nPY\nnohup python3 \u002Ftmp\u002Fwebhook-server.py >\u002Ftmp\u002Fwebhook-server.log 2>&1 &\necho $! >\u002Ftmp\u002Fwebhook-server.pid\n\n# 2. Tunnel — bearer-token-gate so randos can't pollute the capture log\nnohup ssh -p 443 -o StrictHostKeyChecking=no -o UserKnownHostsFile=\u002Fdev\u002Fnull \\\n    -o ServerAliveInterval=30 \\\n    -R0:localhost:18080 \"k:$(openssl rand -hex 12)+free@a.pinggy.io\" \\\n    >\u002Ftmp\u002Fwebhook-pinggy.log 2>&1 &\necho $! >\u002Ftmp\u002Fwebhook-pinggy.pid\nsleep 5\nURL=$(grep -oE 'https:\u002F\u002F[a-z0-9-]+\\.[a-z]+\\.pinggy\\.link' \u002Ftmp\u002Fwebhook-pinggy.log | head -1)\necho \"Webhook URL: $URL\"\n\n# 3. While the agent works, watch hits land\ntail -f \u002Ftmp\u002Fwebhook-hits.log\n```\n\nHand `$URL` to the service that needs to call you. Teardown: `kill $(cat \u002Ftmp\u002Fwebhook-server.pid) $(cat \u002Ftmp\u002Fwebhook-pinggy.pid)`.\n\n### Recipe 2 — Expose an MCP server over HTTP\u002FSSE\n\nUse when a remote MCP client (Claude Desktop on another machine, a teammate's editor, etc.) needs to reach an MCP server running on the local box. Only works for MCP servers that speak HTTP transport — stdio-mode servers can't be tunneled.\n\n```bash\n# 1. Start the MCP server in HTTP mode (example: a FastMCP server on port 8765)\nnohup python3 my_mcp_server.py --transport http --port 8765 \\\n    >\u002Ftmp\u002Fmcp-server.log 2>&1 &\necho $! >\u002Ftmp\u002Fmcp-server.pid\n\n# 2. Tunnel with a bearer token — MCP traffic should not be open to the internet\nTOKEN=$(openssl rand -hex 16)\nnohup ssh -p 443 -o StrictHostKeyChecking=no -o UserKnownHostsFile=\u002Fdev\u002Fnull \\\n    -o ServerAliveInterval=30 \\\n    -R0:localhost:8765 \"k:$TOKEN+free@a.pinggy.io\" \\\n    >\u002Ftmp\u002Fmcp-pinggy.log 2>&1 &\necho $! >\u002Ftmp\u002Fmcp-pinggy.pid\nsleep 5\nURL=$(grep -oE 'https:\u002F\u002F[a-z0-9-]+\\.[a-z]+\\.pinggy\\.link' \u002Ftmp\u002Fmcp-pinggy.log | head -1)\necho \"MCP URL: $URL\"\necho \"Bearer token: $TOKEN\"\n```\n\nThe remote client connects to `$URL` with `Authorization: Bearer $TOKEN`. Hermes' own native MCP client config: `{\"transport\": \"http\", \"url\": \"\u003CURL>\", \"headers\": {\"Authorization\": \"Bearer \u003CTOKEN>\"}}`.\n\n### Recipe 3 — Expose a local LLM endpoint (Ollama \u002F vLLM \u002F llama.cpp)\n\nShare a local model with a remote caller (another agent, a phone, a teammate). Ollama listens on `:11434`, vLLM and llama.cpp typically on `:8000`.\n\n```bash\n# Pre-req: the model server is already running on 127.0.0.1:11434 (Ollama default)\nTOKEN=$(openssl rand -hex 16)\nnohup ssh -p 443 -o StrictHostKeyChecking=no -o UserKnownHostsFile=\u002Fdev\u002Fnull \\\n    -o ServerAliveInterval=30 \\\n    -R0:localhost:11434 \"k:$TOKEN+co+free@a.pinggy.io\" \\\n    >\u002Ftmp\u002Fllm-pinggy.log 2>&1 &\necho $! >\u002Ftmp\u002Fllm-pinggy.pid\nsleep 5\nURL=$(grep -oE 'https:\u002F\u002F[a-z0-9-]+\\.[a-z]+\\.pinggy\\.link' \u002Ftmp\u002Fllm-pinggy.log | head -1)\necho \"Endpoint: $URL\"\necho \"Token:    $TOKEN\"\n\n# Verify\ncurl -s \"$URL\u002Fapi\u002Ftags\" -H \"Authorization: Bearer $TOKEN\" | head\n```\n\n`co` enables CORS so a browser caller can hit the endpoint. Drop `co` for backend-only callers. For an OpenAI-compatible vLLM\u002Fllama.cpp endpoint, callers use base URL `$URL\u002Fv1` with `Authorization: Bearer $TOKEN` — but note Pinggy strips\u002Freplaces nothing in the body, so the model server itself sees Pinggy's token; the local server should be configured to ignore auth (it's already on `127.0.0.1`) and let Pinggy do the gating.\n\n### Recipe 4 — Share a dev server with a one-shot password\n\nThe fastest \"let a teammate poke at my running app\" pattern. Random password, prints once, dies when you Ctrl-C.\n\n```bash\nPASS=$(openssl rand -base64 12 | tr -d '+\u002F=' | head -c 12)\necho \"Dev server password: $PASS\"\nssh -p 443 -o StrictHostKeyChecking=no -o UserKnownHostsFile=\u002Fdev\u002Fnull \\\n    -o ServerAliveInterval=30 \\\n    -R0:localhost:3000 \"b:dev:$PASS+co+x:https+free@a.pinggy.io\"\n# URL prints to the terminal. Share URL + password. Ctrl-C to tear down.\n```\n\n`b:dev:$PASS` gates the URL with HTTP Basic auth. `x:https` forces TLS. `co` adds CORS for SPA frontends.\n\n## Verification\n\n```bash\n# End-to-end: spin up a trivial origin, tunnel it, hit it, tear down\npython3 -m http.server 18000 --bind 127.0.0.1 >\u002Ftmp\u002Forigin.log 2>&1 &\nORIGIN_PID=$!\n\nnohup ssh -p 443 \\\n    -o StrictHostKeyChecking=no \\\n    -o UserKnownHostsFile=\u002Fdev\u002Fnull \\\n    -R0:localhost:18000 free@a.pinggy.io >\u002Ftmp\u002Fpinggy-verify.log 2>&1 &\nSSH_PID=$!\n\nsleep 5\nURL=$(grep -oE 'https:\u002F\u002F[a-z0-9-]+\\.[a-z]+\\.pinggy\\.link' \u002Ftmp\u002Fpinggy-verify.log | head -1)\necho \"URL: $URL\"\ncurl -sI \"$URL\u002F\" | head -1\n\nkill \"$SSH_PID\" \"$ORIGIN_PID\"\n```\n\nExpected: a `pinggy.link` URL and `HTTP\u002F2 200` on the curl head.\n",{"name":5,"author":24,"license":15,"version":25,"metadata":26,"platforms":38,"description":7},"Teknium (teknium1), Hermes Agent","0.1.0",{"hermes":27},{"tags":28,"related_skills":35},[29,30,31,32,33,34],"Pinggy","Tunnel","Networking","SSH","Webhook","Localhost",[36,37],"cloudflared-quick-tunnel","webhook-subscriptions",[39,40,41],"linux","macos","windows","autoresearch\u002Fpi-agent-merchantbench-net-assets-workspace-omp-20260901","762e83a83bedbed565e95e7d42d39204c367c9eb","hermes-agent\u002Foptional-skills\u002Fdevops\u002Fpinggy-tunnel","https:\u002F\u002Fgithub.com\u002Fyuxua24\u002Fworkspace","https:\u002F\u002Fgithub.com\u002Fyuxua24","I am Ao Yuxuan, a student in Xi'an Jiaotong University. I am eager to learn on GitHub and contribute my part to this community.","2026-09-01 17:37:09",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add yuxua24\u002Fworkspace --skill pinggy-tunnel",{"tool":55,"command":56},"bunx","bunx skills add yuxua24\u002Fworkspace --skill pinggy-tunnel",{"tool":58,"command":59},"pnpm","pnpm dlx skills add yuxua24\u002Fworkspace --skill pinggy-tunnel","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fyuxua24\u002Fworkspace\u002Fblob\u002Fautoresearch\u002Fpi-agent-merchantbench-net-assets-workspace-omp-20260901\u002Fhermes-agent\u002Foptional-skills\u002Fdevops\u002Fpinggy-tunnel\u002FSKILL.md",true,[],[64,71,78,85,92,99],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7BXERWENH07XE9XAV53QZ2D","test-driven-development","TDD: enforce RED-GREEN-REFACTOR, tests before code.","https:\u002F\u002Fgithub.com\u002Fyuxua24\u002Fworkspace\u002Fblob\u002Fautoresearch\u002Fpi-agent-merchantbench-net-assets-workspace-omp-20260901\u002Fhermes-agent\u002Fskills\u002Fsoftware-development\u002Ftest-driven-development\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7BXEMHAJQA0RVGZ43ZNDFH2","systematic-debugging","4-phase root cause debugging: understand bugs before fixing.","https:\u002F\u002Fgithub.com\u002Fyuxua24\u002Fworkspace\u002Fblob\u002Fautoresearch\u002Fpi-agent-merchantbench-net-assets-workspace-omp-20260901\u002Fhermes-agent\u002Fskills\u002Fsoftware-development\u002Fsystematic-debugging\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7BXEGNTY1MJD5W8GSWT7MAP","spike","Throwaway experiments to validate an idea before build.","https:\u002F\u002Fgithub.com\u002Fyuxua24\u002Fworkspace\u002Fblob\u002Fautoresearch\u002Fpi-agent-merchantbench-net-assets-workspace-omp-20260901\u002Fhermes-agent\u002Fskills\u002Fsoftware-development\u002Fspike\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7BXEE77341X1N35WV5CBXAY","simplify-code","Parallel 3-agent cleanup of recent code changes.","https:\u002F\u002Fgithub.com\u002Fyuxua24\u002Fworkspace\u002Fblob\u002Fautoresearch\u002Fpi-agent-merchantbench-net-assets-workspace-omp-20260901\u002Fhermes-agent\u002Fskills\u002Fsoftware-development\u002Fsimplify-code\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M7BXEASY2T61Y8FRYTXGMKWY","requesting-code-review","Pre-commit review: security scan, quality gates, auto-fix.","https:\u002F\u002Fgithub.com\u002Fyuxua24\u002Fworkspace\u002Fblob\u002Fautoresearch\u002Fpi-agent-merchantbench-net-assets-workspace-omp-20260901\u002Fhermes-agent\u002Fskills\u002Fsoftware-development\u002Frequesting-code-review\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M7BXE6H4KWMW0DKVXR5G61E4","python-debugpy","Debug Python: pdb REPL + debugpy remote (DAP).","https:\u002F\u002Fgithub.com\u002Fyuxua24\u002Fworkspace\u002Fblob\u002Fautoresearch\u002Fpi-agent-merchantbench-net-assets-workspace-omp-20260901\u002Fhermes-agent\u002Fskills\u002Fsoftware-development\u002Fpython-debugpy\u002FSKILL.md",[],[]]